[mythtv-users] MythSocket writeStringList: Error, called with unconnected socket.
Michael T. Dean
mtdean at thirdcontact.com
Wed Aug 26 17:21:21 UTC 2009
On 08/26/2009 06:15 AM, Panachoi wrote:
> I've been getting lots of these lately, suddenly, after upgrading
> trunk (21509). They usually look something like this, and it seems to
> happen more often when actually watching live TV:
>
> 2009-08-26 11:56:53.739 EITScanner (2): Started passive scan.
> 2009-08-26 11:57:01.387 PID 0x6e status: Encrypted
> 2009-08-26 11:57:02.196 PID 0x65 status: Encrypted
> 2009-08-26 11:57:07.114 EITScanner (1): Added 60 EIT Events
> 2009-08-26 11:57:07.117 Reschedule requested for id -1.
> 2009-08-26 11:57:07.163 Scheduled 8 items in 0.0 = 0.01 match + 0.03 place
> 2009-08-26 11:57:07.167 MythSocket(8cf08a0:-1): writeStringList:
> Error, called with unconnected socket.
> 2009-08-26 11:57:07.169 MythSocket(8cf08f0:-1): writeStringList:
> Error, called with unconnected socket.
> 2009-08-26 11:57:07.170 MythSocket(ffffffffab20b030:-1):
> writeStringList: Error, called with unconnected socket.
> 2009-08-26 11:57:07.170 MythSocket(ffffffffab20b0b8:-1):
> writeStringList: Error, called with unconnected socket.
> 2009-08-26 11:57:07.173 MythSocket(ffffffffab21abf8:-1):
> writeStringList: Error, called with unconnected socket.
> 2009-08-26 11:57:07.177 MythSocket(ffffffffab217128:-1):
> writeStringList: Error, called with unconnected socket.
> 2009-08-26 11:57:07.181 MythSocket(ffffffffab2102c8:-1):
> writeStringList: Error, called with unconnected socket.
> 2009-08-26 11:57:07.190 MythSocket(ffffffffab20f840:-1):
> writeStringList: Error, called with unconnected socket.
> 2009-08-26 11:57:07.196 MythSocket(ffffffffb2430040:-1):
> writeStringList: Error, called with unconnected socket.
>
> Have no idea why this is suddenly happening (problem in trunk?)
>
> Thanks for pointers.
This is a known issue that Daniel K is currently working on. It exists
for both 0.21-fixes and trunk users with a specific system/kernel
configuration. This issue is typically only seen on new distros (those
which are using the affected configuration) and seems to be easier to
trigger with trunk.
So, basically, just watch the commit messages from daniel for mention of
changes that fix issues with socket handling. (Note he's also been
referencing #6516 in his commits.)
Mike
More information about the mythtv-users
mailing list