Plsek 8.4.0 ? Options

[pedrodj]

I have updated to plesk 8.4.0 but now i have some problems

Service is not available now, probably your Plesk is misconfigured.
Contact Your provider for details.

Internal Plesk error occurred: Components::componentUpdate() failed: Unable to exec utility packagemng: packagemng: Unable to connect to Plesk Database: Client does not support authentication protocol requested by server; consider upgrading MySQL client packagemng: Unable to connect to the mysql database

and all my sites have a default page of plesk


I have tryed to set OLD_PASSWORD in /etc/my.cnf and

mysql> UPDATE mysql.user SET Password=OLD_PASSWORD('*******')
-> WHERE Host ='localhost' AND User ='root' ;

but nothing changed, except the error message when i TRY to use my Plesk Control Panel

"Service is not available now, probably your Plesk is misconfigured.
Contact Your provider for details.

Internal Plesk error occurred: Unable to connect to database: saved admin password is incorrect."

How Can i resolve ?

[agruetz]

1) root is not the mysql admin user for plesk, it is admin
2) even if you set the admin password in mysql to something new thats all fine but you also have to change it in /etc/psa/.psa.shadow

That should fix your issue.

[markcausa]

Impressive insight, Anthony (that's my middle name, btw.)

[ElviCities]

Looks like SW-Soft......er I mean Parallels has pulled 8.4 down from their http://autoinstall.plesk.com/ page, as well as from the auto-updater within the CP. Guess there were too many bugs like the one mentioned by Pedro above.

A rule of thumb with Plesk updates that I go by is to wait AT LEAST 2-3 weeks after a new update is out to make sure others aren't having any significant problems.

[markcausa]

Eck, Parallels...

[agruetz]

Looks like SW-Soft......er I mean Parallels has pulled 8.4 down from their http://autoinstall.plesk.com/ page, as well as from the auto-updater within the CP. Guess there were too many bugs like the one mentioned by Pedro above.

A rule of thumb with Plesk updates that I go by is to wait AT LEAST 2-3 weeks after a new update is out to make sure others aren't having any significant problems.

I updated it on 10 - 15 servers without a problem. Most minor release do not have many issues it is when they start tinkering with the database is when you need to be careful. As well as doing big upgrade jumps ie like from 7.x to 8.4 or something like that. Thats just my experience though. Also if you have done things to the server outside of plesk that also will tend to throw a wrench in things like upgrades.

[ideasmultiples]

Access to 3.4 lupgrades or new install ocked for some days...

We need to block access to 8.4 Autoinstaller for couple of days.
During this time, those who has managed to upgrade the product will not be able to get other updates.
Please check the official announcements on the Parallels site

.

[joec@home]

As there is already good into on here I'll just add my 2 cents:

Very first thing to do is verify the rpm install:

rpm -q psa

If there is a major bug then this will report multiple instances instead of just one. If this is the case you will need to roll back the installation. I have found an article on this but not yet tested it. If you are not so brave then put in a ticket requesting to have it sent to Parallels who typically will roll the installation back for you. Typically the newer versions already make backups before they run the upgrade, so this article is slightly dated.

How to backup Plesk
http://dancameron.org/pages/how-to-backup-plesk

The other thing to look for is the upgrade and error log in /tmp. Its name will be different depending on the version but it will stand out with a big PSA some where in its name.

[Bruce Haydon]

Hello - I am having the same problem, but was curious if you could give more step by step command line instructions. Just a little nervous about editing the PSA mySQL database directly.

So is this really just a login issue on the PSA dB?

Thanks so much,
Bruce