Author |
Message |
graysky
|
Posted: Sat Mar 06, 2010 8:48 am |
|
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location:
/dev/null
|
Code: sudo pacman -Sy linhes-scripts sudo upgrade_to_0.22.sh Seems to be stuck in an endless loop of updating schema and errors... it's been running for a good 40 min now like this Code: 2010-03-06 09:26:13.631 Using runtime prefix = /usr 2010-03-06 09:26:13.768 Empty LocalHostName. 2010-03-06 09:26:13.796 Using localhost value of mythtv 2010-03-06 09:26:13.945 New DB connection, total: 1 2010-03-06 09:26:14.088 Connected to database 'mythconverg' at host: localhost 2010-03-06 09:26:14.123 Closing DB connection named 'DBManager0' 2010-03-06 09:26:14.155 Connected to database 'mythconverg' at host: localhost 2010-03-06 09:26:14.202 New DB connection, total: 2 2010-03-06 09:26:14.230 Connected to database 'mythconverg' at host: localhost 2010-03-06 09:26:14.257 Current Schema Version: 1214 Starting up as the master server. 2010-03-06 09:26:14.380 mythbackend: MythBackend started as master server 2010-03-06 09:26:14.478 New DB connection, total: 3 2010-03-06 09:26:14.507 Connected to database 'mythconverg' at host: localhost 2010-03-06 09:26:14.727 New DB scheduler connection 2010-03-06 09:26:14.774 Connected to database 'mythconverg' at host: localhost 2010-03-06 09:26:16.101 Main::Registering HttpStatus Extension 2010-03-06 09:26:16.398 mythbackend version: 0.21.20080304-1 www.mythtv.org 2010-03-06 09:26:16.606 Enabled verbose msgs: important general 2010-03-06 09:26:16.771 AutoExpire: CalcParams(): Max required Free Space: 1.0 GB w/freq: 15 min 2010-03-06 09:26:17.871 Reschedule requested for id -1. 2010-03-06 09:26:18.786 Scheduled 17 items in 0.9 = 0.68 match + 0.24 place 2010-03-06 09:26:18.844 scheduler: Scheduled items: Scheduled 17 items in 0.9 = 0.68 match + 0.24 place 2010-03-06 09:26:18.886 Seem to be woken up by USER 2010-03-06 09:26:19.917 I'm idle now... shutdown will occur in 1200 seconds. 2010-03-06 09:26:20.590 MainServer::HandleAnnounce Playback 2010-03-06 09:26:20.623 adding: mythtv as a client (events: 0) 2010-03-06 09:26:20.640 MainServer::HandleAnnounce Monitor 2010-03-06 09:26:20.673 adding: mythtv as a client (events: 1) 2010-03-06 09:26:24.440 mythbackend: Running housekeeping thread 2010-03-06 09:26:25.125 UPnpMedia: BuildMediaMap VIDEO scan starting in :/myth/video: 2010-03-06 09:26:29.285 UPnpMedia: BuildMediaMap Done. Found 1841 objects 2010-03-06 09:27:34.820 AutoExpire: CalcParams(): Max required Free Space: 1.0 GB w/freq: 15 min 2010-03-06 09:38:59.099 I'm idle now... shutdown will occur in 1200 seconds. 2010-03-06 09:41:36.362 mythbackend version: branches/release-0-22-fixes [23566M] www.mythtv.org 2010-03-06 09:41:36.676 Using runtime prefix = /usr 2010-03-06 09:41:36.699 Using configuration directory = /home/mythtv/.mythtv 2010-03-06 09:41:36.731 Empty LocalHostName. 2010-03-06 09:41:36.766 Using localhost value of mythtv 2010-03-06 09:41:36.821 New DB connection, total: 1 2010-03-06 09:41:36.848 Connected to database 'mythconverg' at host: localhost 2010-03-06 09:41:36.874 Closing DB connection named 'DBManager0' 2010-03-06 09:41:36.900 Connected to database 'mythconverg' at host: localhost 2010-03-06 09:41:36.930 Current MythTV Schema Version (DBSchemaVer): 1214 2010-03-06 09:41:36.958 MythTV database schema is old. Waiting to see if DB is being upgraded. 2010-03-06 09:41:37.983 New DB connection, total: 2 2010-03-06 09:41:38.057 Connected to database 'mythconverg' at host: localhost 2010-03-06 09:41:38.086 Current MythTV Schema Version (DBSchemaVer): 1214 2010-03-06 09:41:39.111 Current MythTV Schema Version (DBSchemaVer): 1214 2010-03-06 09:41:40.160 Current MythTV Schema Version (DBSchemaVer): 1214 2010-03-06 09:41:41.209 Current MythTV Schema Version (DBSchemaVer): 1214 2010-03-06 09:41:42.258 Current MythTV Schema Version (DBSchemaVer): 1214 2010-03-06 09:41:42.311 Timed out waiting. 2010-03-06 09:41:42.486 Backing up database with script: '/usr/share/mythtv/mythconverg_backup.pl' 2010-03-06 09:41:49.367 Database Backup complete. 2010-03-06 09:41:49.422 Backed up database to file: '/myth/tv/mythconverg-1214-20100306094142.sql.gz' 2010-03-06 09:41:49.454 Console is non-interactive, can't prompt user... 2010-03-06 09:41:49.495 Upgrading. 2010-03-06 09:41:49.521 Newest MythTV Schema Version : 1244 2010-03-06 09:41:49.556 Upgrading to MythTV schema version 1215 2010-03-06 09:41:49.579 New DB connection, total: 3 2010-03-06 09:41:49.605 Connected to database 'mythconverg' at host: localhost 2010-03-06 09:41:52.180 Upgrading to MythTV schema version 1216 2010-03-06 09:41:54.840 DB Error (Performing database upgrade): Query was: ALTER TABLE program MODIFY title varbinary(128) NOT NULL default '', MODIFY subtitle varbinary(128) NOT NULL default '', MODIFY description blob NOT NULL, MODIFY category varbinary(64) NOT NULL default '', MODIFY category_type varbinary(64) NOT NULL default '', MODIFY title_pronounce varbinary(128) NOT NULL default '', MODIFY seriesid varbinary(40) NOT NULL default '', MODIFY showtype varbinary(30) NOT NULL default '', MODIFY colorcode varbinary(20) NOT NULL default '', MODIFY syndicatedepisodenumber varbinary(20) NOT NULL default '', MODIFY programid varbinary(40) NOT NULL default ''; Error was: Driver error was [2/1054]: QMYSQL3: Unable to execute statement Database error was: Unknown column 'title_pronounce' in 'program' new version: 1216 2010-03-06 09:41:54.881 DB charset conversions update failed! Your database seems to be partially corrupted. Please move the backup to a safe place. Your database must be fixed before you can upgrade beyond 0.21-fixes. Please see http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding for information. 2010-03-06 09:41:54.906 Database Schema upgrade FAILED, unlocking. 2010-03-06 09:41:54.931 Couldn't upgrade database to new schema 2010-03-06 09:41:55.201 mythbackend version: branches/release-0-22-fixes [23566M] www.mythtv.org 2010-03-06 09:41:55.248 Using runtime prefix = /usr 2010-03-06 09:41:55.273 Using configuration directory = /home/mythtv/.mythtv 2010-03-06 09:41:55.298 Empty LocalHostName. 2010-03-06 09:41:55.323 Using localhost value of mythtv 2010-03-06 09:41:55.357 New DB connection, total: 1 2010-03-06 09:41:55.388 Connected to database 'mythconverg' at host: localhost 2010-03-06 09:41:55.415 Closing DB connection named 'DBManager0' 2010-03-06 09:41:55.440 Connected to database 'mythconverg' at host: localhost 2010-03-06 09:41:55.470 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 09:41:55.490 MythTV database schema is old. Waiting to see if DB is being upgraded. 2010-03-06 09:41:56.515 New DB connection, total: 2 2010-03-06 09:41:56.564 Connected to database 'mythconverg' at host: localhost 2010-03-06 09:41:56.593 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 09:41:57.618 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 09:41:58.651 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 09:41:59.708 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 09:42:00.765 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 09:42:00.818 Timed out waiting. 2010-03-06 09:42:00.864 Backing up database with script: '/usr/share/mythtv/mythconverg_backup.pl' 2010-03-06 09:42:05.360 Database Backup complete. 2010-03-06 09:42:05.424 Backed up database to file: '/myth/tv/mythconverg-1215-20100306094200.sql.gz' 2010-03-06 09:42:05.456 Console is non-interactive, can't prompt user... 2010-03-06 09:42:05.505 Upgrading. 2010-03-06 09:42:05.522 Newest MythTV Schema Version : 1244 2010-03-06 09:42:07.578 New DB connection, total: 3 2010-03-06 09:42:07.631 Connected to database 'mythconverg' at host: localhost 2010-03-06 09:42:07.645 Upgrading to MythTV schema version 1216 2010-03-06 09:42:10.165 DB Error (Performing database upgrade): Query was: ALTER TABLE program MODIFY title varbinary(128) NOT NULL default '', MODIFY subtitle varbinary(128) NOT NULL default '', MODIFY description blob NOT NULL, MODIFY category varbinary(64) NOT NULL default '', MODIFY category_type varbinary(64) NOT NULL default '', MODIFY title_pronounce varbinary(128) NOT NULL default '', MODIFY seriesid varbinary(40) NOT NULL default '', MODIFY showtype varbinary(30) NOT NULL default '', MODIFY colorcode varbinary(20) NOT NULL default '', MODIFY syndicatedepisodenumber varbinary(20) NOT NULL default '', MODIFY programid varbinary(40) NOT NULL default ''; Error was: Driver error was [2/1054]: QMYSQL3: Unable to execute statement Database error was: Unknown column 'title_pronounce' in 'program'
Flyspray task: http://linhes.org/flyspray/index.php?do ... ask_id=636
_________________ Retired KM user (R4 - R6.04); friend to LH users.
|
|
Top |
|
|
graysky
|
Posted: Sat Mar 06, 2010 9:48 am |
|
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location:
/dev/null
|
Before I attempted the upgrade process, I ran the backup script and I did an rsync of my entire root directory to another HDD. After running into the problem, I nuked my /dev/sda1 entirely and rsynced the copy back thinking that would provide me with a failsafe.
After rsyncing back the backup of my / partition and rebooting, The box is just stuck in an endless loop of:
Code: Starting Hal [BKGD] Starting SSH [BKGD] Starting Mysql [BKGD] Starting lighttpd [BKGD] Starting Avahi [BKGD] Starting Hal [BKGD] Starting SSH [BKGD] Starting Mysql [BKGD] Starting lighttpd [BKGD] Starting Avahi [BKGD] Starting Hal [BKGD] Starting SSH [BKGD] Starting Mysql [BKGD] Starting lighttpd [BKGD] Starting Avahi [BKGD] etc.
Advise is greatly appreciated.
_________________ Retired KM user (R4 - R6.04); friend to LH users.
|
|
Top |
|
|
RacerX
|
Posted: Sat Mar 06, 2010 11:27 am |
|
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
|
Graysky
It appears that the database is partially corrupt.
This page looks promising
http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding
You are going to have to rollback to .21 and the fix the database before you can run the perform the upgrade.
Once you have it rolled back to .21 then you can run this command
Code: mysql -umythtv -p mythconverg -e 'status;'
Look at the type of character set it should say "latin1"
|
|
Top |
|
|
graysky
|
Posted: Sat Mar 06, 2010 11:31 am |
|
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location:
/dev/null
|
@RacerX - I tried the procedure but never was able to restore the db, failing in the "restore backup" step. The errors as I remember were something like "cannot continue because data exists." Right now, I can't even boot due to this new endless loop of my daemons trying to load or else I'd get in there and try again posting the full error log.
graysky wrote: After rsyncing back the backup of my / partition and rebooting, The box is just stuck in an endless loop of: Code: Starting Hal [BKGD] Starting SSH [BKGD] Starting Mysql [BKGD] Starting lighttpd [BKGD] Starting Avahi [BKGD] Starting Hal [BKGD] Starting SSH [BKGD] Starting Mysql [BKGD] Starting lighttpd [BKGD] Starting Avahi [BKGD] Starting Hal [BKGD] Starting SSH [BKGD] Starting Mysql [BKGD] Starting lighttpd [BKGD] Starting Avahi [BKGD] etc.
_________________ Retired KM user (R4 - R6.04); friend to LH users.
|
|
Top |
|
|
RacerX
|
Posted: Sat Mar 06, 2010 11:52 am |
|
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
|
I think your backup is the key.
According to the page
You must fix your database configuration before upgrading to post-r16789 SVN trunk or to 0.22.
What version of myth do you have in the backup?
|
|
Top |
|
|
graysky
|
Posted: Sat Mar 06, 2010 12:01 pm |
|
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location:
/dev/null
|
RacerX wrote: I think your backup is the key.
According to the page
You must fix your database configuration before upgrading to post-r16789 SVN trunk or to 0.22.
What version of myth do you have in the backup?
Whatever came with R6.01.00 which I believe is 0.21. I understand that the db has some partial corruption, but right now the bigger problem is the endless daemon loading loop I described. I can switch to another tty and login as root, but I can't run mythrestore due to mysql not running, nor can I start it. I know nothing about the init system R6 is using so I have no idea what is causing the endless loop.
_________________ Retired KM user (R4 - R6.04); friend to LH users.
|
|
Top |
|
|
RacerX
|
Posted: Sat Mar 06, 2010 12:11 pm |
|
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
|
Here is what I was getting at. You can reload the system from scratch to R6.01 and then you can restore your database from your backup. That
should get you system back to normal. Then you can try to repair the database since you have a working system that isn't endless looping.
|
|
Top |
|
|
tjc
|
Posted: Sat Mar 06, 2010 12:22 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
I had similar problems trying to upgrade my production box from R5.5 to R6.02.00 last night. There were also LVM and Nvidia driver issues, but the real deal breaker was a DB upgrade failure. After about ~5-6 hours of trying different things to work around it I gave up and rolled back to R5.5 again. Sadly I didn't think to save the log files since it seemed pretty repeatable.
BTW - Following the directions on that page shows a "Properly-configured server" for R5.5. Since there hasn't been a huge howl of outrage and frustration here from people trying to upgrade R5.5 to R6 that doesn't sound like the issue.
|
|
Top |
|
|
graysky
|
Posted: Sat Mar 06, 2010 1:15 pm |
|
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location:
/dev/null
|
RacerX wrote: Here is what I was getting at. You can reload the system from scratch to R6.01 and then you can restore your database from your backup. That should get you system back to normal. Then you can try to repair the database since you have a working system that isn't endless looping.
Yeah, was saving that as the nuclear option. I really loath the idea and was hoping someone could tell me what I need to tweak to fix this loop issue.
_________________ Retired KM user (R4 - R6.04); friend to LH users.
|
|
Top |
|
|
RacerX
|
Posted: Sat Mar 06, 2010 1:24 pm |
|
Joined: Sun Sep 05, 2004 7:06 pm
Posts: 690
|
I hear ya it's a PITA, but think of it as insurance. Many people lost everything because they did not make a good backup.
The bigger question is getting the database ready for the upgrade. I think it's a scope change that the character set must be "latin1". It would appear that .21 to .22 sets this new requirement. Assuming that is the database problem.
|
|
Top |
|
|
cecil
|
Posted: Sat Mar 06, 2010 1:35 pm |
|
|
Site Admin |
Joined: Fri Sep 19, 2003 6:37 pm
Posts: 2659
Location:
Whittier, Ca
|
I don't believe this is an issue with the upgrade script. Rather something is amiss with you system/db. If you look at the error MythTV is giving, it states your db is corrupt. Furthermore, you attemped to restore your system via an rsync backup. If you know your db from the backup you made is good, I'd recommend booting from the 6.02 ISO and doing an upgrade.
After the upgrade, you'll want to give the backend time to upgrade your schema. The frontend may display that it cannot connect to the backend. Hopefully, this will get you going.
The "latin1" issue isn't an issue w/ KnoppMyth/LinHES unless someone made some modification to their db.
|
|
Top |
|
|
graysky
|
Posted: Sat Mar 06, 2010 1:53 pm |
|
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location:
/dev/null
|
I just reinstalled from R6.01 and my backup. Everything is working now. I'm afraid to run the R6.02 upgrade, since I believe it'll put me back in the endless loop of the inability to upgrade my database.
I just did the R6.01 restore from CD and my db seems fine (all latin1 as per the wiki):
Code: $ mysql -umythtv -p mythconverg -e 'status;' Enter password: -------------- mysql Ver 14.12 Distrib 5.0.75, for pc-linux-gnu (i686) using readline 5.2
Connection id: 16 Current database: mythconverg Current user: mythtv@localhost SSL: Not in use Current pager: stdout Using outfile: '' Using delimiter: ; Server version: 5.0.75 Source distribution Protocol version: 10 Connection: Localhost via UNIX socket Server characterset: latin1 Db characterset: latin1 Client characterset: latin1 Conn. characterset: latin1 UNIX socket: /tmp/mysql.sock Uptime: 4 min 42 sec
Threads: 6 Questions: 76678 Slow queries: 0 Opens: 46 Flush tables: 1 Open tables: 34 Queries per second avg: 271.908
I'm trying the 0.22 upgrade again with fingers crossed.
_________________ Retired KM user (R4 - R6.04); friend to LH users.
|
|
Top |
|
|
graysky
|
Posted: Sat Mar 06, 2010 2:28 pm |
|
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location:
/dev/null
|
One problem I seem to have run into on the upgrade:
Code: Starting the backend. This will automatically update the schema. I'll launch an xterm so you watch output backend log. Once the schema updates are complete, switch back to this xterm. When you see "Upgrading to MythTV schema version 1244" You can switch back to this xterm. Note:After pressing <ENTER>, I'll be asleep for 30 secs... This will give the schema time to upgrade. Press <ENTER> to continue... Press <ENTER> to continue once the schema upgrade is complete. Here is the output from 2nd xterm: Code: 2010-03-06 15:29:51.437 Main::Registering HttpStatus Extension 2010-03-06 15:29:51.501 mythbackend version: 0.21.20080304-1 www.mythtv.org 2010-03-06 15:29:51.526 Enabled verbose msgs: important general 2010-03-06 15:29:51.552 AutoExpire: CalcParams(): Max required Free Space: 1.0 GB w/freq: 15 min 2010-03-06 15:29:53.221 Reschedule requested for id -1. 2010-03-06 15:29:53.282 Scheduled 17 items in 0.1 = 0.04 match + 0.02 place 2010-03-06 15:29:53.320 scheduler: Scheduled items: Scheduled 17 items in 0.1 = 0.04 match + 0.02 place 2010-03-06 15:29:53.353 Seem to be woken up by USER 2010-03-06 15:29:54.369 I'm idle now... shutdown will occur in 1200 seconds. 2010-03-06 15:30:00.088 mythbackend: Running housekeeping thread 2010-03-06 15:30:03.913 UPnpMedia: BuildMediaMap VIDEO scan starting in :/myth/video: 2010-03-06 15:30:34.862 UPnpMedia: BuildMediaMap Done. Found 74864 objects 2010-03-06 15:31:10.222 AutoExpire: CalcParams(): Max required Free Space: 1.0 GB w/freq: 15 min 2010-03-06 15:46:10.555 AutoExpire: CalcParams(): Max required Free Space: 1.0 GB w/freq: 15 min 2010-03-06 15:49:54.015 MainServer::HandleAnnounce Monitor 2010-03-06 15:49:54.040 adding: mythtv as a client (events: 0) It's just frozen there... EDIT: I looked at cesman's script and manually ran though it... seems as though I had to add a force switch to pacman to get it to overwrite some files on the FS leftover from the first failed attempt to upgrade. Anyway, same old story after I brought up the backend: Code: 2010-03-06 15:59:59.551 Connected to database 'mythconverg' at host: localhost 2010-03-06 15:59:59.578 Current MythTV Schema Version (DBSchemaVer): 1214 2010-03-06 16:00:00.603 Current MythTV Schema Version (DBSchemaVer): 1214 2010-03-06 16:00:01.652 Current MythTV Schema Version (DBSchemaVer): 1214 2010-03-06 16:00:02.709 Current MythTV Schema Version (DBSchemaVer): 1214 2010-03-06 16:00:03.775 Current MythTV Schema Version (DBSchemaVer): 1214 2010-03-06 16:00:03.829 Timed out waiting. 2010-03-06 16:00:03.932 Backing up database with script: '/usr/share/mythtv/mythconverg_backup.pl' 2010-03-06 16:00:10.000 Database Backup complete. 2010-03-06 16:00:10.033 Backed up database to file: '/myth/tv/mythconverg-1214-20100306160003.sql.gz' 2010-03-06 16:00:10.065 Console is non-interactive, can't prompt user... 2010-03-06 16:00:10.106 Upgrading. 2010-03-06 16:00:10.132 Newest MythTV Schema Version : 1244 2010-03-06 16:00:10.167 Upgrading to MythTV schema version 1215 2010-03-06 16:00:10.190 New DB connection, total: 3 2010-03-06 16:00:10.215 Connected to database 'mythconverg' at host: localhost 2010-03-06 16:00:11.957 Upgrading to MythTV schema version 1216 2010-03-06 16:00:14.509 DB Error (Performing database upgrade): Query was: ALTER TABLE program MODIFY title varbinary(128) NOT NULL default '', MODIFY subtitle varbinary$ Error was: Driver error was [2/1054]: QMYSQL3: Unable to execute statement Database error was: Unknown column 'title_pronounce' in 'program'
new version: 1216 2010-03-06 16:00:14.542 DB charset conversions update failed! Your database seems to be partially corrupted$ 2010-03-06 16:00:14.567 Database Schema upgrade FAILED, unlocking. 2010-03-06 16:00:14.592 Couldn't upgrade database to new schema 2010-03-06 16:00:14.746 mythbackend version: branches/release-0-22-fixes [23566M] www.mythtv.org 2010-03-06 16:00:14.784 Using runtime prefix = /usr 2010-03-06 16:00:14.809 Using configuration directory = /home/mythtv/.mythtv 2010-03-06 16:00:14.834 Empty LocalHostName. 2010-03-06 16:00:14.859 Using localhost value of mythtv 2010-03-06 16:00:14.889 New DB connection, total: 1 2010-03-06 16:00:14.912 Connected to database 'mythconverg' at host: localhost 2010-03-06 16:00:14.934 Closing DB connection named 'DBManager0' 2010-03-06 16:00:14.959 Connected to database 'mythconverg' at host: localhost 2010-03-06 16:00:14.987 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 16:00:15.009 MythTV database schema is old. Waiting to see if DB is being upgraded. 2010-03-06 16:00:16.034 New DB connection, total: 2 2010-03-06 16:00:16.092 Connected to database 'mythconverg' at host: localhost 2010-03-06 16:00:16.119 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 16:00:17.144 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 16:00:18.193 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 16:00:19.258 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 16:00:20.315 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 16:00:20.370 Timed out waiting. 2010-03-06 16:00:20.402 Backing up database with script: '/usr/share/mythtv/mythconverg_backup.pl' 2010-03-06 16:00:26.110 Database Backup complete. 2010-03-06 16:00:26.133 Backed up database to file: '/myth/tv/mythconverg-1215-20100306160020.sql.gz' 2010-03-06 16:00:26.165 Console is non-interactive, can't prompt user... 2010-03-06 16:00:26.198 Upgrading. 2010-03-06 16:00:26.224 Newest MythTV Schema Version : 1244 2010-03-06 16:00:28.105 New DB connection, total: 3 2010-03-06 16:00:28.124 Connected to database 'mythconverg' at host: localhost 2010-03-06 16:00:28.138 Upgrading to MythTV schema version 1216 2010-03-06 16:00:30.456 DB Error (Performing database upgrade): Query was: ALTER TABLE program MODIFY title varbinary(128) NOT NULL default '', MODIFY subtitle varbinary$ Error was: Driver error was [2/1054]: QMYSQL3: Unable to execute statement Database error was: Unknown column 'title_pronounce' in 'program'
Help
_________________ Retired KM user (R4 - R6.04); friend to LH users.
|
|
Top |
|
|
tjc
|
Posted: Sat Mar 06, 2010 4:09 pm |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
Top |
|
|
graysky
|
Posted: Sat Mar 06, 2010 5:02 pm |
|
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location:
/dev/null
|
tjc wrote: That matches what I saw.
Damn, if you weren't able to solve it, I doubt that I will be...
EDIT: here is the complete error log when I try to start my 0.22 (my above posts had truncated entries):
Code: 2010-03-06 18:08:58.534 Using runtime prefix = /usr 2010-03-06 18:08:58.633 Using configuration directory = /home/mythtv/.mythtv 2010-03-06 18:08:58.659 Empty LocalHostName. 2010-03-06 18:08:58.683 Using localhost value of mythtv 2010-03-06 18:08:58.714 New DB connection, total: 1 2010-03-06 18:08:58.737 Connected to database 'mythconverg' at host: localhost 2010-03-06 18:08:58.759 Closing DB connection named 'DBManager0' 2010-03-06 18:08:58.784 Connected to database 'mythconverg' at host: localhost 2010-03-06 18:08:58.811 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 18:08:58.834 MythTV database schema is old. Waiting to see if DB is being upgraded. 2010-03-06 18:08:59.859 New DB connection, total: 2 2010-03-06 18:08:59.908 Connected to database 'mythconverg' at host: localhost 2010-03-06 18:08:59.952 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 18:09:00.977 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 18:09:02.017 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 18:09:03.083 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 18:09:04.156 Current MythTV Schema Version (DBSchemaVer): 1215 2010-03-06 18:09:04.220 Timed out waiting. 2010-03-06 18:09:04.251 Backing up database with script: '/usr/share/mythtv/mythconverg_backup.pl' 2010-03-06 18:09:08.404 Database Backup complete. 2010-03-06 18:09:08.484 Backed up database to file: '/myth/tv/mythconverg-1215-20100306180904.sql.gz' 2010-03-06 18:09:08.516 Console is non-interactive, can't prompt user... 2010-03-06 18:09:08.548 Upgrading. 2010-03-06 18:09:08.649 Newest MythTV Schema Version : 1244 2010-03-06 18:09:10.425 New DB connection, total: 3 2010-03-06 18:09:10.483 Connected to database 'mythconverg' at host: localhost 2010-03-06 18:09:10.505 Upgrading to MythTV schema version 1216 2010-03-06 18:09:12.808 DB Error (Performing database upgrade): Query was: ALTER TABLE program MODIFY title varbinary(128) NOT NULL default '', MODIFY subtitle varbinary(128) NOT NULL default '', MODIFY description blob NOT NULL, MODIFY category varbinary(64) NOT NULL default '', MODIFY category_type varbinary(64) NOT NULL default '', MODIFY title_pronounce varbinary(128) NOT NULL default '', MODIFY seriesid varbinary(40) NOT NULL default '', MODIFY showtype varbinary(30) NOT NULL default '', MODIFY colorcode varbinary(20) NOT NULL default '', MODIFY syndicatedepisodenumber varbinary(20) NOT NULL default '', MODIFY programid varbinary(40) NOT NULL default ''; Error was: Driver error was [2/1054]: QMYSQL3: Unable to execute statement Database error was: Unknown column 'title_pronounce' in 'program' new version: 1216 2010-03-06 18:09:12.841 DB charset conversions update failed! Your database seems to be partially corrupted. Please move the backup to a safe place. Your database must be fixed before you can upgrade beyond 0.21-fixes. Please see http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding for information. 2010-03-06 18:09:12.866 Database Schema upgrade FAILED, unlocking. 2010-03-06 18:09:12.891 Couldn't upgrade database to new schema 2010-03-06 18:09:13.049 mythbackend version: branches/release-0-22-fixes [23566M] www.mythtv.org
Then it just repeats indefinitely. I have no idea why I have these db issues, nor how to fix them... if I just shitcan my current database, I assume that means that all of my captured content will be orphaned as well which isn't really an option.
_________________ Retired KM user (R4 - R6.04); friend to LH users.
Last edited by graysky on Sat Mar 06, 2010 5:14 pm, edited 2 times in total.
|
|
Top |
|
|