[mythtv-users] Problems having mythbackend running after boot

[Bill Meek]

On 01/05/2014 06:34 AM, Marcel Jira wrote:
> Hi and thank you for mythtv and this mailing list!
>
> I have mythtv installed on my computer with Debian Testing (x64, Gnome3). At the moment I try to get it working just on this computer, so no
> sophisticated network thing ;-)
>
> After I have done my configuration, Myth TV is running fine when I run mythbackend in the shell (I attached the console output in a link below).
>
> However, when I just boot the computer, mythbackend is not running (link to log attached at the bottom of this message).
>
> I have very little knowledge about the cause of this error, but it may be related to the network configuration of my mythtv backend. I entered
> 127.0.0.1 to the IP4-address and ::1 to the IP6-address.
>
> There's an error in the log saying
> [CODE]E CoreContext serverpool.cpp:411 (listen) Failed listening on TCP [fe80::5246:5dff:fe50:5509%eth0]:6543 - Error 9: The address is not
> available[/CODE]
>
> However, the following shell output makes me puzzled about this:
> [CODE]$ ping6 fe80::5246:5dff:fe50:5509%eth0
> PING fe80::5246:5dff:fe50:5509%eth0(fe80::5246:5dff:fe50:5509) 56 data bytes
> 64 bytes from fe80::5246:5dff:fe50:5509: icmp_seq=1 ttl=64 time=0.026 ms
> 64 bytes from fe80::5246:5dff:fe50:5509: icmp_seq=2 ttl=64 time=0.032 ms
> 64 bytes from fe80::5246:5dff:fe50:5509: icmp_seq=3 ttl=64 time=0.035 ms
> 64 bytes from fe80::5246:5dff:fe50:5509: icmp_seq=4 ttl=64 time=0.034 ms
> 64 bytes from fe80::5246:5dff:fe50:5509: icmp_seq=5 ttl=64 time=0.032 ms
> ^C
> --- fe80::5246:5dff:fe50:5509%eth0 ping statistics ---
> 5 packets transmitted, 5 received, 0% packet loss, time 3998ms
> rtt min/avg/max/mdev = 0.026/0.031/0.035/0.007 ms
> [/CODE]
>
> Can you help me to fix that?
>
> Thank you in advance!
>
> running mythbackend in the shell: [url]http://nopaste.info/2003dc44a1.html[/url]
>
> mythbackend.log - right after boot: [url]http://nopaste.info/1c2f8b48a8.html[/url]

I had a similar problem and "solved" it by adding a sleep 5 just before mythbackend
was started (in my case that was done in an Upstart .conf file.) The problem was that
Upstart didn't guarantee that *all* of the addresses on the interface were up. That
may care for the 3rd post boot startup in your log, but the 1st 2 are a bit scarier
(Failed to connect to (127.0.0.1:6543) and I've not seen that.

Good luck.

-- 
Bill