[mythtv-users] Backend won't start - ipv6 issue?
Yan Seiner
yan at seiner.com
Sun Jan 19 14:50:40 UTC 2014
On 01/19/2014 06:44 AM, Yan Seiner wrote:
> My servers reboot automatically at 1AM on Sunday morning. This has
> always gone off without a hitch until this morning when the backend
> refused to start.
>
> These seem to be the pertinent lines from mythbackend.log - notice the
> Error 9 on the ipv6 interface:
>
> Jan 19 06:34:13 NewMoon mythbackend: mythbackend[16639]: I CoreContext
> serverpool.cpp:399 (listen) Listening on TCP 127.0.0.1:6544
> Jan 19 06:34:13 NewMoon mythbackend: mythbackend[16639]: I CoreContext
> serverpool.cpp:399 (listen) Listening on TCP 192.168.128.2:6544
> Jan 19 06:34:13 NewMoon mythbackend: mythbackend[16639]: I CoreContext
> serverpool.cpp:399 (listen) Listening on TCP [::1]:6544
> Jan 19 06:34:13 NewMoon mythbackend: mythbackend[16639]: E CoreContext
> serverpool.cpp:411 (listen) Failed listening on TCP
> [fe80::20a:cdff:fe17:f4bb%bond0]:6544 - Error 9: The address is not
> available
> Jan 19 06:34:13 NewMoon mythbackend: mythbackend[16639]: E CoreContext
> mediaserver.cpp:86 (Init) MediaServer::HttpServer Create Error
> Jan 19 06:34:13 NewMoon mythbackend: mythbackend[16639]: I CoreContext
> serverpool.cpp:399 (listen) Listening on TCP 127.0.0.1:6543
> Jan 19 06:34:13 NewMoon mythbackend: mythbackend[16639]: I CoreContext
> serverpool.cpp:399 (listen) Listening on TCP 192.168.128.2:6543
> Jan 19 06:34:13 NewMoon mythbackend: mythbackend[16639]: I CoreContext
> serverpool.cpp:399 (listen) Listening on TCP [::1]:6543
> Jan 19 06:34:13 NewMoon mythbackend: mythbackend[16639]: E CoreContext
> serverpool.cpp:411 (listen) Failed listening on TCP
> [fe80::20a:cdff:fe17:f4bb%bond0]:6543 - Error 9: The address is not
> available
> Jan 19 06:34:13 NewMoon mythbackend: mythbackend[16639]: C CoreContext
> main_helpers.cpp:681 (run_backend) Backend exiting, MainServer
> initialization error.
>
> But ifconfig tells me the interface is available:
>
> root at NewMoon:/var/log/mythtv# ifconfig
> bond0 Link encap:Ethernet HWaddr 00:0a:cd:17:f4:bb
> inet addr:192.168.128.2 Bcast:192.168.128.255
> Mask:255.255.255.0
> inet6 addr: fe80::20a:cdff:fe17:f4bb/64 Scope:Link
> UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1
> RX packets:233657 errors:2 dropped:0 overruns:2 frame:0
> TX packets:198662 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:131014818 (131.0 MB) TX bytes:107982506 (107.9 MB)
>
> and it's unchanged for weeks....
>
> Any ideas why this morning it would fail?
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>
> !DSPAM:52dbe4ce169551213825713!
>
For now I've disabled ipv6 (since I don't use it anyway) but I'd still
like to know why the backend failed to start....
For posterity, here's how you disable ipv6:
echo net.ipv6.conf.all.disable_ipv6 = 1 > /etc/sysctl.d/01-disable-ipv6.conf
service procps start
service mythtv-backend start
More information about the mythtv-users
mailing list