[clug] MythTV backend uncommunicative
eyal at eyal.emu.id.au
Fri Jul 6 23:20:11 MDT 2012
Are the front- and back-end on the same machine? If not, then ensure that
the exact same version is installed everywhere. Mythtv is amazingly unforgiving
any version mismatch (if I was doing such a design I would be fires on the spot).
Even if I did not mention that the client talks directly to the DB...
Can you browse to port 6544 on the server?
This, of course, does not matter if the frontend is a DLNA client.
On 07/07/12 15:07, Paul Wayper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Hi all,
> I've recently upgraded my home server to CentOS 6 and MythTV 0.25, and all of
> a sudden my MythTV backend is just not responding to network traffic. I can
> see the TCP handshake, and the front end or other program sends its MYTHPROTO
> handshake, but the backend just never seems to respond and, from strace and
> mythbackend's debugging, it's like the packet never actually gets received.
> Has anyone seen anything like this before? I'm kind of stumped at this point
> - - I know that there's something going wrong here but I have no idea what may
> be causing it.
> I've checked the firewall - the machine's firewall isn't preventing the packet
> from getting through.
> netstat says that the program is listening on port 6543 on all interfaces.
> mythbackend --printsched -v all and similar shows that the program is able to
> talk to the database on port 3306.
> Any ideas of things I can pursue to fix this would be greatly appreciated,
> because I'm at a bit of a dead end.
> Thanks in advance,
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
> -----END PGP SIGNATURE-----
Eyal Lebedinsky (eyal at eyal.emu.id.au)
More information about the linux