Plesk 12 is hosed. [RESOLVED]

[weathermon]

Hi all,

I came in this morning and the Plesk 12 autoupdater had tried to update and then failed so I tried a repair as suggested in the control panel link but it has totally broken plesk now.. no mail being delivered for any domains and can't even log into Plesk at all via control panel (see screenshot).

I tried the bootstrapper repair /usr/local/psa/bootstrapper/pp12.0.18-bootstrapper/bootstrapper.sh repair but it showed up these warnings:


Passwords for some MySQL users were not upgraded.
All MySQL DB users that may be used by Panel MUST have passwords in new 41-character format in order for Panel to function properly.
Currently following users have passwords in old format: billing@localhost, sitebuilder_db@localhost, bug115166_68861@%, biancabrady@%, bug115166_14860@%, wordpress@%, aspcomplete@%, aspcomplete@localhost, aspcomplete@xxx, aspcsk@%, aspcsk@localhost, aspcsk@xxx, aspcss@%, aspcss@localhost, aspcss@xxx, aspsession@%, aspsession@localhost, aspsession@xxx.
Please ensure that MySQL server is not forced to use old password hashing algorithm and upgrade password format manually for users from the list above. Consult with MySQL server manual on detailed steps.
You may skip certain users if you are sure they weren't created and aren't used by Panel.

===> Plesk database was not upgraded completely. See installation log for details.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.


The system is running CentOS 5.11 with the Remi repo and never had any issues.. but now when I also try to do a yum update it's wanting to break dependencies:

---> Package tzdata.i386 0:2015f-1.el5 set to be updated
--> Finished Dependency Resolution
plesk-mysql-5.5.44-15061811.i386 from installed has depsolving problems
--> Missing Dependency: mysql = 5.5.44-15061811 is needed by package plesk-mysql-5.5.44-15061811.i386 (installed)
plesk-mysql-5.5.44-15061811.i386 from installed has depsolving problems
--> Missing Dependency: mysql-libs = 5.5.44-15061811 is needed by package plesk-mysql-5.5.44-15061811.i386 (installed)
plesk-mysql-5.5.44-15061811.i386 from installed has depsolving problems
--> Missing Dependency: mysql-server = 5.5.44-15061811 is needed by package plesk-mysql-5.5.44-15061811.i386 (installed)
--> Running transaction check
---> Package kernel-PAE.i686 0:2.6.18-398.el5 set to be erased
---> Package kernel-PAE-devel.i686 0:2.6.18-398.el5 set to be erased
--> Processing Dependency: mysql = 5.5.44-15061811 for package: plesk-mysql
--> Processing Dependency: mysql-libs = 5.5.44-15061811 for package: plesk-mysql
--> Processing Dependency: mysql-server = 5.5.44-15061811 for package: plesk-mysql
--> Finished Dependency Resolution
plesk-mysql-5.5.44-15061811.i386 from installed has depsolving problems
--> Missing Dependency: mysql = 5.5.44-15061811 is needed by package plesk-mysql-5.5.44-15061811.i386 (installed)
plesk-mysql-5.5.44-15061811.i386 from installed has depsolving problems
--> Missing Dependency: mysql-libs = 5.5.44-15061811 is needed by package plesk-mysql-5.5.44-15061811.i386 (installed)
plesk-mysql-5.5.44-15061811.i386 from installed has depsolving problems
--> Missing Dependency: mysql-server = 5.5.44-15061811 is needed by package plesk-mysql-5.5.44-15061811.i386 (installed)
Error: Missing Dependency: mysql-server = 5.5.44-15061811 is needed by package plesk-mysql-5.5.44-15061811.i386 (installed)
Error: Missing Dependency: mysql-libs = 5.5.44-15061811 is needed by package plesk-mysql-5.5.44-15061811.i386 (installed)
Error: Missing Dependency: mysql = 5.5.44-15061811 is needed by package plesk-mysql-5.5.44-15061811.i386 (installed)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest



I did a /etc/init.d/psa restart and I can now log into Plesk again but just wondering what I can do to solve the remi dependency issues.


Cheers, Mike

 

[danallen1]

It seems to me, the only way to be protected from this type of crash, where the database is hosed at the level of mysql passwords would to restore the whole server from backup. You probably will end up getting this fixed after a lot of hassle, but you should have to go through that. What should happen is that the update process should begin by making a snapshot of your whole system. If the update fails, just restore from that backup, end of story. Not enough disk to do that? That's called, you have bad job. How else can you be protected from your current agony? Sorting through the remnants like you are doing now has to be a situation to avoid.

I am at risk of this at the moment, while moving from one server with 100G of disk to 6 servers each with 20-30G. I don't have the backups setup yet, so I am headed right now to make sure automatic updating is available.

 

[weathermon]

Hi Danallen1,

The server is up and running again, everything is all working for plesk itself again (emails, web etc).. it's just the dependency issues that are a problem now. Backups are not an issue at all, we do nightly, weekly and monthly backups of the server (we host over 400 domains). I'm not sure if the latest REMI repo's are supporting Plesk 12 or not but that seems to be causing an error with updates.

 

[UFHH01]

Hi weathermon,

Passwords for some MySQL users were not upgraded.
All MySQL DB users that may be used by Panel MUST have passwords in new 41-character format in order for Panel to function properly.
Currently following users have passwords in old format: billing@localhost, sitebuilder_db@localhost, bug115166_68861@%, biancabrady@%, bug115166_14860@%, wordpress@%, aspcomplete@%, aspcomplete@localhost, aspcomplete@xxx, aspcsk@%, aspcsk@localhost, aspcsk@xxx, aspcss@%, aspcss@localhost, aspcss@xxx, aspsession@%, aspsession@localhost, aspsession@xxx.
Please ensure that MySQL server is not forced to use old password hashing algorithm and upgrade password format manually for users from the list above. Consult with MySQL server manual on detailed steps
You may skip certain users if you are sure they weren't created and aren't used by Panel.

Your MySQL - update/upgrade wasn't finished and the old state was restored, but the additional Plesk - PHP - packages will need this update/upgrade, if you want them to work on your server. The message points out very clear, which passwords have to be changed ( or unused eMail - accounts could be as well deleted ), so that the update/upgrade of MySQL - server can be finished and dependencies for the additional Plesk - PHP - packages can be resolved.

 

[weathermon]

Hi everyone,

Just letting you know I have solved the problems. I manually deleted the problematic MySQL entries, then ran the repairer - it was all ok with no errors now except for Roundcube which I also sorted out. The issues with the dependencies were resolved by this http://kb.odin.com/en/123659