On 10/26/05, Bruce Markey <[EMAIL PROTECTED]> wrote: > Byron Poland wrote: > > On 10/26/05, Michael T. Dean <[EMAIL PROTECTED]> wrote: > >> Byron Poland wrote: > >> > >>> On 10/26/05, Michael T. Dean <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>>> Byron Poland wrote: > >>>> > >>>>> Here is the relevant part of my backend log on on startup: > >>>>> > >>>>> 2005-10-26 15:02:15.804 Using runtime prefix = /usr > >>>>> QSettings::sync: filename is null/empty > User doesn't have ~/.qt dir? > > Missing "Current Schema Version:" message as of changeset 7260... > > >>>>> 2005-10-26 15:02:15.953 New DB connection, total: 1 > >>>>> 2005-10-26 15:02:15.991 Setting Lock for Database Schema upgrade. If > >>>>> you see a long pause here it means the Schema is already locked and is > >>>>> being upgraded by another Myth process. > >>>>> QSettings::sync: filename is null/empty > >>>>> 2005-10-26 15:02:16.005 New DB connection, total: 2 > >>>>> 2005-10-26 15:02:16.013 Database Schema upgrade complete, unlocking. > ... > >>> mysql> SELECT data FROM settings WHERE value = 'DBSchemaVer'; > >>> +------+ > >>> | data | > >>> +------+ > >>> | 1099 | > >>> +------+ > ... > > 2005-10-26 16:07:36.115 Setting Lock for Database Schema upgrade. If > > you see a long pause here it means the Schema is already locked and is > > being upgraded by another Myth process. > > Most likely you are inadvertently running an older version of > mythbackend. This would explain why you don't see the version > message, why it thinks the schema version number doesn't match > and why the basename field is not being filled in. > > If there is more than one machine involved, check that you have > installed the same version on all machines. Run "locate mythbackend" > to see if there is more than one executable. If you start the > backend from a script, check the path in the script and if from > the commandline, check "which mythbackend". > > -- bjm > _______________________________________________ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
This might be it. I had to compile from SVN to get the protocol on my frontend (ubuntu) (Which I also use as a slave backend to commflag and transcode) to match up with the backend (knoppmyth R5A22) so they very well could be different versions. I just located the source for the knoppmyth version, and am compiling it now. Will just equalizing all the version fix any problems or do I have prolems that need to be addressed? I may start my upgrade over again, I'll just loose some of my newer recordings which aren't too many in number. _______________________________________________ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users