Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Users

Entering Watch Recordings causes slave backend to disconnect

 

 

MythTV users RSS feed   Index | Next | Previous | View Threaded


james.orr7 at gmail

Nov 23, 2009, 9:36 PM

Post #1 of 5 (1081 views)
Permalink
Entering Watch Recordings causes slave backend to disconnect

My slave backend appears to be disconnecting as I enter the Watch Recordings
screen.

Here is the message I get on the master backend log ...

2009-11-24 00:31:25.582 MainServer::ANN Monitor
2009-11-24 00:31:25.596 adding: frontend1 as a client (events: 0)
2009-11-24 00:31:25.633 MythSocket(8282430:39): readStringList: Error, timed
out after 30000 ms.
2009-11-24 00:31:25.657 Slave backend: james-computer no longer connected
2009-11-24 00:31:25.667 Reschedule requested for id 0.
2009-11-24 00:31:25.668 PlaybackSock::SendReceiveStringList(): No response.
2009-11-24 00:31:25.717 MainServer::HandleQueryRecordings()
Could not fill program info from backend
2009-11-24 00:31:25.741 MainServer, Warning: Unknown socket closing
MythSocket(0x8230150)
2009-11-24 00:31:25.758 MythSocket(8230150:-1): writeStringList: Error,
socket went unconnected.
We wrote 0 of 96216 bytes with 1 errors

I am running 0.22 build 22824 (gentoo ebuild 0.22_p22824-r1.ebuild).


james.orr7 at gmail

Nov 24, 2009, 6:33 AM

Post #2 of 5 (1033 views)
Permalink
Re: Entering Watch Recordings causes slave backend to disconnect [In reply to]

On Tue, Nov 24, 2009 at 12:36 AM, James Orr <james.orr7 [at] gmail> wrote:

> My slave backend appears to be disconnecting as I enter the Watch
> Recordings screen.
>
> Here is the message I get on the master backend log ...
>
> 2009-11-24 00:31:25.582 MainServer::ANN Monitor
> 2009-11-24 00:31:25.596 adding: frontend1 as a client (events: 0)
> 2009-11-24 00:31:25.633 MythSocket(8282430:39): readStringList: Error,
> timed out after 30000 ms.
> 2009-11-24 00:31:25.657 Slave backend: james-computer no longer connected
> 2009-11-24 00:31:25.667 Reschedule requested for id 0.
> 2009-11-24 00:31:25.668 PlaybackSock::SendReceiveStringList(): No response.
> 2009-11-24 00:31:25.717 MainServer::HandleQueryRecordings()
> Could not fill program info from backend
> 2009-11-24 00:31:25.741 MainServer, Warning: Unknown socket closing
> MythSocket(0x8230150)
> 2009-11-24 00:31:25.758 MythSocket(8230150:-1): writeStringList: Error,
> socket went unconnected.
> We wrote 0 of 96216 bytes with 1 errors
>
> I am running 0.22 build 22824 (gentoo ebuild 0.22_p22824-r1.ebuild).
>
>
Anybody have any ideas? It does record stuff, as long as I don't go into
the Watch Recordings screen which causes the above timeout and disconnect.


james.orr7 at gmail

Nov 24, 2009, 9:45 AM

Post #3 of 5 (1034 views)
Permalink
Re: Entering Watch Recordings causes slave backend to disconnect [In reply to]

On Tue, Nov 24, 2009 at 9:33 AM, James Orr <james.orr7 [at] gmail> wrote:

> On Tue, Nov 24, 2009 at 12:36 AM, James Orr <james.orr7 [at] gmail> wrote:
>
>> My slave backend appears to be disconnecting as I enter the Watch
>> Recordings screen.
>>
>> Here is the message I get on the master backend log ...
>>
>> 2009-11-24 00:31:25.582 MainServer::ANN Monitor
>> 2009-11-24 00:31:25.596 adding: frontend1 as a client (events: 0)
>> 2009-11-24 00:31:25.633 MythSocket(8282430:39): readStringList: Error,
>> timed out after 30000 ms.
>> 2009-11-24 00:31:25.657 Slave backend: james-computer no longer connected
>> 2009-11-24 00:31:25.667 Reschedule requested for id 0.
>> 2009-11-24 00:31:25.668 PlaybackSock::SendReceiveStringList(): No
>> response.
>> 2009-11-24 00:31:25.717 MainServer::HandleQueryRecordings()
>> Could not fill program info from backend
>> 2009-11-24 00:31:25.741 MainServer, Warning: Unknown socket closing
>> MythSocket(0x8230150)
>> 2009-11-24 00:31:25.758 MythSocket(8230150:-1): writeStringList: Error,
>> socket went unconnected.
>> We wrote 0 of 96216 bytes with 1 errors
>>
>> I am running 0.22 build 22824 (gentoo ebuild 0.22_p22824-r1.ebuild).
>>
>>
> Anybody have any ideas? It does record stuff, as long as I don't go into
> the Watch Recordings screen which causes the above timeout and disconnect.
>

Well, no idea what the problem was but rebooting the slave backend fixed
it. I will get much scorn from the wife because of this as I always tell
her the first thing to do when things aren't working right is reboot and I
didn't do it here ....

During the reboot process it did hang at the "Killing ALSA processes" stage,
so maybe it was something to do with that???


mtdean at thirdcontact

Nov 24, 2009, 10:06 AM

Post #4 of 5 (1032 views)
Permalink
Re: Entering Watch Recordings causes slave backend to disconnect [In reply to]

On 11/24/2009 12:45 PM, James Orr wrote:
> On Tue, Nov 24, 2009 at 9:33 AM, James Orr wrote:
>
>> On Tue, Nov 24, 2009 at 12:36 AM, James Orr wrote:
>>
>>> My slave backend appears to be disconnecting as I enter the Watch
>>> Recordings screen.
>>>
>>> Here is the message I get on the master backend log ...
>>>
>>> 2009-11-24 00:31:25.582 MainServer::ANN Monitor
>>> 2009-11-24 00:31:25.596 adding: frontend1 as a client (events: 0)
>>> 2009-11-24 00:31:25.633 MythSocket(8282430:39): readStringList: Error,
>>> timed out after 30000 ms.
>>> 2009-11-24 00:31:25.657 Slave backend: james-computer no longer connected
>>> 2009-11-24 00:31:25.667 Reschedule requested for id 0.
>>> 2009-11-24 00:31:25.668 PlaybackSock::SendReceiveStringList(): No
>>> response.
>>> 2009-11-24 00:31:25.717 MainServer::HandleQueryRecordings()
>>> Could not fill program info from backend
>>> 2009-11-24 00:31:25.741 MainServer, Warning: Unknown socket closing
>>> MythSocket(0x8230150)
>>> 2009-11-24 00:31:25.758 MythSocket(8230150:-1): writeStringList: Error,
>>> socket went unconnected.
>>> We wrote 0 of 96216 bytes with 1 errors
>>>
>>> I am running 0.22 build 22824 (gentoo ebuild 0.22_p22824-r1.ebuild).
>>>
>> Anybody have any ideas? It does record stuff, as long as I don't go into
>> the Watch Recordings screen which causes the above timeout and disconnect.
>>
> Well, no idea what the problem was but rebooting the slave backend fixed
> it. I will get much scorn from the wife because of this as I always tell
> her the first thing to do when things aren't working right is reboot and I
> didn't do it here ....
>
> During the reboot process it did hang at the "Killing ALSA processes" stage,
> so maybe it was something to do with that???

Is this trunk or 0.22-fixes? There's an uninvestigated rumor that
there's a massive file handle leak in at least trunk where the file
handles are to the ALSA control device.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


james.orr7 at gmail

Nov 24, 2009, 11:28 AM

Post #5 of 5 (1026 views)
Permalink
Re: Entering Watch Recordings causes slave backend to disconnect [In reply to]

On Tue, Nov 24, 2009 at 1:06 PM, Michael T. Dean <mtdean [at] thirdcontact>wrote:

> > During the reboot process it did hang at the "Killing ALSA processes"
> stage,
> > so maybe it was something to do with that???
>
>
> Is this trunk or 0.22-fixes? There's an uninvestigated rumor that
> there's a massive file handle leak in at least trunk where the file
> handles are to the ALSA control device.
>

I believe the gentoo ebuilds pull from 0.22-fixes.

I had a different problem with my HDHR in 22860 which is detailed in another
thread (http://mythtv.org/pipermail/mythtv-users/2009-November/272027.html).
Without a solution to that problem I downgraded to the next lower version in
an ebuild, 22824 and that's when this problem showed up. It's possible the
problem I had with 22860 was the source of this problem as I did not reboot
the system, only restarted the backend after the downgrade.

MythTV users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.