[mythtv-users] Linux Kernel or Myth error?

[Steve Smith]

OK,

So I'm trying to figure out why my backend won't go to sleep... but
that's the bigger story.

Whilst doing this I've come across a very strange symptom:

1) Last night I was using my MediaMVP to watch a recording (It's on
192.168.2.10)
2) This morning I switched it off (by unplugging it).
3) Now (several hours later) I see the following:

a) The Mythbackend hasn't noticed it should be idle and to initiate
the shutdown timer (side issue).
b) netstat -an     STILL SHOWS the MVP as CONNECTED!!!
tcp   0    0   192.168.2.26:6543   192.168.2.10:2130      ESTABLISHED

(26 = the mythbox 10 = the MVP)

c) I have backend log full of the messages below:


2008-03-19 16:45:37.334 MythSocket(8452420:-1): writeStringList:
Error, socket went unconnected.
2008-03-19 16:46:37.229 MainServer::HandleAnnounce Playback
2008-03-19 16:46:37.230 adding: eddie as a client (events: 0)
2008-03-19 16:46:37.233 MainServer::HandleAnnounce FileTransfer
2008-03-19 16:46:37.237 adding: eddie as a remote file transfer
2008-03-19 16:46:37.240 RemoteFile::openSocket(control socket):
			Could not connect to server "" @ port -1
2008-03-19 16:46:37.241 RemoteFile::openSocket(file data socket):
			Could not connect to server "" @ port -1
2008-03-19 16:46:37.243 RingBuffer::RingBuffer(): Failed to open remote file ()
2008-03-19 16:46:37.260 MythSocket(8277968:-1): writeStringList:
Error, socket went unconnected.
2008-03-19 16:47:37.261 MainServer::HandleAnnounce Playback
2008-03-19 16:47:37.319 adding: eddie as a client (events: 0)


So is this a Myth or a Kernel bug, the MVP was switched off several
hours ago so I'd expect the connection should have been dropped by
now.

Anyone?

Cheers

Steve