[mythtv-users] Help: Failed to connect to (127.0.0.1:6543) Connection refused

[Bill Meek]

On 9/27/19 3:48 PM, Craig Huff wrote:
> On Sat, Sep 7, 2019 at 6:40 AM Craig Huff <huffcslists at gmail.com <mailto:huffcslists at gmail.com>> wrote:
> 
>     On Fri, Sep 6, 2019 at 9:14 PM Bill Meek <keemllib at gmail.com <mailto:keemllib at gmail.com>> wrote:
> 
>         If mythtv-setup isn't working, and you're comfortable with SQL, I'd do
>         this:
> 
>               SELECT * FROM settings WHERE value IN ('AllowLinkLocal', 'BackendServerIP', 'MasterServerIP');
> 
>         The log say the BE is running as master, so the ServerIPs should be OK.
> 
>         If AllowLinkLocal isn't = 1, then the BE won't be listening on 127.0.0.1
> 
>         -- 
>         Bill
> 
> 
>     Thanks for getting back to me.  It seems there's always something arcane I need to add to my knowledge when working with MythTV. :-)
> 
>     As for the SQL query, it came back with multiple BackendServerIP entries, one for the master backend with it's correct IP -- 192.168.1.149
>     -- and three for frontend-only systems. Dunno whether those should be there, but one lists 192.168.1.148 (That frontend's IP!) and the other
>     two list 127.0.0.1.  Not sure if I should remove them or update them.
> 
>     AllowLinkLocal = 1, so that's good.
> 
>     MasterServerIP = 192.168.1.149, which is correct, but it has hostname = NULL.  IP is correct, but not sure if the hostname = NULL is an issue.
> 
>     AFAIK, these settings haven't changed in years, so I don't know if something else was twiddling with them or I'd just been skating on thin
>     ice all this time (if they're wrong), or they're weird but ok.
> 
>     --
>     Craig.
> 
> 
> I've been tied up with other things for weeks and am now just getting back to trying to solve this problem.  Here are the last few lines of the 
> log from trying to launch mythwelcome from the command line in an xterm window:
> 2019-09-27 15:35:52.557130 I  MythCoreContext: Connecting to backend server: 192.168.1.149:6543 <http://192.168.1.149:6543> (try 2 of 5)
> 2019-09-27 15:35:52.557635 E  MythSocket(14c5ca0:-1): Failed to connect to (127.0.0.1:6543 <http://127.0.0.1:6543>) Connection refused
> 2019-09-27 15:36:52.640164 I  MythCoreContext: Connecting to backend server: 192.168.1.149:6543 <http://192.168.1.149:6543> (try 3 of 5)
> 2019-09-27 15:36:52.640674 E  MythSocket(14c5ca0:-1): Failed to connect to (127.0.0.1:6543 <http://127.0.0.1:6543>) Connection refused
> ICE default IO error handler doing an exit(), pid = 4664, errno = 32
> QWaitCondition: cv destroy failure: Device or resource busy
> QWaitCondition: mutex destroy failure: Device or resource busy
> 
> It seems weird to me that it keeps switching between the correct IP address (192.168.1.149) and the local loopback address (127.0.0.1).
> 
> Any suggestions on how to troubleshoot this?  I have no idea how to figure out why the frontend/mythwelcome suddenly stopped being able to 
> connect to the backend.

Before going further, I'd get rid of the ICE error by renaming that file (I've done it in the past
and simply removing it worked.) Searching the web will turn up similar suggestions.

If that doesn't help, then maybe start with https://www.mythtv.org/wiki/Config.xml#Troubleshooting
and pastebin a full FE log.


-- 
Bill