[mythtv] [mythtv-commits] mythtv commit: r22955 - in trunk by danielk

[Jim Stichnoth]

On Mon, Dec 7, 2009 at 11:00 AM, Jim Stichnoth <stichnot at gmail.com> wrote:
> On Mon, Dec 7, 2009 at 4:50 AM, Daniel Kristjansson
> <danielk at cuymedia.net> wrote:
>> This problem has been reported to me, but I was unable to reproduce
>> with my current setup and current trunk. The initial commit had a
>> loop, but I thought had already fixed it. If this still occurs with
>> trunk can you try something for me?
>>
>> In RemoteSendEvent() replace gContext->IsMasterBackend()
>> with gContext->IsBackend(), that shouldn't cause any problems
>> and might fix the problem.
>
> This appears to fix the problem on my system.  Filesize updates are
> now being made once every 2-10 seconds, rather than every 20-30ms.  I
> tested r22962 with and without this one-line change.
>
> I'll report back if I see any more related problems, for example when
> I get a chance to test Live TV, and also the problem I noted with
> zero-length recordings.

This problem popped up again for me yesterday, running r22969.  At
3:34pm, an HD-PVR recording started on the slave backend and completed
at 5:01pm.  The logs on the slave backend (-v important,general) show
nothing remarkable during the recording or at any later time.  On the
master backend (-v important,general), problems started showing up at
4:46pm, beginning with messages like this repeated every 10 seconds:

2009-12-09 16:46:17.111 MythSocket(a00ce60:60): writeStringList:
Error, No data  written on writeBlock (937 errors)
2009-12-09 16:46:27.120 MythSocket(a00ce60:60): writeStringList:
Error, No data  written on writeBlock (937 errors)
2009-12-09 16:46:37.130 MythSocket(a00ce60:60): writeStringList:
Error, No data  written on writeBlock (937 errors)

These messages stopped around 5:01pm when the slave backend recording
completed, but started up again at 6:45pm when a frontend started
watching a recording.  At 8:00pm when more recordings and commflagging
started, additional kinds of errors appeared, for example:

2009-12-09 20:00:49.212 MainServer, Warning: Unknown socket closing
MythSocket(0xffffffffa9c1c880)
2009-12-09 20:00:49.220 MythSocket(ffffffffa9c1c298:-1):
writeStringList: Error, socket went unconnected.
                        We wrote 0 of 21 bytes with 1 errors

All these errors continued until all recording and playback finished
around 11:40pm, briefly popped up at 4am when I restarted the slave
backend, and disappeared altogether right after that when I restarted
the master backend.  Usually the messages were 1 or 2 seconds apart in
the log instead of 10 seconds.

The frontends were affected during this storm.  Symptoms included not
being able to bring up the Watch Recordings screen, failure to start
playing a program when Watch Recordings finally came up, and one
instance of playback suddenly stopping mid-program.

One other thing might be worth mentioning.  In looking through the
logs, I realized that I also ran a couple of lossless transcode jobs
on the master backend, one from 3:37pm to 3:42pm and another from to
8:16pm to 8:18pm.  It seems unlikely to be related, but just in
case...

I'd like to help get to the bottom of this.  Are there extra -v
arguments I should add to the backends or frontends that would shed
more light?  Any code modifications to try out?

Jim