[mythtv] Upgraded to r12971, now have MythSocket errors every 10s
knowledgejunkie at gmail.com
Thu Mar 8 12:02:01 UTC 2007
On 08/03/07, Chris Pinkham <cpinkham at bc2va.org> wrote:
> * On Thu Mar 08, 2007 at 09:27:27AM +0000, Nick Morrott wrote:
> > I just upgraded from r12830 to last night's r12971. I now find my
> > backend log reporting MythSocket errors every 10 seconds, irrespective
> > of whether a frontend is connected or not. uPNP is disabled also:
> > 2007-03-08 09:21:45.449 Unknown socket closing
> > 2007-03-08 09:21:45.455 MythSocket(8b10bd0:-1): writeStringList:
> > Error, socket went unconnected.
> > Any ideas? I've restarted the backend with no change in behaviour, and
> > am hesitant to turn off socket logging in case it's something
> > important (currently using -v important). I will file a ticket if
> > deemed suitable.
> Not happening here. You should run "mythbackend -v network" and
> see if that gives any clues.
I took a lot at the log output with -v network, and it was giving this
error every 10s:
2007-03-08 11:41:25.455 Unknown socket closing
2007-03-08 11:41:25.464 MythSocket(8b5d710:-1): writeStringList:
Error, socket went unconnected.
2007-03-08 11:41:35.448 read <- 38 21 MYTH_PROTO_VERSION 32
2007-03-08 11:41:35.451 write -> 38 13 REJECT:33
Having shutdown my mythbackends/frontends as normal before installing
the new build, I was wondering whether the fact that mythlcdserver did
not shut down could be causing this protocol mismatch? When the first
install was carried out, it mythlcdserver was still running in the
background. I killed mythlcdserver the second time around,
reinstalled, started mythbackend, and now no messages at all. I've
never seen this happen before, even when compiling after there's been
a protocol bump.
Thanks for the pointer,
MythTV Official wiki:
MythTV users list archive:
"An investment in knowledge always pays the best interest." - Benjamin Franklin
More information about the mythtv-dev