[mythtv-users] Help troubleshooting why remote FE can't connect

[Chris Vargas]

I am having problems connecting to my backend from a remote frontend and can't determine what the problem is. Hoping someone could help figure out what to try next.

The backend reports the following with mythbackend --version

MythTV Version   : 17024M
MythTV Branch    : branches/release-0-21-fixes
Library API      : 0.21.20080304-1
Network Protocol : 40

Both the local and remote frontend show this with mythfrontend --version

MythTV Version   : 17024M
MythTV Branch    : branches/release-0-21-fixes
Library API      : 0.21.20080304-1
Network Protocol : 40

I've enabled remote access on the backend by commenting out the bind-address in my.cnf. I can confirm remote access by logging on to mysql via the command line. All appropriate locations (as far as I can tell) in the backend setup and the frontend are using the IP number of the backend.

When I try to connect, I get the following:

2008-04-16 18:12:36.418 New DB connection, total: 2
2008-04-16 18:12:36.424 Connected to database 'mythconverg' at host: 192.168.1.30
2008-04-16 18:12:36.427 Unexpected DB Schema version.  Waiting to see if DB is being upgraded.
2008-04-16 18:12:41.451 Timed out waiting.
2008-04-16 18:12:41.451 This version of MythTV requires an updated database schema. Please run mythtv-setup or mythbackend to update your database.

If I run mythfrontend with verbose=all, it tries the following about 5 or 6 times

2008-04-17 03:02:08.083 MSqlQuery: CREATE TABLE IF NOT EXISTS schemalock ( schemalock int(1));
2008-04-17 03:02:08.084 MSqlQuery: LOCK TABLE schemalock WRITE;
2008-04-17 03:02:08.085 MSqlQuery: SELECT data FROM settings WHERE value = 'DBSchemaVer' AND hostname = 'fe01' ;
2008-04-17 03:02:08.086 MSqlQuery: SELECT data FROM settings WHERE value = 'DBSchemaVer' AND hostname IS NULL;
2008-04-17 03:02:08.086 MSqlQuery: UNLOCK TABLES;
2008-04-17 03:02:08.087 MSqlQuery: SELECT data FROM settings WHERE value = 'BackupDBLastRunStart' AND hostname = 'fe01' ;
2008-04-17 03:02:08.088 MSqlQuery: SELECT data FROM settings WHERE value = 'BackupDBLastRunStart' AND hostname IS NULL;
2008-04-17 03:02:08.089 MSqlQuery: SELECT data FROM settings WHERE value = 'BackupDBLastRunEnd' AND hostname = 'fe01' ;
2008-04-17 03:02:08.089 MSqlQuery: SELECT data FROM settings WHERE value = 'BackupDBLastRunEnd' AND hostname IS NULL;
2008-04-17 03:02:08.090 DBUtil::BackupInProgress(): Found database backup end time of 2008-04-17T02:37:18 later than start time of 2008-04-17T02:37:00, therefore backup is not running.

then it gives up, gives me the "timed out waiting" message and the "updated schema" message.

So, in posting all of this I just noticed that my remote frontend was inadvertantly set to Pacific time zone (I'm in Eastern). I reset the frontend to Eastern hoping that would fix things; nope, same error.

What can I try? Thanks for any help.