No subject

<br>
<br>
=A0 [root at sirius ccpp-2012-11-22-15:30:49-2018]<u></u># more reason<br></di=
v><div class=3D"im">
=A0 Process /usr/bin/mythlogserver was killed by signal 11 (SIGSEGV)<br>
<br></div>
My experience may be similar to yours, when the backend service is stopped,=
<br>
the logserver SEGVs. But to prove that, the backtrace is required.<br>
<br>
My personal choice for getting the backtrace in this situation is to<br>
analyze the core file using suggestions here:<br>
<br>
=A0 =A0<a href=3D"http://www.mythtv.org/wiki/Debugging#Using_core_files" ta=
rget=3D"_blank">http://www.mythtv.org/wiki/<u></u>Debugging#Using_core_file=
s</a><br>
<br>
But I don&#39;t know how your distribution handles that. I use the command<=
br>
ulimit -c unlimited in /etc/init/mythtv-backend.conf just ahead of the<br>
mythbackend ... command. Also the kernel.core_pattern etc. lines in the<br>
link above.<br></blockquote></div><br>Here is output from a crash that happ=
ened this afternoon.=A0 I&#39;m not sure if this backtrace is equivalent to=
 what you are referring to.<br><br><span style=3D"font-family:courier new,m=
onospace">[root at sirius ccpp-2012-12-02-14:43:07-2122]# pwd<br>

/var/spool/abrt/ccpp-2012-12-02-14:43:07-2122<br>[root at sirius ccpp-2012-12-=
02-14:43:07-2122]# ls<br>abrt_version=A0 cgroup=A0=A0=A0=A0 core_backtrace=
=A0 dso_list=A0=A0=A0 hostname=A0 maps=A0=A0=A0=A0=A0=A0=A0 package=A0=A0 p=
kg_epoch=A0=A0=A0 pkg_version=A0=A0=A0=A0=A0 reason=A0 username<br>

analyzer=A0=A0=A0=A0=A0 cmdline=A0=A0=A0 coredump=A0=A0=A0=A0=A0=A0=A0 envi=
ron=A0=A0=A0=A0 kernel=A0=A0=A0 open_fds=A0=A0=A0 pid=A0=A0=A0=A0=A0=A0 pkg=
_name=A0=A0=A0=A0 proc_pid_status=A0 time=A0=A0=A0 uuid<br>architecture=A0 =
component=A0 count=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 executable=A0 limits=A0=A0=
=A0 os_release=A0 pkg_arch=A0 pkg_release=A0 pwd=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0 uid=A0=A0=A0=A0 var_log_messages<br>

[root at sirius ccpp-2012-12-02-14:43:07-2122]# more core_backtrace<br>cc10c72=
da62c93033e227ffbe2670f2c4fbbde1a 0x35935 raise /lib64/libc.so.6 f33186a4c8=
62fb0751bca60701f553b829210477<br>cc10c72da62c93033e227ffbe2670f2c4fbbde1a =
0x370e8 abort /lib64/libc.so.6 352bc5cf09233cea84fd089527a146cfb5b7d8dc<br>

cc10c72da62c93033e227ffbe2670f2c4fbbde1a 0x2e6a2 __assert_fail_base /lib64/=
libc.so.6 985cad4c0d01e51136a4033696476fe616cc6d7d<br>cc10c72da62c93033e227=
ffbe2670f2c4fbbde1a 0x2e752 __assert_fail /lib64/libc.so.6 -<br>704aa861b9d=
32507ded81dd8cdf8577d053361fc 0x8e30 - /lib64/libmythnzmqt.so.0 844cdba0f60=
1ea41c6b91ffa7fbd83da2da4257b<br>

704aa861b9d32507ded81dd8cdf8577d053361fc 0xc7f8 - /lib64/libmythnzmqt.so.0 =
bef51a4b3c03e7adf1009d4febf2ac2fab772f19<br>8521a74f5b8164a36e245af9524fb7d=
0be9e1203 0x10f8a1 - /lib64/libmythbase-0.26.so.0 c6570a41179bc462a0e882ead=
70c08ce0ef209c2<br>

d1e01c71534f1e41fe10f0aed58b3bf6711aadfb 0x7b7bc - /lib64/libQtCore.so.4 52=
c6044b46de75bcba060fa79f7482d349610223<br>=A00xaa764 - /usr/lib64/nvidia/li=
bGL.so.1 69bdd1dd02093527d72da8890aca3cbd5a6d7006<br>699e7556b23d23a857371a=
f778a5394a7149da61 0x7d14 start_thread /lib64/libpthread.so.0 b0385609f3dd5=
ea1b79d56946826dcbb1b62d86f<br>

cc10c72da62c93033e227ffbe2670f2c4fbbde1a 0xf168d clone /lib64/libc.so.6 e25=
6aa64ea4f21c9e32cd0f782dbc840f150a5b3<br>[root at sirius ccpp-2012-12-02-14:43=
:07-2122]# more reason<br>Process /usr/bin/mythlogserver was killed by sign=
al 6 (SIGABRT)<br>

[root at sirius ccpp-2012-12-02-14:43:07-2122]#</span><br><br>Does that help t=
o clarify what is going on?=A0 This time, it seems to be a different signal=
 (failed assertion?).<br><br>Jerry<br>

--f46d044784e9fcaa8204cfe94c5a--