[mythtv-users] ongoing commo issues with compiled frontend / backend

[Nick Rout]

On Mon, Dec 12, 2011 at 11:08 AM, Mepis Rocks <mepisrocks at gmail.com> wrote:
> as previously mentioned, i've downloaded & compiled the latest source, and
> installed it all without an issue.
>
> my backend will not connect unless the IP address for both the local and
> master backend settings are 192.168.1.xxx.  if it's localhost or 127.0.0.1,
> backend will connection will continuously timeout.
>
> the frontend will not connect when the backend IPs are 192.168.1.xxx.  when
> i start up the frontend process it goes through the normal startup process
> but eventually produces the following error:
>
> Connected to database 'mythconverg' at host: 192.168.1.129
> 2011-12-11 16:55:07.961728 C  Reenabling DB Logging
> 2011-12-11 16:55:12.964639 I  Connected to database 'mythconverg' at host:
> 192.168.1.129
> 2011-12-11 16:55:12.968322 I  MythEvent: RECONNECT_SUCCESS
> 2011-12-11 16:55:12.974595 I  MythCoreContext: Connecting to backend server:
> 192.168.1.129:6543 (try 1 of 1)
> 2011-12-11 16:55:12.975340 I  MythSocket(ffffffffa6b27c60:-1): IP is local,
> using loopback address instead
> 2011-12-11 16:55:12.975386 I  MythSocket(ffffffffa6b27c60:-1): attempting
> connect() to (127.0.0.1:6543)
> 2011-12-11 16:55:12.975406 I  MSocketDevice::connect: setting Protocol to
> IPv4
> 2011-12-11 16:55:12.975416 I  MSocketDevice::connect: attempting to create
> new socket
> 2011-12-11 16:55:12.975571 E  MythSocket(ffffffffa6b27c60:87): connect()
> failed (ConnectionRefused)
> 2011-12-11 16:55:12.975652 E  Connection to master server timed out.
>                         Either the server is down or the master server
> settings
>                         in mythtv-settings does not contain the proper IP
> address
>
> mythbackend log, dmesg, /var/log/messages all show no errors
>
> i tried removing .mythtv from my normal user account to clear any possible
> lingering config issues.  i can connect to mysql to all IPs - 127.0.0.1,
> localhost, 192.168.1.xxx
>
> there are no firewall issues, no other security issues that would prevent
> connections - this was a fully functional system as of Friday.
>
> i really do need help with this.  my searches have not borne any useful
> solutions, and i've tried all sorts of different things to get this compiled
> version working because the latest debian multimedia upgrade segfaults, all
> the time and i don't foresee a new version from them any time.
>
> i'm running version 5.1.49 of mysql.

why do you care? it is better running on the external rather than
loopback address, in case you want to connect another frontend later.