[mythtv-users] One step forward, two steps back - Frontends not woring properly
Mark
schurenmark at versanet.de
Sun May 1 10:50:47 UTC 2016
Am 29.04.2016 23:31, schrieb Damian:
> I ran one of the remote frontends from the command line to see what
> error messages I was getting while things were freezing, and I got
> lots of copies of messages like this ...
>
> 2016-04-29 21:49:14.102196 I MythCoreContext::ConnectCommandSocket():
> Connecting to backend server: 192.168.0.2:6543 (try 1 of 1)
> 2016-04-29 21:49:21.121452 E MythSocket(3b91410:68): ReadStringList:
> Error, timed out after 7000 ms.
> 2016-04-29 21:49:21.121843 C Protocol version check failure.
> The response to MYTH_PROTO_VERSION was empty.
> This happens when the backend is too busy to respond,
> or has deadlocked due to bugs or hardware failure.
> 2016-04-29 21:49:21.122406 W Backend : gingerserver currently
> Unreachable. Skipping this one.
> 2016-04-29 21:49:21.122558 I MythCoreContext::ConnectCommandSocket():
> Connecting to backend server: 192.168.0.2:6543
>
> I've just gone back to the server (backend system) and run the
> frontend on there. Now that's having the same trouble. Almost
> completely unresponsive. I haven't even touch this machine while I've
> been trying other stuff!
I had some very similar issue in my Ubuntu/mythbuntu setup recently.
Connectivity/network was fine, backend and first frontend worked fine.
But when connecting a second frontend (with slave backend) all became
slow and now also my first frontend had weird issues.
In my case all I had to do is check/increase the 'max_connections'
parameter of mysql, to allow for more concurrent connections.
After that I restarted all myth backends and frontends - and problems
were gone.
Just my 2 cents,
regards,
Mark
More information about the mythtv-users
mailing list