[mythtv-users] Frontend crash after 2-3 hours of live tv - Any suggestions?
Christian Husemann
Christian.Husemann at Sun.COM
Tue Mar 21 18:04:18 UTC 2006
William schrieb:
>
>
>
>>William wrote:
>>
>>
>>>I am running 0.19 release-fixes compiled on a FC2 system. After
>>>watching live tv for a while the frontend will just freeze.
>>>
>>>
>>I have not
>>
>>
>>>been able to figure out what to look for on this issue. When the
>>>system fails, the hard drive light will run solid on for a
>>>
>>>
>>good 3-4
>>
>>
>>>minutes. It almost looks like it may be updateing the allocation
>>>tables or trying to fix an error. The file system is a pair of ide
>>>drives in a LVM formatted with XFS. I dont think its an issue with
>>>file size although the live tv files are usually ~4GB in size when
>>>things fail. Any suggestions on what to check?
>>>
>>>TIA,
>>>Bill
>>>
>>>
>>>_______________________________________________
>>>mythtv-users mailing list
>>>mythtv-users at mythtv.org
>>>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>>>
>>>
>>Bill,
>>
>>what about mythbackend.log, messages ....? Also imho your livetv file
>>should be a ringbuffer and should grow to that size.
>>
>>Just my 2c.
>>
>>Christian
>>
>>
>
>Thanks for responding. In 0.19 the live tv function writes a file just like
>any other recording. ASAIK the backend log shows nothing out of the
>ordinary. I may have to recompile with debugging enabled and try to get some
>log data. I was hoping to get some suggestions on where to look. Programs
>record just fine, even long ones like football games are fine. They play
>back fine too. Only live tv is affected. This has started since the changes
>to live tv from a buffer to a file. My suspicion is that tv is playing
>backing slightly faster than its recording and at some point the frontend
>requests data that is not there yet and hangs at that point. As a test, I
>had the wife pause live tv for 30-60 seconds to build up a buffer but I just
>realized that the recording ends and starts with a fresh filename when each
>show ends. Thats probably not going to help.
>
>
>_______________________________________________
>mythtv-users mailing list
>mythtv-users at mythtv.org
>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
Bill,
why a debug compile? My ordinary mythbackend already offers everything
you may need:
legolas ~ # mythbackend -v help
Verbose debug levels.
Accepts any combination (separated by comma) of:
all - ALL available debug output
important - Errors or other very important messages
general - General info
record - Recording related messages
playback - Playback related messages
channel - Channel related messages
osd - On-Screen Display related messages
file - File and AutoExpire related messages
schedule - Scheduling related messages
network - Network protocol related messages
commflag - Commercial Flagging related messages
audio - Audio related messages
libav - Enables libav debugging
jobqueue - JobQueue related messages
siparser - Siparser related messages
eit - EIT related messages
vbi - VBI related messages
database - Display all SQL commands executed
dsmcc - DSMCC carousel related messages
mheg - MHEG debugging messages
timestamp - Conditional data driven messages
none - NO debug output
The default for this program appears to be: '-v important,general'
Most options are additive except for none, all, and important.
These three are semi-explicit and take precedence over any
prior options given. You can however use something like
'-v none,jobqueue' to get only JobQueue related messages
and override the default verbosity level.
The additive options may also be subtracted from 'all' by
prefixing them with 'no', so you may use '-v all,nodatabase'
to view all but database debug messages.
Some debug levels may not apply to this program.
legolas ~ #
You may start your backend with the record, playback and file option for
a good start.
Again, just my 2c
PS: Why the hack no ringbuffer anymore???
More information about the mythtv-users
mailing list