** Description changed:
After performing an apt-get update && apt-get upgrade today (1/19),
mythbackend is no longer stable. There is no exiting information
contained in the mythbackend.log file, however there are numerous
reports of "MainServer, Warning: Unknown socket closing MythSocket"
No longer an issue. I don't understand what changed here - but it would
appear the master backend IP in the database (192.168.0.200) no longer
matched the IP configured in mythtv-setup (127.0.0.1). Hence
mythbackend was assuming itself a slave. Changed IP in mythtv-setup to
the public 192.168.0
Apport bug report attached - although not sure how useful this is as it
wouldn't capture the crash ...
** Attachment added: "apport.mythtv-backend.dUszTT.apport"
https://bugs.launchpad.net/mythbuntu/+bug/705077/+attachment/2023402/+files/apport.mythtv-backend.dUszTT.apport
--
You received th
I'm seeing identical issues here. Mythbunu 10.10 installed & latest
updates applied. System 100% stable for a few days, then yesterday myth
backend starting failing (segfault at 50 ip b46922dc sp bfb94bc0 error 4
in libQtCore.so.4.7.0).
Entries from /var/log/messages:-
Apr 12 10:58:02 myth ker
MythTV Version : 26437
MythTV Branch: branches/release-0-23-fixes
Network Protocol : 23056
Library API : 0.23.1.201000710-1
QT Version : 4.7.0
Options compiled in:
linux debug using_oss using_alsa using_pulse using_jack using_pulseoutput
using_backend using_dvb using_firewire usi
Entries from /var/log/mythtv/mythbackend.log:-
2011-04-12 10:57:07.272 mythbackend version: branches/release-0-23-fixes
[26437] www.mythtv.org
2011-04-12 10:57:07.305 Using runtime prefix = /usr
2011-04-12 10:57:07.330 Using configuration directory = /home/mythtv/.mythtv
2011-04-12 10:57:07.347 E
Hi Will, thanks for the bug report, but there's a few things missing
here.
Can you please follow the directions here:
http://www.mythtv.org/wiki/Debugging#Debugging_with_Ubuntu_packages
Particularly
1) En the apport service
2) Install mythtv-dbg
3) File the crash as it occurs so it will include
This is the /var/log/messages file from the last reboot. From 11:06:02
to 11:06:35 the computer boots. At 11:07:04 the first mythbackend
segfault occurs. The segfaults after that are all caused as I
periodically restarted the backend using "service mythtv-backend start"
** Attachment added: ".var.
--
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
https://bugs.launchpad.net/bugs/705077
Title:
mythbackend will segfault about 10 minutes after starting. "segfault
at 50 ip 0209d2dc sp bff215c0 error 4 in
libQtCore.so.
9 matches
Mail list logo