LinHES Forums
http://forum.linhes.org/

Random crash every night
http://forum.linhes.org/viewtopic.php?f=17&t=13069		 Page 1 of 1
Author:  nlin1996 [ Fri Dec 22, 2006 7:51 am ]
Post subject:  Random crash every night
Looking for some help here. I've tried running both RC57 and now R5D1. Everything works great, recording shows, playing back shows for a while.

Sometime during the night though the whole box freezes and I have to push reset. I can't recover with Ctrl-Alt-backspace or ESC.

The only thing interesting I see in the log files is that it looks like commercial flagging happened shortly before the last log in the mythbackend.log file. I also see errors in there reading:"ac-tex damaged" and "warning MVs not available".

Anybody know what these errors mean or how to fix them?

I'm getting frustrated that this crashes every night.

I'm using a PVR-150 tuner card

BIOSTAR NF325-A7 Socket 754 NVIDIA nForce3 250 ATX AMD motherboard

AMD Sempron 64 2800+ Palermo 1.6GHz Socket 754 Processor

WINTEC AMPO 512MB 184-Pin DDR SDRAM DDR 400 (PC 3200) Desktop Memory

Western Digital Caviar SE WD3200JB 320GB 7200 RPM IDE Ultra ATA100 Hard Drive
Author:  mjl [ Fri Dec 22, 2006 12:32 pm ]
Post subject: 
Hi,

If you have another computer, use putty and ssh into your myth (at least try) as it may only be the frontend that is having a problem, If com flag seems to be a problem try turning it off and see if it still has the issue. You may experiment with disabling some items in the setup menus to see if they affect your problem.

most of the logs files are in /var/log so you may try looking at the ends of those for additional information. Try something like:
# tail -100 /var/log/messages as that would show the last 100 lines of that log.

Mike
Author:  thornsoft [ Fri Dec 22, 2006 12:38 pm ]
Post subject:  Re: Random crash every night
nlin1996 wrote:
The only thing interesting I see in the log files is that it looks like commercial flagging happened shortly before the last log in the mythbackend.log file.


So disable the commflag jobs in the backend setup. See if it runs ok for a few days. That'll let you rule the commflag in or out.
This won't fix it, but at least you'll know more than you do now.

If commflag is the culprint, follow mjl's advice and run a session from another computer. Leave commflag off, and run it manually in the remote session, when you're ready to go to bed. There may be clues in the morning, if it crashes. You'll see last output in the terminal window. Make sure you've got a nice big scrollback buffer.
Page 1 of 1 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/