[mythtv-users] Backend not found when started with initscript
Michael Swanson
rearden at atlantisvalley.com
Mon Nov 26 06:08:39 UTC 2012
Hello all,
I'm having some trouble with getting the backend to start properly on
bootup. I'm using the Debian repo packages on a standard Wheezy
(testing) install. When I start the backend with the Debian provided
init script at boot time, the log shows some errors:
Nov 25 17:00:18 avalon-linux mythbackend[2960]: E CoreContext
serverpool.cpp:407 (listen) Failed listening on TCP
[fe80::224:8cff:fe8f:d311%eth0]:6544 - Error 9: The address is not available
Nov 25 17:00:18 avalon-linux mythbackend[2960]: E CoreContext
mediaserver.cpp:86 (Init) MediaServer::HttpServer Create Error
...
Nov 25 17:00:18 avalon-linux mythbackend[2960]: E CoreContext
serverpool.cpp:407 (listen) Failed listening on TCP
[fe80::224:8cff:fe8f:d311%eth0]:6543 - Error 9: The address is not available
Nov 25 17:00:18 avalon-linux mythbackend[2960]: C CoreContext
main_helpers.cpp:658 (run_backend) Backend exiting, MainServer
initialization error.
When I try and run the frontend on the same machine, it fails saying
it's unable to contact the backend.
However, when I run the backend manually, after boot time, the frontend
works fine, finding the backend with no issues. This happens both when
starting it with the init script and just starting the backend manually
from the command line.
It looks like the problem has to do with the link-local IP6 address not
being properly bound to the network card right away, but I've already
tried moving the backend init script later in the startup process so it
starts up after network-manager, and the problem seems to persist. Does
anyone know why the backend would be crashing for just the IP6 address
not being bound correctly? Thanks
Mike
More information about the mythtv-users
mailing list