[mythtv-users] Really strange one...
matt at mossholder.com
Fri Nov 18 21:07:20 UTC 2011
On Fri, Nov 18, 2011 at 3:37 PM, Matt Mossholder <matt at mossholder.com>wrote:
> So, I decided to rebuild my backend with Scientific Linux 61. I've enabled
> the epel, atrpms and atrpms-testing repos, and installed mythtv-backend,
> mythtv-setup, mythtv-docs, mythweb and mythtv-common.
> After running mythtv-setup and mythfilldatabase, things appear to be fine.
> Recordings are made and show up on disk. However, any connection to the
> backend on port 6543 fails, UNLESS it occurs before the initial run of the
> scheduler. I haven't ever managed to get two connections to occur before
> the scheduler run ( my timing isn't that good :), but any connection that
> occurs after the scheduler runs fails, because the backend never responds.
> By this I mean that the connection is accepted, but no data is ever sent
> back, and mythweb and/or find_orphans.py time out waiting for a response to
> the ANN message.
> Logging with -v all doesn't really show much. MythSocket never logs
> anything for the port 6543/tcp after the scheduler, although I do see
> MythSocket entries for the UPnP SSDP packets being handled.
> Anyone have any ideas? I am at a complete loss... logfiles and a full
> strace available upon request!
Oh, I should also mention that the connections to port 6543 are held open
indefinitely, if you use something like nc or telnet to open the
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users