MythTV normally starts without any problems, but sometimes the front end starts, and then an error message appears saying that MythTV couldn’t connect to the master back end server. When this happens the error message will go away after a short time, then reappear. The only remedy is to turn off the MythTV computer, then restart. Often the error message will re-appear after MythTV is restarted, and it will require several restarts before MythTV starts correctly, and then behaves normally. Waiting for perhaps 15 minutes or more before attempting to restart MythTV seems to help.
Details of the system: Both back end and front end are on the same computer. The computer is running MythBuntu 0.28/ Ubuntu 14.04. Motherboard CPU/GPU AMD Zacate E35M1-M PRO. The computer connects to the internet via WiFi.
Does anybody know what might be causing this problem? Could it be due to problems timing problems for the startup due to the WiFi card having problems connecting to the WiFi network?
intermittent back end connection problem
Re: intermittent back end connection problem
AFAIK, you don't need and internet connection for mythtv to operate. Although I wouldn't rule out the system slowing down trying to get the connection.
BE/FE-Asrock AB350 Pro Ryzen 3 3200G, 6 atsc tuners. FE's-GF8200's Athlon II, Ryzen 3 2200G. Mythtv user since 2005.
Re: intermittent back end connection problem
Ubuntu 14.04 is a bit old. Consider installing 18.04. Is the backend and frontend set to use "localhost" and not an ip address in Setup --> General? If the frontend is automatically starting, maybe a delay could help (bash -c "sleep 20 && mythfrontend --service").
Ted | My blog
Re: intermittent back end connection problem
I'd try this: grep "<Host>" {~,~mythtv}/.mythtv/config.xm and expect the response
to be: <Host>localhost</Host> for both config.xml files. That will cause the backend
to use a socket, rather than a TCP connection for mysql. It's the best practice for the
backend and a combined frontend/backend.
to be: <Host>localhost</Host> for both config.xml files. That will cause the backend
to use a socket, rather than a TCP connection for mysql. It's the best practice for the
backend and a combined frontend/backend.