[mythtv-users] Same backend bug/issue in 0.18 from 0.17: backend
running but doesn't work!
JY
jyoun24 at gmail.com
Tue Apr 26 23:22:49 UTC 2005
Sorry I don't have a solution, but I have this exact same problem.
The backend process is still running, but the frontend can't watch
live tv, can't browse recordings, can't browse upcoming shows, etc.
At this point all I can do is to restart the backend. I was going to
upgrade to 0.18 to see if that fixed it so I'm discouraged to hear you
have the same problem w/0.18. This would happen at least once a day,
occasionally it would not happen for a couple of days. It's been
happening since I installed myth about 3 weeks ago.
Are you using a remote front end? I've had my remote frontend up only
for the past 2 days, but so far it hasn't hung the backend yet, using
the remote front-end exclusively. I'll have to run it a bit longer to
see if thats a fluke or not.
Does anybody have any suggestions on how to debug this problem if it persists?
On 4/26/05, mythtv-users at fastdruid.co.uk <mythtv-users at fastdruid.co.uk> wrote:
> I have an issue with 0.18, exactly the same as I had with 0.17 where the
> backend stops
> working, it's still running but it doesn't record and wont play,
>
> The only near warning/error is by the start of a program that failed to
> record is:
>
> 2005-04-26 13:39:02.040 backend still changing state, waiting..
>
> The backend is still running but it doesn't schedule or play anything.
>
> *Exactly* the same as it did on 0.17
>
> Then the frontend times out with repeats of the following 4 lines.
>
> 2005-04-26 18:09:13.266 Connecting to backend server: 192.168.1.15:6543 (try
> 1 of 5)
> 2005-04-26 18:09:33.268 ReadStringList timeout (quick).
> 2005-04-26 18:09:33.268 Unexpected response to MYTH_PROTO_VERSION:
> 2005-04-26 18:09:37.894 All Programs
>
> I restarted the backend and the two programs that were meant to be recording
> suddenly
> kicked in and the frontend worked again.
>
> Any ideas please? I have no idea even where to start, I'm at the stage of
> setting up a cron
> job to check for that message and restart but that is just a bodge.
>
> Thanks
>
> David
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
>
More information about the mythtv-users
mailing list