[mythtv-users] Problem upgrading from 0.24 fixes to 0.25 schema 1266 to 1299
Michael T. Dean
mtdean at thirdcontact.com
Wed Apr 11 20:37:21 UTC 2012
(back on list)
On 04/11/2012 02:23 PM, david.medland-slater wrote:
> Hi Mike - in terms of the upgrade I shut down the other machine using
> the backend (I have two machines, one a FE and the other a BE), then
> did the apt-get type upgrade and found I had the issue. So I then
> killed off all the myth processes on the single remaining machine,
> restore the DB and ran the script.
> I can certainly send you the DB and that is a generous offer which I
> really appreciate. Hopefully the following link gives this to you.
OK, so having looked at your database, it's not a valid 1264 schema. It
actually does have some (but not all) post-0.24-fixes changes in it.
Were you running a version of MythTV compiled with some patches
applied? Did you run some MySQL commands to change the schema?
It seems your database has changes in it from the 1268, 1271, 1277,
1278, and 1279 (and possibly some other) updates, but is lacking changes
from other post-0.24 DB updates. However, for some reason, it still has
a 0.24 DB schema version set. I can't say how it happened (and hope you
might be able to give me an idea), but I can say that there's no
possible way our code (MythTV, as released) could have done
it--something else was involved and broke your database.
Note, also, that it's possible that if you improperly restored
0.24-fixes data into a differently-versioned database schema (such as a
"pre-created-by-distro/packager scripts" database schema), it could have
caused this issue. The MythTV-specific backup/restore scripts will
prevent users from doing such an invalid restore (which is why we have
our own scripts--to protect users from mistakes that corrupt their
databases), but if you used something else (phpmyadmin or even mysql
command-line client directly) to restore a good 0.24-fixes backup, it's
possible that may have caused the issues.
The commands you ran to let the upgrades succeed clean up at least the
"easily visible" non-0.24 stuff, so--short of checking everything--is
about the best you could do.
I did take a quick look at your schema and there are some issues with
it, still--specifically you still have some latin1 character encoding
that shouldn't exist, and possibly other issues.
You may want to consider doing a partial restore. Create a full back up
your 0.25 database, then drop the database, create a new, empty
database, then import the "critical" data from your backup using
, then reconfigure everything (backends, frontends, and all plugins).
See the linked wiki page for more details.
If you don't do the partial restore, you may not see problems, but
something has been messing with your schema, so both the schema
structure /and/ the data within your database are suspect at this point.
Thanks for letting me take a look at the database backup--and if you
have any ideas what might have messed up your schema, please let me
know. Since other users have shared similar stories about things
already existing that couldn't possibly have existed in a 0.24 schema,
I'm wondering if we might be able to track down what's causing the
issues for some users and warn people, appropriately.
More information about the mythtv-users