[mythtv-users] Same trunk versions report different network protocols plus a DB schema version oddity
George Poulson
george.poulson at gmail.com
Mon Oct 4 10:17:33 UTC 2010
Hi all,
Last night I updated my two frontend and one backend boxes to the latest
trunk version from the Mythbuntu daily build repos.
All three boxes now report 'MythTV Version : 26630' and 'MythTV Branch :
Trunk'
The problem I now have is that neither of the frontends will connect to the
backend server!!
One of the frontends reports "This version of MythTV requires an updated
database (schema is 1 versions behind) - Please run mythtv-setup or
mythbackend to update your database"
Running mythfrontend --version on this box gives:
MythTV Version : 26630
MythTV Branch : trunk
Network Protocol : 63
Library API : 0.23.20100917-1
QT Version : 4.6.2
.. and the frontend log shows:
2010-10-04 10:57:56.215 Using Full Screen Window
2010-10-04 10:57:56.725 Using the Qt painter
2010-10-04 10:57:57.237 Current MythTV Schema Version (DBSchemaVer): 1263
2010-10-04 10:57:57.238 MythTV database schema is old. Waiting to see if DB
is being upgraded.
2010-10-04 10:57:58.238 New DB connection, total: 2
2010-10-04 10:57:58.243 Connected to database 'mythconverg' at host:
192.168.0.6
2010-10-04 10:57:58.266 Current MythTV Schema Version (DBSchemaVer): 1263
2010-10-04 10:57:59.277 Current MythTV Schema Version (DBSchemaVer): 1263
2010-10-04 10:58:00.290 Current MythTV Schema Version (DBSchemaVer): 1263
2010-10-04 10:58:01.312 Current MythTV Schema Version (DBSchemaVer): 1263
2010-10-04 10:58:02.321 Current MythTV Schema Version (DBSchemaVer): 1263
2010-10-04 10:58:02.324 Timed out waiting.
2010-10-04 10:58:02.324 Not allowed to upgrade the database.
2010-10-04 11:01:31.343 Couldn't upgrade database to new schema, exiting.
2010-10-04 11:01:31.343 Deleting UPnP client...
QWaitCondition: cv destroy failure:
QWaitCondition: mutex destroy failure:
george at revo:~$
The other frontend reports "The server uses network protocol version 63 but
this client only understands version 62. Make sure you are running
compatible versions of backend and frontend"
mythfrontend --version shows:
MythTV Version : 26630
MythTV Branch : trunk
Network Protocol : 62
Library API : 0.23.20100917-1
QT Version : 4.6.2
And this frontend log shows:
2010-10-04 11:02:17.463 MythCoreContext: Connecting to backend server:
192.168.0.6:6543 (try 1 of 1)
2010-10-04 11:02:17.510 Protocol version or token mismatch
(frontend=62/78B5631E,backend=63/??)
2010-10-04 11:02:22.511 MythCoreContext: Connecting to backend server:
192.168.0.6:6543 (try 1 of 1)
2010-10-04 11:02:22.568 Protocol version or token mismatch
(frontend=62/78B5631E,backend=63/??)
2010-10-04 11:02:27.128 Deleting UPnP client...
george at zotac:~$
On both frontends the mythfrontend.real is the same size and with the same
timestamp.
On the backend, mythbackend --version shows:
MythTV Version : 26630
MythTV Branch : trunk
Network Protocol : 62
Library API : 0.23.20100917-1
QT Version : 4.6.2
And the database schema version really is 1263:
mysql> select * from settings where value = "DBSchemaVer";
+-------------+------+----------+
| value | data | hostname |
+-------------+------+----------+
| DBSchemaVer | 1263 | NULL |
+-------------+------+----------+
Any idea what could be going on here? Apart from all of the frustrations I'm
describing here we are unable to watch any recordings, and as a result the
WAF is declining rapidly!
With the wonders of hindsight I should never have moved to trunk from
0.23.1, but I'm a born fiddler and the desire to dabble got the better of
me.. I will learn one day!
Thanks,
George
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20101004/7508f107/attachment.htm>
More information about the mythtv-users
mailing list