1.15.8 to 1.17.2 Upgrader Error

twerth

Ubuntu: 18.04.6 LTS
Php: 8.1
MySQL: 5.7.40
osTicket: 1.15.8 -> 1.17.2

Good day,

When attempting to upgrade from 1.15.8 to 1.17.2, I am receiving the following error:

[core]: Upgrader Error
[CREATE TABLE ost_plugin_instance ( id int(11) unsigned NOT NULL AUTO_INCREMENT, plugin_id int(11) unsigned NOT NULL, flags int(10) NOT NULL DEFAULT 0, name varchar(128) NOT NULL DEFAULT '', config text DEFAULT NULL, notes text DEFAULT NULL, created datetime NOT NULL, updated datetime DEFAULT NULL, PRIMARY KEY (id), KEY plugin_id (plugin_id) ) DEFAULT CHARSET=utf8] Table 'ost_plugin_instance' already exists

Log Date: Wed, Jan 18 2023 10:48AM IP Address: 192.168.X.XXX

I have perused this forum for others with the same issue. I took the advice listed here and deleted all plug-ins prior to upgrade. When I attempted again, it yielded the same error. I have also attempted to upgrade to 1.17, which yielded the same error.

Does anyone have an idea what I could do to run a successful upgrade?

KevinTheJedi

twerth

You need to delete the plugin_instance table as it says that exists when it shouldn’t.

Cheers.

twerth

It worked, thank you @KevinTheJedi !

As general feedback, here is an issue I encountered:

I deleted the ldap auth plugin while logged in as an admin user which had authenticated via ldap ("ldap-user")
I copied the upload files over
When presented with the login screen, I attempted to log in with our dedicated local admin account ("local-admin"). However I received an error "Authorization Required". I copy and pasted from our pw database and am confident it was not an error on my end.
After restoring the files and db backups, I did exactly the same, but taking care to log in as local-admin before copying upload files.
Now, when I access the login screen again I can log in as local-admin and continue with the upgrade attempt.

This actually occurred for me several times, both on this recent successful upgrade attempt and one some previous attempts.

KevinTheJedi

twerth

If you’re agent account is tied to an authentication backend it’s good practice to set the account to "use any available backend" and set a local password if you don’t have one already.

Cheers.

KevinTheJedi

twerth

Clarification: Somehow I missed mentioning that this is only the case for upgrades. Otherwise it's totally okay to have your account tied to a specific auth backend.

Cheers.