<div class="gmail_quote">On Thu, Nov 22, 2012 at 2:26 PM, Richard Shaw <span dir="ltr"><<a href="mailto:hobbes1069@gmail.com" target="_blank">hobbes1069@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Thu, Nov 22, 2012 at 10:36 AM, Jerry <span dir="ltr"><<a href="mailto:mythtv@hambone.e4ward.com" target="_blank">mythtv@hambone.e4ward.com</a>></span> wrote:<br></div><div class="gmail_quote"><div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br><br>I just installed 0.26.0 from RPMFusion on Fedora 17 last night and I'm getting problems with mythtv-common-0.26.0-1.fc17.x86_64 in abrt (the error reporting daemon in Fedora). I'm not sure what to do next to give you any more information than that.</blockquote>
<div><br></div></div><div>Short answer for the moment... I'm not sure what's going on. I had a couple of beta testers but none reported issues like this. I haven't upgraded yet because my FE/BE machine is still on Fedora 14 which has too old of an x264 build for 0.26. My plan over the Thanksgiving holiday was to convert over to CentOS 6.3 but I haven't had time yet. Hopefully others on the list will have some ideas.</div>
<div><br></div><div>Thanks,</div><div>Richard</div></div></blockquote><div> <br>Here is some more info from the abrtd log. I ran this a few times with the same result. Mythlogserver seems to be the culprit, but it was running fine after seeing the message from abrtd.<br>
<br><span style="font-family:courier new,monospace">[root@sirius ccpp-2012-11-22-15:30:49-2018]# pwd<br>/var/spool/abrt/ccpp-2012-11-22-15:30:49-2018<br>[root@sirius ccpp-2012-11-22-15:30:49-2018]# more cmdline<br>/usr/bin/mythlogserver --daemon --verbose general --logpath /var/log/mythtv --loglevel info<br>
[root@sirius ccpp-2012-11-22-15:30:49-2018]# more kernel<br>3.6.7-4.fc17.x86_64<br>[root@sirius ccpp-2012-11-22-15:30:49-2018]# more reason<br>Process /usr/bin/mythlogserver was killed by signal 11 (SIGSEGV)<br>[root@sirius ccpp-2012-11-22-15:30:49-2018]# more pid<br>
2018<br>[root@sirius ccpp-2012-11-22-15:30:49-2018]# ps ax | grep mythlogserver<br> 2031 ? Ssl 0:01 /usr/bin/mythlogserver --daemon --verbose general --logpath /var/log/mythtv --loglevel info<br> 2279 pts/0 S+ 0:00 grep --color=auto mythlogserver<br>
[root@sirius ccpp-2012-11-22-15:30:49-2018]#</span><br><br>So there seems to be a segmentation violation, but then something starts it over again. I killed the process that was running and restarted it using the same syntax without abrtd complaining. Is there a way I can more closely watch mythlogserver?<br>
</div></div>