Closed Bug 480836 Opened 16 years ago Closed 16 years ago

checksetup.pl fails when converting tables to innodb

Categories

(Bugzilla :: Installation & Upgrading, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: jeff, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.6) Gecko/2009011913 Firefox/3.0.6 Build Identifier: 3.2.2 [root@slider bugzilla-3.2.2]# ./checksetup.pl * This is Bugzilla 3.2.2 on perl 5.8.5 * Running on Linux 2.6.9-67.0.7.ELsmp #1 SMP Wed Feb 27 04:48:20 EST 2008 ... Reading ./localconfig... Checking for DBD-mysql (v4.00) ok: found v4.006 Checking for MySQL (v4.1.2) ok: found v5.1.23-rc-community Removing index 'longdescs_thetext_idx' from the longdescs table... Bugzilla now uses the InnoDB storage engine in MySQL for most tables. Converting tables to InnoDB: Converting table attach_data... DBD::mysql::db do failed: Error on rename of './bugs3/#sql-86b_4' to './bugs3/attach_data' (errno: 121) [for Statement "ALTER TABLE attach_data TYPE = InnoDB"] at Bugzilla/DB/Mysql.pm line 329 Bugzilla::DB::Mysql::bz_setup_database('Bugzilla::DB::Mysql=HASH(0xb1b7d50)') called at ./checksetup.pl line 144 When you run the script again, it successfully converts the attach_data table but gets the same error on the next table. This continues (after run the script for each table until it gets to fielddefs and it will not continue after that point. This behavior continues even if databases are restored (by copying from production) and installation tarball untarred into new directory and localconfig and data directories copied. Even occurs with I am converting from 3.0.2 to 3.2.2. Reproducible: Always
I should have included the next run of checksetup... [root@slider bugzilla-3.2.2]# ./checksetup.pl * This is Bugzilla 3.2.2 on perl 5.8.5 * Running on Linux 2.6.9-67.0.7.ELsmp #1 SMP Wed Feb 27 04:48:20 EST 2008 ... Reading ./localconfig... Checking for DBD-mysql (v4.00) ok: found v4.006 Checking for MySQL (v4.1.2) ok: found v5.1.23-rc-community Bugzilla now uses the InnoDB storage engine in MySQL for most tables. Converting tables to InnoDB: Converting table attach_data... done. Converting table attachments... DBD::mysql::db do failed: Error on rename of './bugs3/#sql-9df_6' to './bugs3/attachments' (errno: 121) [for Statement "ALTER TABLE attachments TYPE = InnoDB"] at Bugzilla/DB/Mysql.pm line 329 Bugzilla::DB::Mysql::bz_setup_database('Bugzilla::DB::Mysql=HASH(0xa425d50)') called at ./checksetup.pl line 144
$ perror 121 OS error code 121: Remote I/O error Any disk errors in the logs?
...or the mysql server has dropped you - check its logs, too?
It turns out that the backup of the production database being used in test was done with the database open and it was causing some issues when it was converting the tables to Innodb. I have been able to get a clean backup of the database and do the upgrade cleanly. Sorry to have opened the bug.
This means there is some problem with your database: http://forums.mysql.com/read.php?22,33999,76181#msg-76181
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
(In reply to comment #4) > It turns out that the backup of the production database being used in test was > done with the database open and it was causing some issues when it was > converting the tables to Innodb. I have been able to get a clean backup of the > database and do the upgrade cleanly. Ah, didn't see this comment before I closed the bug. Yeah, that sounds like it could cause that error. Glad you were able to get it fixed.
You need to log in before you can comment on or make changes to this bug.