[mythtv-users] connection issue

[Bill Meek]

On 09/18/2013 06:23 PM, Daryl McDonald wrote:
...
> Here is the backend log:  http://paste.ubuntu.com/6126024/
>
> And the frontend log:   http://paste.ubuntu.com/6126031/
...

I cut the logs down so they fit on a screen (at least on my wide screen.)

OK, the frontend 1st tells of a problem here:

     Sep 18 18:50:44 ... mythfrontend[2396]: I ... MythCoreContext: Connecting  to backend server: 127.0.0.1:6543 (try 1 of 1)
     Sep 18 18:50:44 ... mythfrontend[2396]: E ... Connection to master server timed out. ...Either the server is down or...

So look at the backend log and see what it's doing *at that time*:

     Sep 18 18:50:39 ... mythbackend[1899]: E ... Failed listening on TCP [fd11:cc97:526d:0:1278:d2ff:fe1d:9989]:6543 - Error 9:...
     ...
     Sep 18 18:50:39 ... mythbackend[1899]: C ... Backend exiting, MainServer initialization error.
     Sep 18 18:50:49 ... mythbackend[1899]: I ... Running housekeeping thread
     Sep 18 18:51:59 ... mythbackend[1899]: E ... AutoExpire: Filesystem Info cache is empty, unable to calculate necessary parameters.
     ...
     Sep 18 18:55:54 ... mythbackend[1899]: I ... Running housekeeping thread
     ...
     Sep 18 19:09:03 ... mythbackend[2887]: C ... mythbackend version: fixes/0.25 [v0.25.3-49-gb5adf03] www.mythtv.org

It's shutting down. Then a new backend is started (PID 2887.) Pay special attention to
Note 5 in the link HP-mini posted. It has to do with IPv6 addresses being available
at the time the backend starts. Once the machine is running, the problem doesn't
occur.

Do you use IPv6? Just curious because the address that starts out with fd11: is
a manually configured Unique Local Address in my experience.

And, you don't need to keep doing the: mythbackend --setverbose idle,system.
That was for testing you shutdown problems.

-- 
Bill