[mythtv-users] Frequent backend crashing

[Nick Morrott]

On 21/08/07, James Cummings <cummings.james at gmail.com> wrote:

> of the problem from my point of view.  On my box the backend can be still
> running and it decides not to lock onto a channel even though signal is
> strong.  In liveTV it just vgives you the option to wait longer, etc. but
> when it is meant to be recording it just doesn't record anything, creates a
> 0 byte file which then the frontend is not able to find.  Restarting the
> backend in these cases solves the problem, it will lock on the channel right
> away, but the cron script won't help, because the backend is technically
> running.
>
> My logs when this happens look something like:
>
> =======
> 2007-08-17 20:21:38.440 EITScanner: Now looking for EIT data on multiplex of
> channel 701
> QDateTime::fromString: Parameter out of range
> QSocketDevice::writeBlock: Invalid socket
> QDateTime::fromString: Parameter out of range
> QSocketDevice::writeBlock: Invalid socket
> 2007-08-17 20:26:50.015 EITScanner: Now looking for EIT data on multiplex of
> channel 11
> QDateTime::fromString: Parameter out of range
> QSocketDevice::writeBlock: Invalid socket
> 2007-08-17 20:30:02.928 TVRec(1): Changing from None to RecordingOnly
> 2007-08-17 20:30:02.944 TVRec(1): HW Tuner: 1->1
> 2007-08-17 20:30:02.952 DVBChan(0) Error: Tune(): Setting Frontend tuning
> parameters failed.
>                         eno: No such device (19)
> 2007-08-17 20:30:02.953 DVBChan(0) Error: SetChannelByString(13): Tuning to
> frequency.
> 2007-08-17 20:30:02.953 TVRec(1) Error: Failed to set channel to 13.
> Reverting to kState_None

I think you have problems with your DVB capture card and video source
setup, which will need to be fixed in mythtv-setup.

-- 
Nick

MythTV Official wiki:
http://mythtv.org/wiki/
MythTV users list archive:
http://www.gossamer-threads.com/lists/mythtv/users

"An investment in knowledge always pays the best interest." - Benjamin Franklin