[mythtv-users] Incompatible versions

Ken Smith kens at kensnet.org
Fri Nov 25 10:08:18 UTC 2022

Stephen Worthington wrote:
> On Thu, 24 Nov 2022 17:26:12 +0000, you wrote:
>> Hi All,
>> I wonder if someone can give me a pointer here. I have a friend with a
>> 0.32 installation on a Rocky Linux host.
>> If I configure it with its capture cards as a completely new system all
>> works well.
>> But, if I migrate the database from his old 0.25 system, using
>> mythconverg_restore.pl to restore the database and also change the
>> hostname I get this error from MythWeb ->
>> User Notice at /usr/share/mythtv/bindings/php/MythBackend.php, line 109:
>> !!NoTrans: Incompatible protocol version (mythweb=91, backend=72)!!
>> User Notice at /usr/share/mythtv/bindings/php/MythBackend.php, line 133:
>> !!NoTrans: Failed to set php timezone to !!
>> If I restore the mysqldump I made of the database prior to the restore
>> of the 0.25 database all returns to normal.
>> The upgrade process produced logs and errors like this:-
>> Table 'mythconverg.recgroups' doesn't exist
>> Unknown column 'autoextend' in 'field list'
>> I know about the store errors and will create the right folders for it,
>> but later in the process there are many errors like this.....
>> Unknown column 'r.lastplay' in 'field list'
>> Table 'mythconverg.recgroups' doesn't exist in the original database
> >from 0.25.
>> If this is hard to work around is there are simple way to transfer the
>> records of previous recordings from the old database to the new.
>> Everything else, capture cards etc etc has changed.
>> Interestingly I did a similar migration from my old 0.24 system earlier
>> in the year without any issues.
>> Any pointers would be much appreciated.
>> Thanks
>> Ken
> When you want to restore a database, you need to make sure you
> completely drop the old database first and get mythconverg_restore.pl
> to create a new database:
> mythconverg_restore.pl --drop_database --create_database --filename
> <backup file>.sql
> Then the next thing to do is run mythtv-setup to get it to upgrade the
> database schema.  It will do a database backup first, so it can take a
> while.  Check the /var/log/mythtv/mythtv-setup.log file for progress
> reports.  Then run mythfrontend and it will upgrade the database
> schema for any frontend only database tables (mythmusic in
> particular).  Again, it will backup the database first, so check
> /var/log/mythtv/mythfrontend.log for progress reports.
> _______________________________________________
Thanks Stephen, Thats the puzzle, as thats exactly what I did. Well I 
manually dropped and re-created an empty database prior to the 
mythconverg_restore. There does not appear to be a mythtv-setup.log on 
the system, nor on mine for that matter. Thus far I haven't run the 
frontend. The deeper puzzle is that I did a similar migration from my 
0.24 system earlier in the year without issue.

As far as I can see in the documentation 0.22 is the earliest version 
that migration is supported from.

Open to any suggestions.....



This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

More information about the mythtv-users mailing list