• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Solving some 8.0 to 8.1 problems

M

MarcosBL

Guest
Sorry for the bad english, just a quick note that could help someone:

After upgrading from 8.0 to 8.1 almost everything stopped working:

- Email
- DNS
- Plesk
- MySQL

While httpd seems to work fine... but my vhost are completly lost... every host points to Plesk default page.

When i try to login in Plesk i get a:

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

If i try to start Plesk via command line i get:

[root@llwb320 root]# service 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]
/usr/local/psa/admin/bin/httpsdctl start: httpd (pid 3377) already running
....

I get similar errors regarding database connectivity each time i ry to upgrade using the command line autoinstaller... so in the end my solution was:

# mysql -uadmin -pYOUR_DB_PASSWORD
mysql> use psa;
Database changed
mysql> UPDATE mysql.user SET Password=OLD_PASSWORD('YOUR_DB_PASSWORD') WHERE User='admin';
Query OK, 1 row affected (0.00 sec)
Rows matched: 1 Changed: 1 Warnings: 0
mysql> UPDATE mysql.user SET Password=OLD_PASSWORD('YOUR_DB_PASSWORD') WHERE User='root';
Query OK, 1 row affected (0.00 sec)
Rows matched: 1 Changed: 1 Warnings: 0
mysql> flush privileges;
Query OK, 0 rows affected (0.00 sec)
mysql> exit;
Bye



# /usr/local/psa/admin/bin/websrvmng -a -v

The first MySQL steps fixes the MySQL passwords (Notice the OLD_PASSWORD function) so the psa software can connect to the database. You need to flush privileges too in order to get the changes working.

The second step, websvrmng rebuilds the vhosts part, so everything works fine in my server now, a pretty old Fedora Core 1.

It was not so " just a quick note " in the end... but i hope it helps someone.
 
Back
Top