• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Plesk 8.1.1 Mysql Client Error

D

dav666

Guest
Help I'm getting this error since upgrading plesk via the web based auto installer:

ERROR: PleskFatalException

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

0: /usr/local/psa/admin/auto_prepend/auth.php3:484

Please help.

Thank you.

Dav
 
Yes I have tried restarting mySQL, I also tried putting old_passwords in the my.cnf file, but no luck.

I'm really stuck with this one.

Thanks for your reply.

Any ideas?
 
Also tried rebooting the server just now and I still have the same issue :(
 
Here is the output of /etc/init.d/psa start

[root@web1 /]# /etc/init.d/psa start
Unable to connect to Plesk Database: Client does not support authentication protocol requested by server; consider upgrading MySQL client
Unable to connect to mysql database

System error 25: Inappropriate ioctl for device
Starting psa-spamassassin service: [FAILED]
websrvmng: Unable to connect to Plesk Database: Client does not support authentication protocol requested by server; consider upgrading MySQL client
websrvmng: Unable to connect to Plesk Database: Client does not support authentication protocol requested by server; consider upgrading MySQL client
websrvmng: Unable to connect to the mysql database
websrvmng: Unable to connect to the mysql database
/usr/local/psa/admin/bin/httpsdctl start: httpd (pid 3636) already running
Starting Plesk: [ OK ]
Starting up drwebd: Dr.Web (R) daemon for Linux/Plesk Edition v4.33 (4.33.0.09211)
Copyright (c) Igor Daniloff, 1992-2005
Doctor Web, Ltd., Moscow, Russia
Support service: http://support.drweb.com
To purchase: http://buy.drweb.com

Daemon version: 4.33.0 <API:2.1>
Engine version: 4.33 <API:2.1>
Loading /var/drweb/bases/drwtoday.vdb - Ok, virus records: 491
Loading /var/drweb/bases/drw43380.vdb - Ok, virus records: 906
Loading /var/drweb/bases/drw43379.vdb - Ok, virus records: 1485
Loading /var/drweb/bases/drw43378.vdb - Ok, virus records: 2545
Loading /var/drweb/bases/drw43377.vdb - Ok, virus records: 1031
Loading /var/drweb/bases/drw43376.vdb - Ok, virus records: 1390
Loading /var/drweb/bases/drw43375.vdb - Ok, virus records: 1633
Loading /var/drweb/bases/drw43374.vdb - Ok, virus records: 2090
Loading /var/drweb/bases/drw43373.vdb - Ok, virus records: 1252
Loading /var/drweb/bases/drw43372.vdb - Ok, virus records: 1289
Loading /var/drweb/bases/drw43371.vdb - Ok, virus records: 2370
Loading /var/drweb/bases/drw43370.vdb - Ok, virus records: 2022
Loading /var/drweb/bases/drw43369.vdb - Ok, virus records: 687
Loading /var/drweb/bases/drw43368.vdb - Ok, virus records: 1099
Loading /var/drweb/bases/drw43367.vdb - Ok, virus records: 1834
Loading /var/drweb/bases/drw43366.vdb - Ok, virus records: 4015
Loading /var/drweb/bases/drw43365.vdb - Ok, virus records: 1342
Loading /var/drweb/bases/drw43364.vdb - Ok, virus records: 1335
Loading /var/drweb/bases/drw43363.vdb - Ok, virus records: 1152
Loading /var/drweb/bases/drw43362.vdb - Ok, virus records: 1006
Loading /var/drweb/bases/drw43361.vdb - Ok, virus records: 878
Loading /var/drweb/bases/drw43360.vdb - Ok, virus records: 988
Loading /var/drweb/bases/drw43359.vdb - Ok, virus records: 1205
Loading /var/drweb/bases/drw43358.vdb - Ok, virus records: 1139
Loading /var/drweb/bases/drw43357.vdb - Ok, virus records: 1302
Loading /var/drweb/bases/drw43356.vdb - Ok, virus records: 1332
Loading /var/drweb/bases/drw43355.vdb - Ok, virus records: 2456
Loading /var/drweb/bases/drw43354.vdb - Ok, virus records: 1283
Loading /var/drweb/bases/drw43353.vdb - Ok, virus records: 795
Loading /var/drweb/bases/drw43352.vdb - Ok, virus records: 2016
Loading /var/drweb/bases/drw43351.vdb - Ok, virus records: 941
Loading /var/drweb/bases/drw43350.vdb - Ok, virus records: 1020
Loading /var/drweb/bases/drw43349.vdb - Ok, virus records: 1008
Loading /var/drweb/bases/drw43348.vdb - Ok, virus records: 1096
Loading /var/drweb/bases/drw43347.vdb - Ok, virus records: 707
Loading /var/drweb/bases/drw43346.vdb - Ok, virus records: 1428
Loading /var/drweb/bases/drw43345.vdb - Ok, virus records: 1358
Loading /var/drweb/bases/drw43344.vdb - Ok, virus records: 694
Loading /var/drweb/bases/drw43343.vdb - Ok, virus records: 1186
Loading /var/drweb/bases/drw43342.vdb - Ok, virus records: 744
Loading /var/drweb/bases/drw43341.vdb - Ok, virus records: 841
Loading /var/drweb/bases/drw43340.vdb - Ok, virus records: 822
Loading /var/drweb/bases/drw43339.vdb - Ok, virus records: 1071
Loading /var/drweb/bases/drw43338.vdb - Ok, virus records: 989
Loading /var/drweb/bases/drw43337.vdb - Ok, virus records: 855
Loading /var/drweb/bases/drw43336.vdb - Ok, virus records: 1297
Loading /var/drweb/bases/drw43335.vdb - Ok, virus records: 1195
Loading /var/drweb/bases/drw43334.vdb - Ok, virus records: 900
Loading /var/drweb/bases/drw43333.vdb - Ok, virus records: 1381
Loading /var/drweb/bases/drw43332.vdb - Ok, virus records: 1340
Loading /var/drweb/bases/drw43331.vdb - Ok, virus records: 2735
Loading /var/drweb/bases/drw43330.vdb - Ok, virus records: 2078
Loading /var/drweb/bases/drw43329.vdb - Ok, virus records: 2490
Loading /var/drweb/bases/drw43328.vdb - Ok, virus records: 743
Loading /var/drweb/bases/drw43327.vdb - Ok, virus records: 958
Loading /var/drweb/bases/drw43326.vdb - Ok, virus records: 793
Loading /var/drweb/bases/drw43325.vdb - Ok, virus records: 713
Loading /var/drweb/bases/drw43324.vdb - Ok, virus records: 655
Loading /var/drweb/bases/drw43323.vdb - Ok, virus records: 655
Loading /var/drweb/bases/drw43322.vdb - Ok, virus records: 778
Loading /var/drweb/bases/drw43321.vdb - Ok, virus records: 846
Loading /var/drweb/bases/drw43320.vdb - Ok, virus records: 808
Loading /var/drweb/bases/drw43319.vdb - Ok, virus records: 764
Loading /var/drweb/bases/drw43318.vdb - Ok, virus records: 838
Loading /var/drweb/bases/drw43317.vdb - Ok, virus records: 363
Loading /var/drweb/bases/drw43316.vdb - Ok, virus records: 730
Loading /var/drweb/bases/drw43315.vdb - Ok, virus records: 627
Loading /var/drweb/bases/drw43314.vdb - Ok, virus records: 824
Loading /var/drweb/bases/drw43313.vdb - Ok, virus records: 842
Loading /var/drweb/bases/drw43312.vdb - Ok, virus records: 830
Loading /var/drweb/bases/drw43311.vdb - Ok, virus records: 862
Loading /var/drweb/bases/drw43310.vdb - Ok, virus records: 853
Loading /var/drweb/bases/drw43309.vdb - Ok, virus records: 733
Loading /var/drweb/bases/drw43308.vdb - Ok, virus records: 708
Loading /var/drweb/bases/drw43307.vdb - Ok, virus records: 839
Loading /var/drweb/bases/drw43306.vdb - Ok, virus records: 930
Loading /var/drweb/bases/drw43305.vdb - Ok, virus records: 759
Loading /var/drweb/bases/drw43304.vdb - Ok, virus records: 721
Loading /var/drweb/bases/drw43303.vdb - Ok, virus records: 638
Loading /var/drweb/bases/drw43302.vdb - Ok, virus records: 806
Loading /var/drweb/bases/drw43301.vdb - Ok, virus records: 504
Loading /var/drweb/bases/drw43300.vdb - Ok, virus records: 24
Loading /var/drweb/bases/drwebase.vdb - Ok, virus records: 78674
Loading /var/drweb/bases/dwrtoday.vdb - Ok, virus records: 460
Loading /var/drweb/bases/dwr43301.vdb - Ok, virus records: 697
Loading /var/drweb/bases/drwrisky.vdb - Ok, virus records: 1271
Loading /var/drweb/bases/dwntoday.vdb - Ok, virus records: 324
Loading /var/drweb/bases/dwn43307.vdb - Ok, virus records: 854
Loading /var/drweb/bases/dwn43306.vdb - Ok, virus records: 781
Loading /var/drweb/bases/dwn43305.vdb - Ok, virus records: 752
Loading /var/drweb/bases/dwn43304.vdb - Ok, virus records: 793
Loading /var/drweb/bases/dwn43303.vdb - Ok, virus records: 766
Loading /var/drweb/bases/dwn43302.vdb - Ok, virus records: 850
Loading /var/drweb/bases/dwn43301.vdb - Ok, virus records: 772
Loading /var/drweb/bases/drwnasty.vdb - Ok, virus records: 4867
Total virus records: 185549
Key file: /opt/drweb/drweb32.key - Key file not found!
A path to a valid license key file does not specified.
Plesk authorization failed: malformed response (no 'response=' field).
Error: Plesk Software not running.
[FAILED]
 
I'm using CentOS 3.6 as my OS.

I'm guessing I just need to update Plesk's mySQL client library but I have no idea how?

Thanks for your help.
 
i think you can use yum to update, but i not use centos and don't know how...
 
Does anyone know a fix for this? I'm having the same problem. Upgraded to 8.1.1 from 8.1.0, all websites are down and get the same error message from plesk.
 
I called my server host, and they fixed it in a few minutes, but I would still like to know what the solution was.
 
My Plesk installation is still nuked, certain features don't work even after paying for a server engineer to fix them for me. They managed to get the site back up which is great!

I'm thinking about switching to CPanel soon. I've had nothing but trouble with Plesk.
 
Hi,
Regarding the issues with Plesk on your server.
The issue was caused by the MySQL server being upgraded along with Plesk.
This caused certain incompatibilities with the MySQL authentication protocol.

I was able to reset the MySQL admin password using the older protocol
and Plesk should now be working again.

Let us know if you have any questions

That's what my dedicated support sent me. I tried resetting the root (admin) password but left out OLD_PASSWORD function. So I'm assuming that's what the technician did.

Then I had to run /usr/local/psa/admin/sbin/websrvmng -a -v
to get my websites back up.
 
Back
Top