[mythtv-users] mythtv-common-0.26.0-1.fc17.x86_64 giving errors in abrt daemon on startup

[Jerry]

On Sun, Nov 25, 2012 at 10:44 AM, Bill Meek <keemllib at gmail.com> wrote:

> On 11/24/2012 05:23 PM, Jerry wrote:
>
>> Mythbackend seems to be causing a crash in mythlogserver.  Is this
>> something that can be tracked in a backtrace?  I'm not familiar with the
>> process.
>>
>
> From your earlier post, mythlogserver is taking the SEGV:
>
>
>   [root at sirius ccpp-2012-11-22-15:30:49-2018]**# more reason
>   Process /usr/bin/mythlogserver was killed by signal 11 (SIGSEGV)
>
> My experience may be similar to yours, when the backend service is stopped,
> the logserver SEGVs. But to prove that, the backtrace is required.
>
> My personal choice for getting the backtrace in this situation is to
> analyze the core file using suggestions here:
>
>    http://www.mythtv.org/wiki/**Debugging#Using_core_files<http://www.mythtv.org/wiki/Debugging#Using_core_files>
>
> But I don't know how your distribution handles that. I use the command
> ulimit -c unlimited in /etc/init/mythtv-backend.conf just ahead of the
> mythbackend ... command. Also the kernel.core_pattern etc. lines in the
> link above.
>

Here is output from a crash that happened this afternoon.  I'm not sure if
this backtrace is equivalent to what you are referring to.

[root at sirius ccpp-2012-12-02-14:43:07-2122]# pwd
/var/spool/abrt/ccpp-2012-12-02-14:43:07-2122
[root at sirius ccpp-2012-12-02-14:43:07-2122]# ls
abrt_version  cgroup     core_backtrace  dso_list    hostname  maps
package   pkg_epoch    pkg_version      reason  username
analyzer      cmdline    coredump        environ     kernel    open_fds
pid       pkg_name     proc_pid_status  time    uuid
architecture  component  count           executable  limits    os_release
pkg_arch  pkg_release  pwd              uid     var_log_messages
[root at sirius ccpp-2012-12-02-14:43:07-2122]# more core_backtrace
cc10c72da62c93033e227ffbe2670f2c4fbbde1a 0x35935 raise /lib64/libc.so.6
f33186a4c862fb0751bca60701f553b829210477
cc10c72da62c93033e227ffbe2670f2c4fbbde1a 0x370e8 abort /lib64/libc.so.6
352bc5cf09233cea84fd089527a146cfb5b7d8dc
cc10c72da62c93033e227ffbe2670f2c4fbbde1a 0x2e6a2 __assert_fail_base
/lib64/libc.so.6 985cad4c0d01e51136a4033696476fe616cc6d7d
cc10c72da62c93033e227ffbe2670f2c4fbbde1a 0x2e752 __assert_fail
/lib64/libc.so.6 -
704aa861b9d32507ded81dd8cdf8577d053361fc 0x8e30 - /lib64/libmythnzmqt.so.0
844cdba0f601ea41c6b91ffa7fbd83da2da4257b
704aa861b9d32507ded81dd8cdf8577d053361fc 0xc7f8 - /lib64/libmythnzmqt.so.0
bef51a4b3c03e7adf1009d4febf2ac2fab772f19
8521a74f5b8164a36e245af9524fb7d0be9e1203 0x10f8a1 -
/lib64/libmythbase-0.26.so.0 c6570a41179bc462a0e882ead70c08ce0ef209c2
d1e01c71534f1e41fe10f0aed58b3bf6711aadfb 0x7b7bc - /lib64/libQtCore.so.4
52c6044b46de75bcba060fa79f7482d349610223
 0xaa764 - /usr/lib64/nvidia/libGL.so.1
69bdd1dd02093527d72da8890aca3cbd5a6d7006
699e7556b23d23a857371af778a5394a7149da61 0x7d14 start_thread
/lib64/libpthread.so.0 b0385609f3dd5ea1b79d56946826dcbb1b62d86f
cc10c72da62c93033e227ffbe2670f2c4fbbde1a 0xf168d clone /lib64/libc.so.6
e256aa64ea4f21c9e32cd0f782dbc840f150a5b3
[root at sirius ccpp-2012-12-02-14:43:07-2122]# more reason
Process /usr/bin/mythlogserver was killed by signal 6 (SIGABRT)
[root at sirius ccpp-2012-12-02-14:43:07-2122]#

Does that help to clarify what is going on?  This time, it seems to be a
different signal (failed assertion?).

Jerry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20121202/ea66abce/attachment.html>