View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 16 posts ] 
Go to page 1, 2  Next

Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Mon Sep 07, 2009 5:02 pm 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
About a month ago, I moved the guts of my KM 5.5 computer into a new Home Theater case, so it would fit under my tv with the other video components. There is adequate ventilation in the new case and the temperature sensors never read more than 34 degrees C.

About 2 weeks ago, I started seeing that every couple of days, the Mythtv GUI had stopped and the screen was showing the Fluxbox desktop with Cecil, Dale and Tux. When this happened, I just restarted the Mythtv GUI with a "pkill xinit" or a RIGHT-CLICK, EXIT with the mouse.

When the machine was in it's former case, I never saw the Mythtv GUI stop like this.

This holiday weekend, I started looking at the logs. Each day that the GUI has stopped, I see these lines in the /var/log/mythtv/mythtvfrontend.log file:
Code:
2009-09-07 17:31:59.819 New DB connection, total: 2
2009-09-07 17:31:59.834 Connected to database 'mythconverg' at host: localhost
2009-09-07 17:31:59.843 mythfrontend version: 0.21.20080304-1 www.mythtv.org
2009-09-07 17:31:59.844 Enabled verbose msgs:  important general
2009-09-07 17:32:00.280 Unable to parse themeinfo.xml for glass-wide
2009-09-07 17:32:00.280 The theme (glass-wide) is missing a themeinfo.xml file
2009-09-07 17:32:00.740 Unable to parse themeinfo.xml for glass-wide
2009-09-07 17:32:00.740 The theme (glass-wide) is missing a themeinfo.xml file
2009-09-07 17:32:01.175 No theme dir: /home/mythtv/.mythtv/themes/neon-wide
2009-09-07 17:32:01.177 Primary screen 0.
2009-09-07 17:32:01.177 Using screen 0, 1920x1080 at 0,0
2009-09-07 17:32:01.178 No theme dir: /home/mythtv/.mythtv/themes/neon-wide
2009-09-07 17:32:01.179 Switching to wide mode (neon-wide)
2009-09-07 17:32:01.212 Using the Qt painter
2009-09-07 17:32:01.214 lirc init success using configuration file: /home/mythtv/.mythtv/lircrc
2009-09-07 17:32:01.245 JoystickMenuClient Error: Joystick disabled - Failed to open device /dev/input/js0
2009-09-07 17:32:02.991 Loading from: /usr/share/mythtv/themes/neon-wide/base.xml
2009-09-07 17:32:03.160 Loading from: /usr/share/mythtv/themes/default/base.xml
2009-09-07 17:32:03.255 Registering Internal as a media playback plugin.
2009-09-07 17:32:03.462 MonitorRegisterExtensions(0x100, gif,jpg,png)
2009-09-07 17:32:03.883 MythMusic adding CD-Writer: ATA:1,0,0 -- DVD-RW  DVR-111D
2009-09-07 17:32:05.390 Failed to run 'cdrecord --scanbus -dev=ATAPI'
2009-09-07 17:32:05.429 MonitorRegisterExtensions(0x40, ogg,mp3,aac,flac)
SIP listening on IP Address 192.168.7.10:5060 NAT address 192.168.7.10
SIP: Cannot register; proxy, username or password not set
2009-09-07 17:32:05.677 No theme dir: /home/mythtv/.mythtv/themes/neon-wide
mount: No medium found
2009-09-07 17:32:06.059 Failed to mount /dev/sdb.
mount: No medium found
2009-09-07 17:32:06.215 Failed to mount /dev/sdc.
mount: No medium found
2009-09-07 17:32:06.371 Failed to mount /dev/sdd.
mount: No medium found
2009-09-07 17:32:06.529 Failed to mount /dev/sde.


This afternoon, I removed both sticks of RAM, blew out the case and reseated the RAM. It has not had an effect. The Mythtv GUI stopped again - sometime between 3pm and 5:30pm.

I'm not 100% sure these log entries are directly linked to the stopping of the Mythtv GUI, but they are common to all the Mythtv GUI stops I have seen. At this point, I'm not sure if this is a software problem or a hardware problem.

Does this situation look familiar to anyone? I'm not sure what to look at next.

Eric

_________________
KnoppMyth R5.5, Asus A8N-VM CSM (nvidia 6150 onboard video), AMD Athlon 64 dual-core 4200+, two 1GB sticks DDR 400, HD-3000 HDTV card, PVR-150 card, Iguanaworks RS-232 IR receiver/transmitter, Pioneer DVR-110 DVD burner


Last edited by neutron68 on Fri Sep 18, 2009 10:04 am, edited 1 time in total.


Top
 Profile  
 
PostPosted: Mon Sep 07, 2009 6:46 pm 
Offline
Joined: Sun Aug 28, 2005 7:07 pm
Posts: 821
Location: Melbourne, Australia
neutron68 wrote:
I'm not sure what to look at next.
Eric


tail -50 /var/log/Xorg.0.log
tail -30 /var/log/messages
run dmesg|less

Change the numbers to how ever many lines you want to look at. you can also pipe dmesg through tail -20 instead of less.

Here's what I would do:
1. quit mythfrontend
2. pop up an xterm
3. run mythfrontend like this:
mythfrontend -v all -l /home/mythtv/frontend-verboselogging.log

Don't close the xterm, but alt-tab to get to your frontend. You can alt-tab whenever you want to see what's going on. I *think* it will also log to stdout (the xterm) but it will always log to the file you asked it to log to. Have a look at it as soon as the frontend crashes (of course, it will never crash, since now you're looking at it :-) )

Mike

_________________
*********************
LinHES 7.4
Australian Dragon
*********************


Top
 Profile  
 
 Post subject: other details
PostPosted: Mon Sep 07, 2009 7:08 pm 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
Thanks manicmike. I'll try your suggestions.
When you say XTERM, do you mean to pop up a virtual console by doing an CTRL-ALT-F1 or CTRL-ALT-F2, etc?
Or do you mean to open a window on the Fluxbox desktop where Cecil, Dale and Tux are?

:!:I just thought of other changes I made when I moved cases...

I removed the floppy disk drive and did not move it to the new case, AND I did NOT change the /etc/fstab file - which still has an entry for the floppy drive. Could this be it?

Also, I plugged in a USB memory card reader that was part of the HT case.
I see messages in the dmesg that look like the card readers getting recognized. Maybe these are screwing up the system?

Code:
root@mythtv:/tmp# dmesg|less
ense not available.
scsi 4:0:0:0: rejecting I/O to dead device
scsi 4:0:0:0: [sdb] READ CAPACITY failed
scsi 4:0:0:0: [sdb] Result: hostbyte=0x01 driverbyte=0x00
scsi 4:0:0:0: [sdb] Sense not available.
scsi 4:0:0:0: rejecting I/O to dead device
scsi 4:0:0:0: [sdb] Write Protect is off
scsi 4:0:0:0: [sdb] Mode Sense: 00 00 00 00
scsi 4:0:0:0: [sdb] Assuming drive cache: write through
scsi 4:0:0:0: rejecting I/O to dead device
scsi 4:0:0:1: rejecting I/O to dead device
scsi 4:0:0:1: rejecting I/O to dead device
scsi 4:0:0:1: rejecting I/O to dead device
scsi 4:0:0:1: rejecting I/O to dead device
scsi 4:0:0:1: [sdc] READ CAPACITY failed
scsi 4:0:0:1: [sdc] Result: hostbyte=0x01 driverbyte=0x00
scsi 4:0:0:1: [sdc] Sense not available.
scsi 4:0:0:1: rejecting I/O to dead device
scsi 4:0:0:1: [sdc] Write Protect is off
scsi 4:0:0:1: [sdc] Mode Sense: 00 00 00 00
scsi 4:0:0:1: [sdc] Assuming drive cache: write through
scsi 4:0:0:1: rejecting I/O to dead device
scsi 4:0:0:3: [sde] Write Protect is off
scsi 4:0:0:3: [sde] Mode Sense: 00 00 00 00
scsi 4:0:0:3: [sde] Assuming drive cache: write through
scsi 4:0:0:3: rejecting I/O to dead device
scsi 4:0:0:3: [sde] READ CAPACITY failed
scsi 4:0:0:3: [sde] Result: hostbyte=0x01 driverbyte=0x00
scsi 4:0:0:3: [sde] Sense not available.
scsi 4:0:0:3: rejecting I/O to dead device
scsi 4:0:0:3: [sde] Write Protect is off
scsi 4:0:0:3: [sde] Mode Sense: 00 00 00 00
scsi 4:0:0:3: [sde] Assuming drive cache: write through
scsi 4:0:0:3: rejecting I/O to dead device
usb 1-6: new high speed USB device using ehci_hcd and address 3
usb 1-6: configuration #1 chosen from 1 choice
scsi5 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
scsi 5:0:0:0: Direct-Access     Generic  USB SD Reader    1.00 PQ: 0 ANSI: 0
sd 5:0:0:0: [sdb] Attached SCSI removable disk
scsi 5:0:0:1: Direct-Access     Generic  USB CF Reader    1.01 PQ: 0 ANSI: 0
sd 5:0:0:1: [sdc] Attached SCSI removable disk
scsi 5:0:0:2: Direct-Access     Generic  USB SM Reader    1.02 PQ: 0 ANSI: 0
sd 5:0:0:2: [sdd] Attached SCSI removable disk
scsi 5:0:0:3: Direct-Access     Generic  USB MS Reader    1.03 PQ: 0 ANSI: 0
sd 5:0:0:3: [sde] Attached SCSI removable disk
usb-storage: device scan complete
mythfrontend[4032]: segfault at 9759fedb eip 081c42a8 esp bfeb158c error 6


Eric

_________________
KnoppMyth R5.5, Asus A8N-VM CSM (nvidia 6150 onboard video), AMD Athlon 64 dual-core 4200+, two 1GB sticks DDR 400, HD-3000 HDTV card, PVR-150 card, Iguanaworks RS-232 IR receiver/transmitter, Pioneer DVR-110 DVD burner


Top
 Profile  
 
 Post subject: Re: other details
PostPosted: Mon Sep 07, 2009 7:52 pm 
Offline
Joined: Sun Aug 28, 2005 7:07 pm
Posts: 821
Location: Melbourne, Australia
neutron68 wrote:
Thanks manicmike. I'll try your suggestions.
When you say XTERM, do you mean to pop up a virtual console by doing an CTRL-ALT-F1 or CTRL-ALT-F2, etc?
Or do you mean to open a window on the Fluxbox desktop where Cecil, Dale and Tux are?


The latter (alt+x is a keyboard shortcut). Incidentally, I didn't know that white guy was Dale.

neutron68 wrote:
:!:I just thought of other changes I made when I moved cases...

I removed the floppy disk drive and did not move it to the new case, AND I did NOT change the /etc/fstab file - which still has an entry for the floppy drive. Could this be it?


I doubt it, but quote it out just in case.

neutron68 wrote:
Also, I plugged in a USB memory card reader that was part of the HT case.
I see messages in the dmesg that look like the card readers getting recognized. Maybe these are screwing up the system?
Eric


How long after you plugged in the USB device did the frontend crash?

Mike

_________________
*********************
LinHES 7.4
Australian Dragon
*********************


Top
 Profile  
 
 Post subject: Re: other details
PostPosted: Mon Sep 07, 2009 9:09 pm 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
manicmike wrote:

neutron68 wrote:
Also, I plugged in a USB memory card reader that was part of the HT case.
I see messages in the dmesg that look like the card readers getting recognized. Maybe these are screwing up the system?
Eric


How long after you plugged in the USB device did the frontend crash?

Mike

It may have been a week after moving into the HT case before I remember noticing the random crashing of the Mythtv GUI. I'd have to check the logs to make 100% sure.
As of now, I have remarked out the floppy disk line in the /etc/fstab and have unplugged the USB card reader from the motherboard header. I'll keep monitoring the situation...

Eric

_________________
KnoppMyth R5.5, Asus A8N-VM CSM (nvidia 6150 onboard video), AMD Athlon 64 dual-core 4200+, two 1GB sticks DDR 400, HD-3000 HDTV card, PVR-150 card, Iguanaworks RS-232 IR receiver/transmitter, Pioneer DVR-110 DVD burner


Top
 Profile  
 
 Post subject: Re: other details
PostPosted: Mon Sep 07, 2009 11:38 pm 
Offline
Joined: Sun Aug 28, 2005 7:07 pm
Posts: 821
Location: Melbourne, Australia
Did you start mythfrontend like I said, from the xterm and with debugging enabled?

_________________
*********************
LinHES 7.4
Australian Dragon
*********************


Top
 Profile  
 
 Post subject: Re: other details
PostPosted: Tue Sep 08, 2009 7:03 pm 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
manicmike wrote:
Did you start mythfrontend like I said, from the xterm and with debugging enabled?

I did try and it didn't work. I got the message "mythfrontend: cannot connect to X server" when I typed your mythfrontend line as root.
I tried in both an XTERM window sitting on the Fluxbox desktop and also by using a virtual terminal window (ALT-F1).

After pulling the USB plug wires on the card reader and commenting out the floppy drive lines in fstab, there have been no Mythtv GUI crashes. It's been about 24 hours thus far...

_________________
KnoppMyth R5.5, Asus A8N-VM CSM (nvidia 6150 onboard video), AMD Athlon 64 dual-core 4200+, two 1GB sticks DDR 400, HD-3000 HDTV card, PVR-150 card, Iguanaworks RS-232 IR receiver/transmitter, Pioneer DVR-110 DVD burner


Top
 Profile  
 
 Post subject:
PostPosted: Tue Sep 08, 2009 7:54 pm 
Offline
Joined: Wed Jul 25, 2007 7:56 pm
Posts: 103
Location: Arlington, VA, USA
Quote:
I did try and it didn't work. I got the message "mythfrontend: cannot connect to X server" when I typed your mythfrontend line as root.

Just FYI, I'm guessing you get that because X is running as the mythtv user, and you're trying to start mythfrontend as a different user. If you start mythfrontend from an xterm as the mythtv user, it should work, or at least start.

_________________
MBE/FE: R6, P4 2.8 GHz/2 GB/2 TB, GeForce 6200 512 MB, PVR-150, Cisco RNG-100 cable box
FE: R6, P4 2.0 GHz/1 GB, GeForce4 MX 420 64 MB, diskless netboot


Top
 Profile  
 
 Post subject: Re: other details
PostPosted: Tue Sep 08, 2009 9:05 pm 
Offline
Joined: Sun Aug 28, 2005 7:07 pm
Posts: 821
Location: Melbourne, Australia
neutron68 wrote:
I got the message "mythfrontend: cannot connect to X server" when I typed your mythfrontend line as root..


Why did you do it as root?

Why didn't you just do what I suggested?

_________________
*********************
LinHES 7.4
Australian Dragon
*********************


Top
 Profile  
 
 Post subject: Re: other details
PostPosted: Wed Sep 09, 2009 7:28 am 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
manicmike wrote:
neutron68 wrote:
I got the message "mythfrontend: cannot connect to X server" when I typed your mythfrontend line as root..


Why did you do it as root?

Why didn't you just do what I suggested?

Hi Mike, please note, that you did NOT say what user to log in as. I had to guess.
Since, nearly every maintenance action I've ever done with Knoppmyth was/is done as root, I concluded root was the user to use.
I will try your mythfrontend command again by logging in as user mythtv.

Update: The Mythtv GUI has not crashed since pulling the USB card reader and commenting out the floppy disk line in fstab - after about 36 hours.

Eric

_________________
KnoppMyth R5.5, Asus A8N-VM CSM (nvidia 6150 onboard video), AMD Athlon 64 dual-core 4200+, two 1GB sticks DDR 400, HD-3000 HDTV card, PVR-150 card, Iguanaworks RS-232 IR receiver/transmitter, Pioneer DVR-110 DVD burner


Top
 Profile  
 
 Post subject: log file thus far
PostPosted: Wed Sep 09, 2009 1:51 pm 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
The log file is already over 40,000 lines after only 6 hours!

Thus far, the log file is mostly full of the following line:
Code:
2009-09-09 14:47:50.089 /dev/cdrom No disc
2009-09-09 14:47:50.666 /dev/cdrom No disc
2009-09-09 14:47:51.243 /dev/cdrom No disc
2009-09-09 14:47:51.821 /dev/cdrom No disc
2009-09-09 14:47:52.398 /dev/cdrom No disc
2009-09-09 14:47:52.987 /dev/cdrom No disc
2009-09-09 14:47:53.571 /dev/cdrom No disc
2009-09-09 14:47:54.148 /dev/cdrom No disc
2009-09-09 14:47:54.726 /dev/cdrom No disc
2009-09-09 14:47:55.303 /dev/cdrom No disc
2009-09-09 14:47:55.880 /dev/cdrom No disc
2009-09-09 14:47:56.457 /dev/cdrom No disc
2009-09-09 14:47:57.048 /dev/cdrom No disc
2009-09-09 14:47:57.625 /dev/cdrom No disc

_________________
KnoppMyth R5.5, Asus A8N-VM CSM (nvidia 6150 onboard video), AMD Athlon 64 dual-core 4200+, two 1GB sticks DDR 400, HD-3000 HDTV card, PVR-150 card, Iguanaworks RS-232 IR receiver/transmitter, Pioneer DVR-110 DVD burner


Top
 Profile  
 
 Post subject: Re: other details
PostPosted: Wed Sep 09, 2009 6:45 pm 
Offline
Joined: Sun Aug 28, 2005 7:07 pm
Posts: 821
Location: Melbourne, Australia
neutron68 wrote:
Hi Mike, please note, that you did NOT say what user to log in as. I had to guess.


Not really. If anyone expects you to do something as root, then they will explicitly tell you. I said to pop up an xterm (which always runs as user mythtv) then run the commands. Sometimes making assumptions.... nah, I won't say it :-)

Generally, running gui programs as root is not allowed. If you really must, and know what you're doing, you can overcome this with sudo.

The message in the log file can be stopped in the short term by putting a disc in the drive, but if it persists after rebooting with no disc in it, a process is auto-starting and checking your drive twice a second. You can check processes with ps -ef or you could try (as root [see?]) lsof | grep cdrom. That may give you a process that's accessing your cd drive. You may have to replace cdrom with the real device name (e.g. scd0).

Mike

_________________
*********************
LinHES 7.4
Australian Dragon
*********************


Top
 Profile  
 
 Post subject: ps -ef
PostPosted: Thu Sep 10, 2009 8:11 pm 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
(as root) "ps -ef" barfed up a screen-full, including this suspicious line:
Code:
root      3642  3619  0 Sep07 ?        00:00:10 hald-addon-storage: polling /dev/hdc (every 2 sec)
Does this tell us anything? I appears that everyone's Knoppmyth box is polling the cdrom drive MANY times per minute by default.

(as root) "lsof | grep cdrom" yielded nothing at all - not one character.

Update: It's been 72 hours and still no GUI crashes since my above noted changes. I have a feeling I found the problem. Time will tell...

Eric

_________________
KnoppMyth R5.5, Asus A8N-VM CSM (nvidia 6150 onboard video), AMD Athlon 64 dual-core 4200+, two 1GB sticks DDR 400, HD-3000 HDTV card, PVR-150 card, Iguanaworks RS-232 IR receiver/transmitter, Pioneer DVR-110 DVD burner


Top
 Profile  
 
 Post subject:
PostPosted: Fri Sep 11, 2009 5:13 am 
Offline
Joined: Wed Jul 25, 2007 7:56 pm
Posts: 103
Location: Arlington, VA, USA
"hald" appears to be this. In my case, I have the following lines:
Code:
[root]# ps -ef | grep hald
hal       4294  4272  0 Sep01 ?        00:00:05 /usr/sbin/hald --daemon=no --use-syslog
root      5033  4294  0 Sep01 ?        00:00:00 hald-runner
root      5084  5033  0 Sep01 ?        00:00:00 hald-addon-input: Listening on /dev/input/event3 /dev/input/event2 /dev/input/event1
hal       5088  5033  0 Sep01 ?        00:00:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket
root      5204  5033  0 Sep01 ?        00:01:44 hald-addon-storage: polling /dev/sr0 (every 2 sec)
root      5206  5033  0 Sep01 ?        00:02:05 hald-addon-storage: polling /dev/sr1 (every 2 sec)

I notice unexpected behavior with a USB card reader on my Windows box - the card reader itself is what can be ejected, rather than individual SD or CF cards. So maybe your box senses "a USB device is plugged in" but goes to look for media in it and doesn't find any. That's what these messages look like:
Code:
mount: No medium found
2009-09-07 17:32:06.059 Failed to mount /dev/sdb.
mount: No medium found
2009-09-07 17:32:06.215 Failed to mount /dev/sdc.
mount: No medium found
2009-09-07 17:32:06.371 Failed to mount /dev/sdd.
mount: No medium found
2009-09-07 17:32:06.529 Failed to mount /dev/sde.

Still doesn't explain why it says "/dev/cdrom" in your other logs or why your GUI crashed... but hey, if it works it works, right :-)

And if you really want to use that card reader device, you at least have an idea of where to start troubleshooting now.

_________________
MBE/FE: R6, P4 2.8 GHz/2 GB/2 TB, GeForce 6200 512 MB, PVR-150, Cisco RNG-100 cable box
FE: R6, P4 2.0 GHz/1 GB, GeForce4 MX 420 64 MB, diskless netboot


Top
 Profile  
 
 Post subject: don't need card reader
PostPosted: Sat Sep 12, 2009 10:04 am 
Offline
Joined: Tue Mar 28, 2006 8:26 pm
Posts: 804
Location: Minneapolis, MN
No, I don't really need the card reader - especially if it makes the KM box malfunction! I just plugged it in because it was there. I didn't expect it to have any effect on the machine. I was WRONG! :)

Now, that we know it is a problem, it is going to stay unplugged!

Update: 96 hours without crashing - no card reader ...

_________________
KnoppMyth R5.5, Asus A8N-VM CSM (nvidia 6150 onboard video), AMD Athlon 64 dual-core 4200+, two 1GB sticks DDR 400, HD-3000 HDTV card, PVR-150 card, Iguanaworks RS-232 IR receiver/transmitter, Pioneer DVR-110 DVD burner


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 16 posts ] 
Go to page 1, 2  Next



All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 15 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu