[rt-users] FW: Issue upgrading to 4.2.x
I'm getting an error when doing upgrade-database on a 4.2 installation. I am coming from 4.0.7 and I am able to successfully upgrade to 4.0.18 without error. This is the message I'm getting after doing 'make upgrade-database' (highlighted below): /usr/bin/perl -I/opt/rt4/local/lib -I/opt/rt4/lib sbin/rt-setup-database --action upgrade --prompt-for-dba-password In order to create or update your RT database, this script needs to connect to your mysql instance on localhost (port '') as root Please specify that user's database password below. If the user has no database password, just press return. Password: Working with: Type: mysql Host: localhost Port: Name: rt4 User: rt_user DBA:root Enter RT version you're upgrading from: 4.0.18 Going to apply following upgrades: * 4.1.0 * 4.1.1 * 4.1.4 * 4.1.5 * 4.1.6 * 4.1.7 * 4.1.8 * 4.1.9 * 4.1.10 * 4.1.11 * 4.1.12 * 4.1.13 * 4.1.14 * 4.1.15 * 4.1.16 * 4.1.17 * 4.1.18 * 4.1.19 * 4.1.20 * 4.1.21 * 4.1.22 * 4.1.23 Enter RT version if you want to stop upgrade at some point, or leave it blank if you want apply above upgrades: IT'S VERY IMPORTANT TO BACK UP BEFORE THIS STEP Proceed [y/N]:y Processing 4.1.0 Now inserting data. Processing 4.1.1 Now populating database schema. [18504] [Wed Nov 20 17:27:58 2013] [critical]: DBD::mysql::st execute failed: Table 'ObjectScrips' already exists at /tmp/rt-4.2.0/sbin/../lib/RT/Handle.pm line 526. (/tmp/rt-4.2.0/sbin/../lib/RT.pm:391) DBD::mysql::st execute failed: Table 'ObjectScrips' already exists at /tmp/rt-4.2.0/sbin/../lib/RT/Handle.pm line 526. make: *** [upgrade-database] Error 255 Any help/input would be greatly appreciated. Adam Hutchins, Systems Administrator Town of Kernersville, NC, USA o-336.992.5456 m-336.529.7164 This email message, and any attachment(s) hereto, as well as any email message(s) that may be sent in response to it, may be considered Public Record, and as such are subject to requests for review. If you are not the intended recipient, please destroy this message and inform the sender immediately. The information contained in this email may be confidential and, in any event, is intended only for the use of the entity or individual to whom it is addressed. Thank you.
Re: [rt-users] FW: Issue upgrading to 4.2.x
On Wed, 2013-11-20 at 13:56 -0500, Adam Hutchins wrote: [18504] [Wed Nov 20 17:27:58 2013] [critical]: DBD::mysql::st execute failed: Table 'ObjectScrips' already exists at /tmp/rt-4.2.0/sbin/../lib/RT/Handle.pm line 526. (/tmp/rt-4.2.0/sbin/../lib/RT.pm:391) DBD::mysql::st execute failed: Table 'ObjectScrips' already exists at /tmp/rt-4.2.0/sbin/../lib/RT/Handle.pm line 526. Have you tried to upgrade this RT instance previously? What extensions are installed, or have been at some point? - Alex
Re: [rt-users] FW: Issue upgrading to 4.2.x
Please keep all replies on-list. On Wed, 2013-11-20 at 14:10 -0500, Adam Hutchins wrote: I have upgraded it in the past from 3.x to 4.0.7. And I was successful with 4.0.7 to 4.0.18 today. It's the jump to 4.2.x that's giving me errors. Did you attempt the 4.0 - 4.2 upgrade at some earlier point? I'm not using any extensions at this time. Have you ever? RT has not, prior to RT 4.2, shipped an ObjectScrips table, yet you are finding one -- the question is how it got there. Please show the output of: mysql -u root rt4 -p -e select Content from Attributes where Name = 'UpgradeHistory' - Alex
Re: [rt-users] FW: Issue upgrading to 4.2.x
Please see my replies below. Adam Hutchins, Systems Administrator Town of Kernersville, NC, USA o-336.992.5456 m-336.529.7164 -Original Message- From: Alex Vandiver [mailto:ale...@bestpractical.com] Sent: Wednesday, November 20, 2013 2:28 PM To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] FW: Issue upgrading to 4.2.x Please keep all replies on-list. On Wed, 2013-11-20 at 14:10 -0500, Adam Hutchins wrote: I have upgraded it in the past from 3.x to 4.0.7. And I was successful with 4.0.7 to 4.0.18 today. It's the jump to 4.2.x that's giving me errors. Did you attempt the 4.0 - 4.2 upgrade at some earlier point? Not that I'm aware of. I'm not using any extensions at this time. Have you ever? RT has not, prior to RT 4.2, shipped an ObjectScrips table, yet you are finding one -- the question is how it got there. The only extension I think I have used in the past was the GD library for Charts... etc... Please show the output of: mysql -u root rt4 -p -e select Content from Attributes where Name = 'UpgradeHistory' It returns no output. - Alex This email message, and any attachment(s) hereto, as well as any email message(s) that may be sent in response to it, may be considered Public Record, and as such are subject to requests for review. If you are not the intended recipient, please destroy this message and inform the sender immediately. The information contained in this email may be confidential and, in any event, is intended only for the use of the entity or individual to whom it is addressed. Thank you.
Re: [rt-users] FW: Issue upgrading to 4.2.x
On Wed, 2013-11-20 at 14:34 -0500, Adam Hutchins wrote: Did you attempt the 4.0 - 4.2 upgrade at some earlier point? Not that I'm aware of. That's extremely odd. Can you show the output of: mysqldump -u root rt4 -p --no-data - Alex
Re: [rt-users] FW: Issue upgrading to 4.2.x
`Users`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `Users` ( `id` int(11) NOT NULL AUTO_INCREMENT, `Name` varchar(200) NOT NULL, `Password` varchar(256) DEFAULT NULL, `Comments` text, `Signature` text, `EmailAddress` varchar(120) DEFAULT NULL, `FreeformContactInfo` text, `Organization` varchar(200) DEFAULT NULL, `RealName` varchar(120) DEFAULT NULL, `NickName` varchar(16) DEFAULT NULL, `Lang` varchar(16) DEFAULT NULL, `EmailEncoding` varchar(16) DEFAULT NULL, `WebEncoding` varchar(16) DEFAULT NULL, `ExternalContactInfoId` varchar(100) DEFAULT NULL, `ContactInfoSystem` varchar(30) DEFAULT NULL, `ExternalAuthId` varchar(100) DEFAULT NULL, `AuthSystem` varchar(30) DEFAULT NULL, `Gecos` varchar(16) DEFAULT NULL, `HomePhone` varchar(30) DEFAULT NULL, `WorkPhone` varchar(30) DEFAULT NULL, `MobilePhone` varchar(30) DEFAULT NULL, `PagerPhone` varchar(30) DEFAULT NULL, `Address1` varchar(200) DEFAULT NULL, `Address2` varchar(200) DEFAULT NULL, `City` varchar(100) DEFAULT NULL, `State` varchar(100) DEFAULT NULL, `Zip` varchar(16) DEFAULT NULL, `Country` varchar(50) DEFAULT NULL, `Timezone` varchar(50) DEFAULT NULL, `PGPKey` text, `Creator` int(11) NOT NULL DEFAULT '0', `Created` datetime DEFAULT NULL, `LastUpdatedBy` int(11) NOT NULL DEFAULT '0', `LastUpdated` datetime DEFAULT NULL, `AuthToken` varchar(16) CHARACTER SET ascii DEFAULT NULL, PRIMARY KEY (`id`), UNIQUE KEY `Users1` (`Name`), KEY `Users4` (`EmailAddress`) ) ENGINE=InnoDB AUTO_INCREMENT=31908 DEFAULT CHARSET=utf8; /*!40101 SET character_set_client = @saved_cs_client */; -- -- Table structure for table `sessions` -- DROP TABLE IF EXISTS `sessions`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `sessions` ( `id` char(32) NOT NULL, `a_session` longblob, `LastUpdated` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, PRIMARY KEY (`id`) ) ENGINE=InnoDB DEFAULT CHARSET=ascii; /*!40101 SET character_set_client = @saved_cs_client */; /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; /*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */; -- Dump completed on 2013-11-20 14:45:47 Adam Hutchins, Systems Administrator Town of Kernersville, NC, USA o-336.992.5456 m-336.529.7164 -Original Message- From: Alex Vandiver [mailto:ale...@bestpractical.com] Sent: Wednesday, November 20, 2013 2:45 PM To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] FW: Issue upgrading to 4.2.x On Wed, 2013-11-20 at 14:34 -0500, Adam Hutchins wrote: Did you attempt the 4.0 - 4.2 upgrade at some earlier point? Not that I'm aware of. That's extremely odd. Can you show the output of: mysqldump -u root rt4 -p --no-data - Alex This email message, and any attachment(s) hereto, as well as any email message(s) that may be sent in response to it, may be considered Public Record, and as such are subject to requests for review. If you are not the intended recipient, please destroy this message and inform the sender immediately. The information contained in this email may be confidential and, in any event, is intended only for the use of the entity or individual to whom it is addressed. Thank you.
Re: [rt-users] FW: Issue upgrading to 4.2.x
On Wed, 2013-11-20 at 14:46 -0500, Adam Hutchins wrote: On Wed, 2013-11-20 at 14:34 -0500, Adam Hutchins wrote: Did you attempt the 4.0 - 4.2 upgrade at some earlier point? Not that I'm aware of. That's extremely odd. Can you show the output of: mysqldump -u root rt4 -p --no-data This dump confirms that you either ran 'make initdb', or did a test upgrade, and did not drop the database before re-importing your backup. This results in some 4.2 tables still existing, with 4.0 schemas and data in the remainder of the database. Running: mysql -u root -p rt4 -e 'drop table ObjectScrips' ...should suffice to remove the extraneous table, and allow 'make upgrade-database' to complete. - Alex
Re: [rt-users] FW: Issue upgrading to 4.2.x
That worked! Thank you very much for your help! Adam Hutchins, Systems Administrator Town of Kernersville, NC, USA o-336.992.5456 m-336.529.7164 -Original Message- From: Alex Vandiver [mailto:ale...@bestpractical.com] Sent: Wednesday, November 20, 2013 3:05 PM To: rt-users@lists.bestpractical.com Subject: Re: [rt-users] FW: Issue upgrading to 4.2.x On Wed, 2013-11-20 at 14:46 -0500, Adam Hutchins wrote: On Wed, 2013-11-20 at 14:34 -0500, Adam Hutchins wrote: Did you attempt the 4.0 - 4.2 upgrade at some earlier point? Not that I'm aware of. That's extremely odd. Can you show the output of: mysqldump -u root rt4 -p --no-data This dump confirms that you either ran 'make initdb', or did a test upgrade, and did not drop the database before re-importing your backup. This results in some 4.2 tables still existing, with 4.0 schemas and data in the remainder of the database. Running: mysql -u root -p rt4 -e 'drop table ObjectScrips' ...should suffice to remove the extraneous table, and allow 'make upgrade-database' to complete. - Alex This email message, and any attachment(s) hereto, as well as any email message(s) that may be sent in response to it, may be considered Public Record, and as such are subject to requests for review. If you are not the intended recipient, please destroy this message and inform the sender immediately. The information contained in this email may be confidential and, in any event, is intended only for the use of the entity or individual to whom it is addressed. Thank you.
