Hi,
I'm having the annoying problem, that my Plesk update/upgrade fails repeatedly with this error message:
After hours of searching and trying different workarounds, I found out that one workaround seems to be to just completely REMOVE the following line in "/etc/mysql/my.cnf":
BUT here comes the weird thing: this line is actually inserted by the PLESK BOOTSTRAPPER after each update / upgrade process!! And during the next Plesk Update process, the Bootstrapper fails again on his inserted line. I actually never had something like "old_passwords" in my "my.cnf"!
This is generally quite annoying and having to use this workaround prevents me from using the Plesk Auto-Update feature at all. It's even more frustrating than that because the failing Plesk-Auto-Updater shuts down all important services and does not restart them after the failed auto-update! So each day around 6:45 am, the WebServer, Xinetd Services, Mail Services etc. shut down and must manually be restarted.
Here's the complete Plesk log with the failing Auto-Update:
And here is the successful Plesk Auto-Update after removing "#old_passwords=1" in "my.cnf":
Anyone else has this problem? Any suggestions?
My Plesk Installation came from Plesk 9.0 with Debian 4.0 and is at the moment at 11.0.9 Update #16 with Debian 6.0.6.
I'm having the annoying problem, that my Plesk update/upgrade fails repeatedly with this error message:
ERROR while trying to disable old_passwords=1 in my.cnf
After hours of searching and trying different workarounds, I found out that one workaround seems to be to just completely REMOVE the following line in "/etc/mysql/my.cnf":
#old_passwords = 1
BUT here comes the weird thing: this line is actually inserted by the PLESK BOOTSTRAPPER after each update / upgrade process!! And during the next Plesk Update process, the Bootstrapper fails again on his inserted line. I actually never had something like "old_passwords" in my "my.cnf"!
This is generally quite annoying and having to use this workaround prevents me from using the Plesk Auto-Update feature at all. It's even more frustrating than that because the failing Plesk-Auto-Updater shuts down all important services and does not restart them after the failed auto-update! So each day around 6:45 am, the WebServer, Xinetd Services, Mail Services etc. shut down and must manually be restarted.
Here's the complete Plesk log with the failing Auto-Update:
START Bootstrapper 11.0.9 prep-install for BASE AT Sun Sep 23 06:57:06 CEST 2012
**** Product prep-install started.
===> Checking for previous installation ... found.
Create user 'psaadm' and group 'psaadm'
Checking for the group 'psaadm'...
Group 'psaadm' already exists
Checking for the user 'psaadm'...
User 'psaadm' already exists
Create group swkey-data
Checking for the group 'swkey-data'...
Group 'swkey-data' already exists
Checking for the group 'swkey-data'...
Trying to add supplementary group 'swkey-data' for user 'psaadm'... already there
Create Mail accounts
Checking for the group 'popuser'...
Group 'popuser' already exists
Checking for the user 'popuser'...
User 'popuser' already exists
Checking for the user 'mhandlers-user'...
User 'mhandlers-user' already exists
Trying to got legacy variables... done
config updated
===> Updated /etc/psa/psa.conf
Trying to save legacy variables... done
Checking for the system groups and users necessary for ftp server...
Checking for the group 'psaftp'...
Group 'psaftp' already exists
Checking for the user 'psaftp'...
User 'psaftp' already exists
Checking for the system groups and users necessary for Apache...
Checking for the group 'www-data'...
Group 'www-data' already exists
Checking for the user 'www-data'...
User 'www-data' already exists
===> Checking for the necessary system accounts
Checking for the system groups and users necessary for MySQL...
Checking for the group 'mysql'...
Group 'mysql' already exists
Checking for the user 'mysql'...
User 'mysql' already exists
Checking for the system groups and users necessary for admin server...
Checking for the group 'psaadm'...
Group 'psaadm' already exists
Checking for the user 'psaadm'...
User 'psaadm' already exists
Checking for the group 'psaserv'...
Group 'psaserv' already exists
Checking for the group 'psaserv'...
Trying to add supplementary group 'psaserv' for user 'www-data'... already there
Checking for the group 'psaserv'...
Trying to add supplementary group 'psaserv' for user 'psaftp'... already there
Checking for the group 'psaserv'...
Trying to add supplementary group 'psaserv' for user 'psaadm'... already there
Checking for the group 'psacln'...
Group 'psacln' already exists
Trying to start service mysql... /usr/sbin/mysqld (pid 1588) is running...
done
Trying to establish test connection... connected
done
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.11.0.9-11.0.9.20120923-065708.dump.gz
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
ERROR while trying to disable old_passwords=1 in my.cnf
Check the error reason(see log file: /tmp/plesk_11.0.9_installation.log), fix and try again
**** Product prep-install for BASE failed.
***** problem report *****
ERROR while trying to disable old_passwords=1 in my.cnf
Check the error reason(see log file: /tmp/plesk_11.0.9_installation.log), fix and try again
STOP Bootstrapper 11.0.9 prep-install for BASE AT Sun Sep 23 06:57:49 CEST 2012
And here is the successful Plesk Auto-Update after removing "#old_passwords=1" in "my.cnf":
Trying to start service mysql... /usr/sbin/mysqld is stopped
Starting MySQL database server: mysqld.
Checking for corrupt, not cleanly closed and upgrade needing tables finished..
done
Trying to establish test connection... connected
done
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.11.0.9-11.0.9.20120923-135826.dump.gz
Trying to restart service mysql... /usr/sbin/mysqld is stopped
Starting MySQL database server: mysqld.
NOTE: 'check_for_crashed_tables' is disabled because it takes too long, see: /etc/mysql/debian-start
Checking for corrupt, not cleanly closed and upgrade needing tables finished..
done
Checking that /opt/psa/bin/chrootsh registered as login shell...
Create PPSB support group
Checking for the group 'psasb'...
Group 'psasb' already exists
Checking for the group 'psasb'...
Trying to add supplementary group 'psasb' for user 'psaadm'... already there
Checking for the group 'psasb'...
Trying to add supplementary group 'psasb' for user 'www-data'... already there
===> Performing safe prep-install database actions
===> Upgrading database
Trying to start service mysql... /usr/sbin/mysqld is stopped
Starting MySQL database server: mysqld.
NOTE: 'check_for_crashed_tables' is disabled because it takes too long, see: /etc/mysql/debian-start
Checking for corrupt, not cleanly closed and upgrade needing tables finished..
done
Trying to establish test connection... connected
done
Trying to find psa database... version is 011009
Version is OK, no need to create psa database.
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.11.0.9-11.0.9.20120923-135902.dump.gz
no upgrade from 80
[...]
no upgrade from 1100
Trying to set psa database version to 011009...
**** Product prep-install for BASE completed successfully.
STOP Bootstrapper 11.0.9 prep-install for BASE AT Sun Sep 23 13:59:04 CEST 2012
Anyone else has this problem? Any suggestions?
My Plesk Installation came from Plesk 9.0 with Debian 4.0 and is at the moment at 11.0.9 Update #16 with Debian 6.0.6.