mythtv-frontend only looks for backend at 127.0.0.1

[Edward Goodwin]

On a clean install of the mythtv-frontend 0.27 package with 9/16 updates, the frontend will not connect to a remote backend server. It only looks to 127.0.0.1 for the backend, no matter what is specified in the configuration:

2013-12-16 21:42:15.911741 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1)
2013-12-16 21:42:15.912260 E MythSocket(ffffffffb5a29508:-1): Failed to connect to (127.0.0.1:6543) Connection refused
2013-12-16 21:42:15.914394 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

2013-12-16 21:42:15.914444 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1)
2013-12-16 21:42:15.914971 E MythSocket(a0f8828:-1): Failed to connect to (127.0.0.1:6543) Connection refused
2013-12-16 21:42:15.924225 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

My backend runs on a different host.

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04.2 LTS"

version 2:0.27.0+fixes.20131216.39171be-0ubuntu0mythbuntu2

[Thomas Mashos (tgm4883)]

2 things.

1) There are far newer updates than 9/16, I would update to the latest fixes. (12/16 is the latest)

2) Can you post your ~/.mythtv/config.xml file

[Edward Goodwin (eddiegood)]

Sorry I meant the 12/16 update
 version is 2:0.27.0+fixes.20131216.39171be-0ubuntu0mythbuntu2

here is my config.xml (this works fine on the latest build for 0.26, but after upgrading to 0.27 latest build i can't connect to the backend<Configuration>
  <LocalHostName>thinkpad/LocalHostName>
  <Database>
      <PingHost>1</PingHost>
      <Host>192.168.1.5</Host>
      <UserName>eddie</UserName>
      <Password>password</Password>
      <DatabaseName>mythconverg</DatabaseName>
      <Port>3306</Port>
    </Database>
    <WakeOnLAN>
      <Enabled>0</Enabled>
      <SQLReconnectWaitTime>0</SQLReconnectWaitTime>
      <SQLConnectRetry>5</SQLConnectRetry>
      <Command>echo 'WOLsqlServerCommand not set'</Command>
    </WakeOnLAN>
    <UPnP>
      <UDN>
        <MediaRenderer>66c419c9-d515-4317-af8d-289f531e333c</MediaRenderer>
      </UDN>
    </UPnP>
  </LocalHostName>
  <UPnP>
    <UDN>
      <MediaRenderer>{5b164504-92d9-415c-897c-b02758aa6f7</MediaRenderer>
    </UDN>
  </UPnP>
</Configuration>

[Thomas Mashos (tgm4883)]

That all looks good. what is the output of

'dpkg -l | grep -i myth'
Thanks,

Thomas Mashos

On Tue, Dec 17, 2013 at 4:14 PM, Edward Goodwin <email address hidden> wrote:
> Sorry I meant the 12/16 update
> version is 2:0.27.0+fixes.20131216.39171be-0ubuntu0mythbuntu2
>
> here is my config.xml (this works fine on the latest build for 0.26, but after upgrading to 0.27 latest build i can't connect to the backend<Configuration>
> <LocalHostName>thinkpad/LocalHostName>
> <Database>
> <PingHost>1</PingHost>
> <Host>192.168.1.5</Host>
> <UserName>eddie</UserName>
> <Password>password</Password>
> <DatabaseName>mythconverg</DatabaseName>
> <Port>3306</Port>
> </Database>
> <WakeOnLAN>
> <Enabled>0</Enabled>
> <SQLReconnectWaitTime>0</SQLReconnectWaitTime>
> <SQLConnectRetry>5</SQLConnectRetry>
> <Command>echo 'WOLsqlServerCommand not set'</Command>
> </WakeOnLAN>
> <UPnP>
> <UDN>
> <MediaRenderer>66c419c9-d515-4317-af8d-289f531e333c</MediaRenderer>
> </UDN>
> </UPnP>
> </LocalHostName>
> <UPnP>
> <UDN>
> <MediaRenderer>{5b164504-92d9-415c-897c-b02758aa6f7</MediaRenderer>
> </UDN>
> </UPnP>
> </Configuration>
>
> --
> You received this bug notification because you are a member of Mythbuntu
> Bug Team, which is subscribed to mythtv in Ubuntu.
> https://bugs.launchpad.net/bugs/1261609
>
> Title:
> mythtv-frontend only looks for backend at 127.0.0.1
>
> Status in “mythtv” package in Ubuntu:
> New
>
> Bug description:
> On a clean install of the mythtv-frontend 0.27 package with 9/16
> updates, the frontend will not connect to a remote backend server. It
> only looks to 127.0.0.1 for the backend, no matter what is specified
> in the configuration:
>
>
> 2013-12-16 21:42:15.911741 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1)
> 2013-12-16 21:42:15.912260 E MythSocket(ffffffffb5a29508:-1): Failed to connect to (127.0.0.1:6543) Connection refused
> 2013-12-16 21:42:15.914394 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
>
> 2013-12-16 21:42:15.914444 I MythCoreContext: Connecting to backend server: 127.0.0.1:6543 (try 1 of 1)
> 2013-12-16 21:42:15.914971 E MythSocket(a0f8828:-1): Failed to connect to (127.0.0.1:6543) Connection refused
> 2013-12-16 21:42:15.924225 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
>
> My backend runs on a different host.
>
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=12.04
> DISTRIB_CODENAME=precise
> DISTRIB_DESCRIPTION="Ubuntu 12.04.2 LTS"
>
> version 2:0.27.0+fixes.20131216.39171be-0ubuntu0mythbuntu2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1261609/+subscriptions
>
> _______________________________________________
> Mailing list: https://launchpad.net...

[Edward Goodwin (eddiegood)]

I figured it out. Its actually a backend configuration item in the database. The frontend is connecting to the database at first, but in the settings table it had 127.0.0.1 defined for BackendServerIP and MasterServerIP.

Strange that they got entered in there like that. I always use the host name in mythtv-setup and it certainly resolves to 192.168.1.5.

I changed them appropriately and now it works:

+-----------------+-------------+-----------+
| value | data | hostname |
+-----------------+-------------+-----------+
| BackendServerIP | 192.168.1.5 | galvatron |
| MasterServerIP | 192.168.1.5 | NULL |
+-----------------+-------------+-----------+

Its also strange that the 0.26 frontend didn't use these settings, it seemed to rely on what was specified in config.xml.

[Thomas Mashos (tgm4883)]

Glad you figured that out. I'll go ahead and close this ticket.