I’m trying to upgrade from 4.2.0 > 4.4.0 on Ubuntu Server 15.10 and have
been running into some snags. The first was that I had "ExternalAuthId"
with values in my RT4 database, as I was using that plug-in. Once I dropped
that table I was able to continue upgrading. However, my upgrade has
stalled at the following:
Upgrade from 4.3.12 to 4.3.13 (Incomplete) Fri Feb 26 08:31:50 2016 4.4.0 Schema updates from /tmp/rt-4.4.0/etc/upgrade/4.3.13 (Incomplete) Fri Feb
26 08:31:50 2016 4.4.0
I get the following error when running “make upgrade-database:”
Processing 4.3.13Now populating database schema.[16494] [Fri Feb 26
16:48:54 2016] [critical]: DBD::mysql::st execute failed: Can’t DROP
’IssueStatement’; check that column/key exists at
/tmp/rt-4.4.0/sbin/…/lib/RT/Handle.pm line 552.
(/tmp/rt-4.4.0/sbin/…/lib/RT.pm:390)DBD::mysql::st execute failed: Can’t
DROP ‘IssueStatement’; check that column/key exists at
/tmp/rt-4.4.0/sbin/…/lib/RT/Handle.pm line 552.Makefile:391: recipe for
target ‘upgrade-database’ failedmake: *** [upgrade-database] Error 9
Listing the Tables in my RT4 database doesn’t show any such table, nor does
listing all rows in each column. I assume the error is because
IssuerStatement doesn’t exist, so it fails. However, I am completely
clueless to this reference. Any help on this issue would be greatly
appreciated, as I have another RT server at another School that will have
the same issue. Thanks!
Sincerely,
Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext. 1111
Email Confidentiality Notice: This email message, including all
attachments, is for the sole use of the intended recipient(s) and contains
confidential information. If you are not the intended recipient, you may
not use, disclose, print, copy or disseminate this information. Please
reply and notify the sender, delete the message and any attachments and
destroy all copies.
I’m trying to upgrade from 4.2.0 > 4.4.0 on Ubuntu Server 15.10 and
have been running into some snags. The first was that I had
“ExternalAuthId” with values in my RT4 database, as I was using that
plug-in. Once I dropped that table I was able to continue upgrading.
However, my upgrade has stalled at the following:
Using something like : update users set externalauthid=null where
externalauthid is not null should do the trick. Don’t drop the users table.
I just did a test upgrade from 4.0.23 to 4.4.0 and we’re using
ExternalAuth too.
For those interested: we also use AssetTracker and I migrated all its
assets to the shine new RT::Assets
Got a question about something related but will post that in a new thread.
Thanks, Joop. I’ll restore my 4.2 database backup and run the following SQL
command on the database:
UPDATE users SET ExternalAuthID=null WHERE ExternalAuthId IS NOT null;
MySQL isn’t my strongest set of skills, but that is how I am understanding
your post. Thanks a lot for the quick response!
Sincerely,
Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext. 1111On Fri, Feb 26, 2016 at 2:59 PM, Joop jvdwege@xs4all.nl wrote:
On 26-2-2016 18:47, Lush, Aaron wrote:
I’m trying to upgrade from 4.2.0 > 4.4.0 on Ubuntu Server 15.10 and have
been running into some snags. The first was that I had “ExternalAuthId”
with values in my RT4 database, as I was using that plug-in. Once I dropped
that table I was able to continue upgrading. However, my upgrade has
stalled at the following:
Using something like : update users set externalauthid=null where
externalauthid is not null should do the trick. Don’t drop the users table.
I just did a test upgrade from 4.0.23 to 4.4.0 and we’re using
ExternalAuth too.
For those interested: we also use AssetTracker and I migrated all its
assets to the shine new RT::Assets
Got a question about something related but will post that in a new thread.
Email Confidentiality Notice: This email message, including all
attachments, is for the sole use of the intended recipient(s) and contains
confidential information. If you are not the intended recipient, you may
not use, disclose, print, copy or disseminate this information. Please
reply and notify the sender, delete the message and any attachments and
destroy all copies.
No w I am getting the following error when upgrading, after using the
UPDATE command listed below. This only occurs when upgrading from 4.3.9 to
4.3.10. Any further advice would be much appreciated!
Processing 4.3.10 Now populating database schema. [19046] [Fri Feb 26 21:33:59 2016] [critical]: DBD::mysql::st execute
failed: Table ‘Assets’ already exists at
/tmp/rt-4.4.0/sbin/…/lib/RT/Handle.pm line 552.
(/tmp/rt-4.4.0/sbin/…/lib/RT.pm:390) DBD::mysql::st execute failed: Table ‘Assets’ already exists at
/tmp/rt-4.4.0/sbin/…/lib/RT/Handle.pm line 552. Makefile:391: recipe for target ‘upgrade-database’ failed
Sincerely,
Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext. 1111On Fri, Feb 26, 2016 at 3:12 PM, Lush, Aaron alush@scentral.k12.in.us wrote:
Thanks, Joop. I’ll restore my 4.2 database backup and run the following
SQL command on the database:
UPDATE users SET ExternalAuthID=null WHERE ExternalAuthId IS NOT null;
MySQL isn’t my strongest set of skills, but that is how I am understanding
your post. Thanks a lot for the quick response!
Sincerely,
Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext. 1111
I’m trying to upgrade from 4.2.0 > 4.4.0 on Ubuntu Server 15.10 and have
been running into some snags. The first was that I had “ExternalAuthId”
with values in my RT4 database, as I was using that plug-in. Once I dropped
that table I was able to continue upgrading. However, my upgrade has
stalled at the following:
Using something like : update users set externalauthid=null where
externalauthid is not null should do the trick. Don’t drop the users table.
I just did a test upgrade from 4.0.23 to 4.4.0 and we’re using
ExternalAuth too.
For those interested: we also use AssetTracker and I migrated all its
assets to the shine new RT::Assets
Got a question about something related but will post that in a new thread.
Email Confidentiality Notice: This email message, including all
attachments, is for the sole use of the intended recipient(s) and contains
confidential information. If you are not the intended recipient, you may
not use, disclose, print, copy or disseminate this information. Please
reply and notify the sender, delete the message and any attachments and
destroy all copies.
No w I am getting the following error when upgrading, after using the
UPDATE command listed below. This only occurs when upgrading from
4.3.9 to 4.3.10. Any further advice would be much appreciated!
/Processing 4.3.10/
/Now populating database schema./
/[19046] [Fri Feb 26 21:33:59 2016] [critical]: DBD::mysql::st execute
failed: Table ‘Assets’ already exists at
/tmp/rt-4.4.0/sbin/…/lib/RT/Handle.pm line 552.
(/tmp/rt-4.4.0/sbin/…/lib/RT.pm:390)/
/DBD::mysql::st execute failed: Table ‘Assets’ already exists at
/tmp/rt-4.4.0/sbin/…/lib/RT/Handle.pm line 552./
/Makefile:391: recipe for target ‘upgrade-database’ failed/
That suggests that you have been using the Assets extension in 4.2.
I didn’t get that error when upgrading from 4.0.23 to 4.4, besides that
, I’m using postgres as a db backend but that shouldn’t matter.
I’ve attached my RT_SiteConfig to this email. I’m not using the Assets
extension, which is mind-boggling. All I’d used was the LDAP extension,
which you’ll see is commented out. This is driving me crazy, as it’s the
last hurdle before I can roll out my pilot program.
Any help would be greatly appreciated. Thanks!
Sincerely,
Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext. 1111On Fri, Feb 26, 2016 at 4:23 PM, Joop jvdwege@xs4all.nl wrote:
On 26-2-2016 22:39, Lush, Aaron wrote:
No w I am getting the following error when upgrading, after using the
UPDATE command listed below. This only occurs when upgrading from 4.3.9 to
4.3.10. Any further advice would be much appreciated!
Processing 4.3.10 Now populating database schema. [19046] [Fri Feb 26 21:33:59 2016] [critical]: DBD::mysql::st execute
failed: Table ‘Assets’ already exists at
/tmp/rt-4.4.0/sbin/…/lib/RT/Handle.pm line 552.
(/tmp/rt-4.4.0/sbin/…/lib/RT.pm:390) DBD::mysql::st execute failed: Table ‘Assets’ already exists at
/tmp/rt-4.4.0/sbin/…/lib/RT/Handle.pm line 552. Makefile:391: recipe for target ‘upgrade-database’ failed
That suggests that you have been using the Assets extension in 4.2.
I didn’t get that error when upgrading from 4.0.23 to 4.4, besides that ,
I’m using postgres as a db backend but that shouldn’t matter.
Email Confidentiality Notice: This email message, including all
attachments, is for the sole use of the intended recipient(s) and contains
confidential information. If you are not the intended recipient, you may
not use, disclose, print, copy or disseminate this information. Please
reply and notify the sender, delete the message and any attachments and
destroy all copies.
