5.2.9 Upgrade to 5.3 Error.

[TBT]

No support required as I was testing on Dev and already rolled back. But FYI, I ran the Web GUI Update for 5.3 and it did not complete successfully with the following error log.

...
Dashlets installed/updated OK
ALTER TABLE
ALTER TABLE
UPDATE 6
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
ALTER TABLE
CREATE SEQUENCE
CREATE TABLE
ERROR 1142 (42000) at line 39: ALTER command denied to user 'nagiosql'@'xxx.xxx.xxx.xxx' for table 'tbl_lnkServiceToHost'

[lmiltchev]

I was not able to recreate the issue. My upgrade from the web UI (5.2.9 to 5.3.0) completed with no issues.

example01.PNG

Have you limited nagiosql user to not allow altering the table? What is the output of the following command?

Code: Select all

echo "show grants for 'nagiosql'@'localhost';" | mysql -t -uroot -pnagiosxi nagiosql

[TBT]

Code: Select all

------------------------+
| GRANT USAGE ON . TO 'nagiosql'@'xxx.xxx.xxx.xxx' IDENTIFIED BY PASSWORD '*124773959909A94DDF2A7F78DD067589D4092EE7' |
| GRANT ALL PRIVILEGES ON `nagiosqldev`.* TO 'nagiosql'@'xxx.xxx.xxx.xxx'                                               |
+------------------------------------------------------------------------------------------------------------------+

[jomann]

Can you please update your upgrade script to on line 828 to use cfg__db_info__nagiosql__pwd instead of cfg__db_info__nagiosxi__pwd

This fix has been applied to the current tarball also, so you can also download the tarball. You will want to comment out the lines on 822 and 824 so that it doesn't try to re-run those mysql/psql upgrades or it may error out agian.

[TBT]

Can you please update your upgrade script to on line 828 to use cfg__db_info__nagiosql__pwd instead of cfg__db_info__nagiosxi__pwd

This fix has been applied to the current tarball also, so you can also download the tarball. You will want to comment out the lines on 822 and 824 so that it doesn't try to re-run those mysql/psql upgrades or it may error out agian.

Would it be best to upgrade using the tarball instead of the Web GUI so lint like this is cleaned up?

[jomann]

In this instance, since you already started the upgrade and it failed - I would recommend doing it from the CLI this time, just to make sure you get it upgraded.

[TBT]

So, trying this again with the tarball. Seems the upgrade script assumes a local database (IP of host), where in our case it is remote. Thus the same error occurs.

Is this attributed to what you suggested above, we need to still comment out 822/824 in the new tarball regardless?

This fix has been applied to the current tarball also, so you can also download the tarball. You will want to comment out the lines on 822 and 824 so that it doesn't try to re-run those mysql/psql upgrades or it may error out agian.

Please advise.

[ssax]

Is this attributed to what you suggested above, we need to still comment out 822/824 in the new tarball regardless?

Yes, since your DB has already been upgraded.

[dwhitfield]

5.3.1 should be out this week. At this point, it probably makes sense to just wait to upgrade, unless there is something very specific you need from 5.3.0.

[TBT]

5.3.1 should be out this week. At this point, it probably makes sense to just wait to upgrade, unless there is something very specific you need from 5.3.0.

Will 5.3.1 have a sanity check to avoid this, or will commenting lines 822/824 still be required?