[mythtv-users] RE: Mythfrontend and backend crashes on yesterday's CVS

nowhere nowhere at cox.net
Thu Nov 4 15:08:05 UTC 2004


Once more piece of information. I see this quite a bit and it seems to
be correlated to some of the front end freezes/crashes:

Nov  4 01:14:05 localhost gconfd (mythtv-12664): starting (version
2.6.0), pid 12664 user 'mythtv'
Nov  4 01:14:05 localhost gconfd (mythtv-12664): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config
source at position 0
Nov  4 01:14:05 localhost gconfd (mythtv-12664): Resolved address
"xml:readwrite:/home/mythtv/.gconf" to a writable config source at
position 1
Nov  4 01:14:05 localhost gconfd (mythtv-12664): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config
source at position 2
Nov  4 01:14:59 localhost lircd 0.7.0pre7[2334]: accepted new client on
/dev/lircd
Nov  4 01:15:05 localhost gconfd (mythtv-12664): GConf server is not in
use, shutting down.
Nov  4 01:15:05 localhost gconfd (mythtv-12664): Exiting
Nov  4 01:15:24 localhost lircd 0.7.0pre7[2334]: accepted new client on
/dev/lircd
Nov  4 01:30:30 localhost gconfd (mythtv-12700): starting (version
2.6.0), pid 12700 user 'mythtv'
Nov  4 01:30:30 localhost gconfd (mythtv-12700): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config
source at position 0
Nov  4 01:30:30 localhost gconfd (mythtv-12700): Resolved address
"xml:readwrite:/home/mythtv/.gconf" to a writable config source at
position 1
Nov  4 01:30:30 localhost gconfd (mythtv-12700): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config
source at position 2

Not even sure those are error messages tho...

Thanks,
Eric

> -----Original Message-----
> From: nowhere [mailto:nowhere at cox.net]
> Sent: Wednesday, November 03, 2004 10:34 PM
> To: MythTV Users (mythtv-users at mythtv.org)
> Subject: Mythfrontend and backend crashes on yesterday's CVS
> 
> Hi everyone,
> 
> Chances are I already know the answer but I would like some
confirmation.
> The mythfrontend is crashing very very frequently, dropping out to the
X
> desktop when I try to do many different things like start a video,
delete
> videos, use the skip function while watching a video, starting LiveTV,
> calling up the OSG etc.
> 
> Quite frequently I will have the backend crash too in what I believe
is
> association with the frontend crashes but sometimes I walk up and find
the
> back end dead (or not responding and needing a restart).
> 
> There are no errors in dmesg, or /var/log/messages and the backend
logs
> show no errors either, but yesterday's crash has a huge hole in the
log
> with no entries from about 1am to 7pm on 11-02.
> 
> I did notice that in the messages file at 7:06am (during that gap
above) I
> find the following...
> 
> Nov  2 07:06:53 localhost kernel: hda: dma_intr: status=0x51 {
DriveReady
> SeekComplete Error }
> Nov  2 07:06:53 localhost kernel: hda: dma_intr: error=0x40 {
> UncorrectableError }, LBAsect=2158733, high=0, low=2158733,
sector=2158733
> Nov  2 07:06:53 localhost kernel: end_request: I/O error, dev hda,
sector
> 2158733
> Nov  2 07:06:57 localhost kernel: hda: dma_intr: status=0x51 {
DriveReady
> SeekComplete Error }
> Nov  2 07:06:57 localhost kernel: hda: dma_intr: error=0x40 {
> UncorrectableError }, LBAsect=2158733, high=0, low=2158733,
sector=2158733
> Nov  2 07:06:57 localhost kernel: end_request: I/O error, dev hda,
sector
> 2158733
> 
> So. I'm betting I know what this means but would like to hear it from
> someone else before I spend more money. Keep in mind we had a power
> failure of some kind last month that trashed my filesystem requiring
me to
> format and start over with the root filesystem (my /video partition
> survived that).
> 
> I was suspecting that the hack of a script I wrote to re-insert all
the
> videos that survived the crash back into mysql was causing the
instability
> but I have since watched and deleted them all and have found the had
error
> in the logs now.
> 
> Please let me know what you all think...
> 
> Thanks,
> Eric



More information about the mythtv-users mailing list