[mythtv-users] mythbackend --printsched timeout

David Engel david at istwok.net
Tue May 18 22:51:01 UTC 2010

On Tue, May 18, 2010 at 03:13:17PM -0400, Daniel Kristjansson wrote:
> On Tue, 2010-05-18 at 13:10 -0400, Brian Long wrote:
> > I have a script I use to determine basic backend health.   One of the
> > hourly commands I run is "mythbackend --printsched | head -50" and I
> > search for error strings.  Once or twice a day I will receive the
> > following error.
> > 
> > 2010-05-18 10:00:10.346 MythSocket(8846cc8:8): readStringList: Error,
> > timed out after 7000 ms.
> > 
> > Any ideas what causes this?  I've seen it with 0.22-fixes and
> > 0.23-fixes.
> I don't know off the top of my head, but my guess is the scheduler
> is running and that is preventing --printsched from obtaining the
> schedule before the 7 second timeout expires. Some backend queries
> use a 30 second timeout when the query might take a long time to
> complete, but since printsched is mainly intended for debugging
> this probably wasn't considered necessary, seven seconds is the
> default.

That shouldn't be the case.  The --printsched option simply retrieves
the main list from the scheduler.  Since changes in Fall '06, that
list is only locked for very short periods of time so --printsched
should always return quickly.  It would probably help to the logs from
both the master backend and the backend running --printsched.

David Engel
david at istwok.net

More information about the mythtv-users mailing list