<div dir="ltr">On Wed, Jun 12, 2013 at 4:36 AM, Stephen Worthington <span dir="ltr"><<a href="mailto:stephen_agent@jsw.gen.nz" target="_blank" class="cremed">stephen_agent@jsw.gen.nz</a>></span> wrote:<br><div class="gmail_extra">
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Tue, 11 Jun 2013 21:06:09 -0700, you wrote:<br>
<br>
>Tuesday afternoon at 1:30pm, mythtv is set to record 2 shows, and every<br>
>week when I come home Tuseday evening, I find that the backend is stuck:<br>
>the backend can't connect to it, and later scheduled recordings didn't<br>
>happen.<br>
>After killing and restarting the backend so that the frontend can connect<br>
>to it again and get the list of recordings, I see one recording shows up<br>
>with the "missing file" X next to it, while the other shows up as a 0 sized<br>
>recording. If I try to play the 0-sized one, the backend seems to hang<br>
>again.<br>
>I can manually tune to the channels in question just fine, and I've<br>
>recorded two things simultaneously from those two channels too. There's<br>
>nothing in the log that indicates any kind of failure. Any idea why those<br>
>same scheduled recording would always cause the backend to hang?<br>
<br>
</div></div>What version of MythTV are you using?</blockquote><div><br></div><div style>This is 0.25 (Mythbuntu, in case that matters).</div><div style><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I used to get a similar problem<br>
to that on, IIRC, 0.24. I upgraded to 0.25 and then quickly to 0.26,<br>
so I am not sure if 0.25 ever did it. It was a deadlock situation,<br>
and I tended to get it at the same time each week, but it took more<br>
than two programs at once to trigger it for me.</blockquote><div><br></div><div style>I regularly record 2 or 3 programs at once without any issues. The case I described above is the only one that consistently reproduces the problem.</div>
<div style> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> In 0.26, I can still<br>
get a similar problem, but instead of a deadlock, mythbackend detects<br>
the lockup and restarts itself. On restart, it records OK. This is<br>
much better than having it stop recording, but I still miss a couple<br>
of minutes of recordings due to the time mythbackend takes to restart.<br>
<br>
In my case, if I already had recordings running at the time of the<br>
deadlock, those recordings would continue and end normally, but any<br>
new recordings would never start after that. If it is like my<br>
problem, you may be able to prevent it from happening by getting one<br>
or other of the recordings to start a minute or two earlier.<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" class="cremed">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank" class="cremed">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</blockquote></div><br></div></div>