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 > >>>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. > >>> > >>>no errors... it does do this on every start of the backend though. > >>> > >>What does > >> > >>SELECT data FROM settings WHERE value = 'DBSchemaVer'; > >> > >>give? > >> > >> > >mysql> SELECT data FROM settings WHERE value = 'DBSchemaVer'; > >+------+ > >| data | > >+------+ > >| 1099 | > >+------+ > >1 row in set (0.00 sec) > > > > > And it's still trying to upgrade the database on every backend restart? > (You keep seeing the, "Setting Lock for Database Schema upgrade," > message?) Were there lines: > > Current Schema Version: 109X > Newest Schema Version : 1099 > > above the, "Setting lock," message in the log? > > Mike > _______________________________________________ > mythtv-users mailing list > [email protected] > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users >
No lines like that. the only thing mentioning the Schema was the messages I posted. full start up logs are below. I just restarted the backend, and ran the mysql statement from above, and the schema version still reports as 1099 2005-10-26 16:07:36.072 Using runtime prefix = /usr QSettings::sync: filename is null/empty 2005-10-26 16:07:36.104 New DB connection, total: 1 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. QSettings::sync: filename is null/empty 2005-10-26 16:07:36.129 New DB connection, total: 2 2005-10-26 16:07:36.134 Database Schema upgrade complete, unlocking. Starting up as the master server. 2005-10-26 16:07:36.290 mythbackend: MythBackend started as master server 2005-10-26 16:07:36.303 DVB#0 Using DVB card 0, with frontend pcHDTV HD3000 HDTV. QSettings::sync: filename is null/empty 2005-10-26 16:07:36.317 New DB connection, total: 3 2005-10-26 16:07:37.466 DVB#1 Using DVB card 1, with frontend Nextwave nxt2002 VSB/QAM frontend. QSettings::sync: filename is null/empty 2005-10-26 16:07:37.935 New DB scheduler connection 2005-10-26 16:07:37.952 mythbackend version: 0.19.20050712-1 www.mythtv.org 2005-10-26 16:07:37.957 Enabled verbose msgs : important general 2005-10-26 16:07:37.963 AutoExpire: Found 3 recorders w/max rate of 349 MiB/min 2005-10-26 16:07:37.970 AutoExpire: space: 3.7 GB w/freq: 5 min 2005-10-26 16:07:38.365 adding: piper.tube013.org as a slave backend server 2005-10-26 16:07:38.372 adding: glide as a slave backend server 2005-10-26 16:07:39.952 Reschedule requested for id 0. 2005-10-26 16:07:39.957 Reschedule requested for id 0. 2005-10-26 16:07:39.961 Reschedule requested for id -1. 2005-10-26 16:07:40.235 Scheduled 51 items in 0.3 = 0.16 match + 0.12 place 2005-10-26 16:07:40.246 scheduler: Scheduled items 2005-10-26 16:07:40.257 Seem to be woken up by USER 2005-10-26 16:07:43.375 AutoExpire: Found 3 recorders w/max rate of 349 MiB/min 2005-10-26 16:07:43.386 AutoExpire: space: 3.7 GB w/freq: 5 min 2005-10-26 16:07:47.953 mythbackend: Running housekeeping thread 2005-10-26 16:07:48.406 AutoExpire: Found 3 recorders w/max rate of 349 MiB/min 2005-10-26 16:07:48.415 AutoExpire: space: 3.7 GB w/freq: 5 min _______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
