[mythtv-users] Re: mythbackend v.14 dies after an hour?

[Dan Fleming]

THANK YOU!

I was having a hard time figuring out if this was a MythTV issue or an
ivtv issue.  The MythTV system that was having this problem is a
diskless slave backend with a PVR-350.  The partition it was caching its
live-tv only had about 2GB left on it.  I'm guesing that since it is
using nfs as its root partion MythTV was confused about how much free
space it had.

After moving the live-tv buffer to a disk with more space it ran for 2
hours before dying.  However, at least it indicated an issue with ivtv!
Now at least I can provide the folks on the ivtv list better
information.

Thanks again Dennis your reply definitly pointed me in the right
direction.

---Dan

On Tue, Apr 20, 2004 at 03:27:25PM -0400, Dennis Hand wrote:
> Is anyone aware of an issue with mythbackend simply dying after an hour? 
> 
> I've been able to duplicate this consistantly. Basically within a 
> minute or so of an hour mythbackend just dies which causes the frontend 
> to display a black screen. Below are the frontend logs from "No 
> response from control socket." the lines are duplicated over and over 
> again. 
> 
> 2004-04-20 07:51:45 Changing from None to WatchingLiveTV 
> 2004-04-20 08:49:25 ReadStringList timeout (quick). 
> 2004-04-20 08:49:26 RemoteFile::Read(): No response from control socket. 
> 2004-04-20 08:49:26 RemoteFile::Read() failed in 
> RingBuffer::safe_read(). 
> 2004-04-20 08:49:26 Error writing stringlist 
> 2004-04-20 08:49:26 RemoteFile::Read() failed in 
> RingBuffer::safe_read(). 
> 
> ---Dan 
> 
> 
> 
>     Just a guess here but it looks like your ringbuffer might be full. What is it set at, the default of 5GB?
> 
> Dennis