J
JacobG
Guest
Last night, Plesk tried to auto-update itself from 11.0.9 Update #6 to whatever the most recent version is. During the upgrade process, it appears that something to do with the APS database failed, causing sites and Plesk to go offline.
Here is the excerpt from the update log:
--
ERROR 1050 (42S01) at line 19: Table '`apsc`.`aps_application`' already exists
ERROR 1227 (42000) at line 1: Access denied; you need (at least one of) the PROCESS privilege(s) for this operation
ERROR while trying to create database for APS controller
Check the error reason(see log file: /tmp/plesk_11.0.9_installation.log), fix and try again
**** Product post-install for BASE failed.
***** problem report *****
ERROR while trying to create database for APS controller
Check the error reason(see log file: /tmp/plesk_11.0.9_installation.log), fix and try again
STOP Bootstrapper 11.0.9 post-install for BASE AT Fri Jul 27 03:38:59 MDT 2012
To complete product installation one should run bootstrapper script:
/usr/local/psa/bootstrapper/pp11.0.9-bootstrapper/bootstrapper.sh repair
--
Before trying to update again, I'd like to make sure that it doesn't cause another outage for our clients.
Any help is appreciated!
Thanks
Here is the excerpt from the update log:
--
ERROR 1050 (42S01) at line 19: Table '`apsc`.`aps_application`' already exists
ERROR 1227 (42000) at line 1: Access denied; you need (at least one of) the PROCESS privilege(s) for this operation
ERROR while trying to create database for APS controller
Check the error reason(see log file: /tmp/plesk_11.0.9_installation.log), fix and try again
**** Product post-install for BASE failed.
***** problem report *****
ERROR while trying to create database for APS controller
Check the error reason(see log file: /tmp/plesk_11.0.9_installation.log), fix and try again
STOP Bootstrapper 11.0.9 post-install for BASE AT Fri Jul 27 03:38:59 MDT 2012
To complete product installation one should run bootstrapper script:
/usr/local/psa/bootstrapper/pp11.0.9-bootstrapper/bootstrapper.sh repair
--
Before trying to update again, I'd like to make sure that it doesn't cause another outage for our clients.
Any help is appreciated!
Thanks