• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Can't upgrade from 11.0.9 to 11.5

Shibumi

Basic Pleskian
Hi,

I cannot upgrade from Plesk 11.0.9 to 11.5 because I have to upgrade the following accounts from 16 to 41 characters password hashes.

***********
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: aspcomplete@%, aspcomplete@localhost, aspcsk@%, aspcsk@localhost, aspcss@%, aspcss@localhost, aspsession@%, aspsession@localhost, billing@localhost, bug115166_79077@%.
***********

What are the passwords for these accounts? The same as admin?

Thanks for your help

With best regards
 
If you're seeing this message, then you've likely already upgraded.

It's fine to leave passwords in old format as long as Plesk or CBM don't use MySQL accounts. AFAIK, Plesk doesn't use any of these. CBM might, though (particularly billing@localhost). So, if you use only Plesk you have nothing to worry about. If you don't get any MySQL access errors, you likely have nothing to worry about as well.
 
Mh but the install breaks after that point with the passwords and than there is an error while executing a query.

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 $
You may skip certain users if you are sure they weren't created and aren't used by Panel.
ERROR while trying to execute SQL query, the query was: INSERT INTO `ServiceNodeConfiguration` (`serviceNodeId`, `section`, `name`, `value`) SELECT '1', 'webProxy', 'enabled', `v$
Check the error reason(see log file: /tmp/plesk_11.5.30_installation.log), fix and try again
STOP Bootstrapper 11.5.30 prep-install for BASE AT Wed Jul 3 15:25:59 CEST 2013
 
Mh when Table ServiceNodeProperties doesn't exists in Plesk 11.5 database. Maybe I should try to backup the db and delete the table ServiceNodeProperties before upgrade?
 
The table didn't exist in Plesk 11.0.9, but should exist in Plesk 11.5. Not sure I understood correctly what you are proposing, but feel free to do whatever you want as long as you have full server backup. :)

You may post results of following queries and it may help somebody to understand why do you have such problem:

SELECT * FROM misc WHERE param = 'version' OR param LIKE 'upgrader%';

SELECT * FROM upgrade_history;

SELECT * FROM ServiceNodeConfiguration WHERE name LIKE 'web%' OR section LIKE 'web%';

SELECT * FROM ServiceNodeProperties WHERE name LIKE 'server.%';

SELECT * FROM misc WHERE param LIKE '%port';
 
Mh from what I read in the thread of your link the table exists in 11.0.9 and not in 11.5. And it's correct that the table exists in my db from 11.0.9. So in 11.5 it shouldn't exist.

Here are my results:
# SELECT * FROM misc WHERE param = 'version' OR param LIKE 'upgrader%';
version | 011009

# SELECT * FROM upgrade_history;
2010-11-24 10:10:19 | 10.0.1 CentOS 5 109101029.18 | 01090 |
| 2010-11-24 17:24:19 | 10.0.1 CentOS 5 109101029.18 | 01090 |
| 2010-11-24 20:21:18 | 10.0.1 CentOS 5 109101029.18 | 01090 |
| 2011-01-04 14:26:21 | 10.0.1 CentOS 5 109101029.18 | 01090 |
| 2011-01-25 15:16:05 | 10.0.1 CentOS 5 109101029.18 | 010101 |
| 2011-02-11 16:07:05 | 10.1.1 CentOS 5 1010110120.18 | 010101 |
| 2011-03-09 10:38:16 | 10.1.1 CentOS 5 1010110120.18 | 010101 |
| 2011-05-14 19:56:51 | 10.1.1 CentOS 5 1010110120.18 | 010110 |
| 2011-05-30 09:27:42 | 10.2.0 CentOS 5 1011110331.11 | 010110 |
| 2011-08-18 10:00:02 | 10.2.0 CentOS 5 1011110331.11 | |
| 2012-07-02 18:24:18 | 10.4.4 | 10.3.1 |
| 2012-07-02 18:24:20 | 10.4.4 | 10.4.4 |
| 2012-07-02 20:30:25 | 11.0.9 | 11.0.9 |
| 2012-07-02 21:40:56 | 11.0.9 | 11.0.9 |
| 2012-07-17 23:03:17 | 11.0.9 | 11.0.9 |
| 2012-10-28 21:34:57 | 11.0.9 | 11.0.9 |
| 2013-04-09 08:25:55 | 11.0.9 | 11.0.9 |
| 2013-07-04 15:47:52 | 11.0.9 | 11.0.9 |
| 2013-07-05 13:00:02 | 11.0.9 | 11.0.9

#SELECT * FROM ServiceNodeConfiguration WHERE name LIKE 'web%' OR section LIKE 'web%';
| 1 | webProxy | enabled | false |
| 1 | webServer | httpPort | 80 |
| 1 | webServer | httpsPort | 443 |

#SELECT * FROM ServiceNodeProperties WHERE name LIKE 'server.%';
too much info

#SELECT * FROM misc WHERE param LIKE '%port';
| aps_port | 3306 |
 
#SELECT * FROM ServiceNodeProperties WHERE name LIKE 'server.%';
too much info

Oh, you skipped the most juicy part! :(

How about this query?

SELECT * FROM ServiceNodeProperties WHERE name LIKE 'server.webserver.%' OR name LIKE 'server.nginx.%';
 
Here is the result for
#SELECT * FROM ServiceNodeProperties WHERE name LIKE 'server.webserver.%' OR name LIKE 'server.nginx.%';
server.nginx.enabled | false |
server.webserver.httpPort | 80 |
server.webserver.httpsPort | 443 |

The other command are really a lot of informations:
#SELECT * FROM ServiceNodeProperties WHERE name LIKE 'server.%';
server.configuration.SNI_SUPPORT false
server.configuration.synced 1373085133
server.configuration.TAR_BIN /bin/tar
server.configuration.WEB_STAT /usr/bin/webalizer
server.ftpservice.FTP_Bandwidth 1
server.ftpservice.FTP_DiskQuota 1
server.ftpservice.FTP_PamFacility proftpd
server.ftpservice.FTP_Server ProFTPd
server.ftpservice.FTP_Server_package proftpd
server.nginx.enabled false
server.os.availableShells a:9:{s:10:"/bin/false";a:3:{s:4:"name";s:9:"Forbidden";s:5:"empty";b:1;s:8:"chrooted";b:0;}s:7:"/bin/sh";a:3:{s:4:"name";s:7:"/bin/sh";s:5:"empty";b:0;s:8:"chrooted";b:0;}s:9:"/bin/bash";a:3:{s:4:"name";s:9:"/bin/bash";s:5:"empty";b:0;s:8:"chrooted";b:0;}s:13:"/sbin/nologin";a:3:{s:4:"name";s:13:"/sbin/nologin";s:5:"empty";b:1;s:8:"chrooted";b:0;}s:9:"/bin/tcsh";a:3:{s:4:"name";s:9:"/bin/tcsh";s:5:"empty";b:0;s:8:"chrooted";b:0;}s:8:"/bin/csh";a:3:{s:4:"name";s:8:"/bin/csh";s:5:"empty";b:0;s:8:"chrooted";b:0;}s:8:"/bin/ksh";a:3:{s:4:"name";s:8:"/bin/ksh";s:5:"empty";b:0;s:8:"chrooted";b:0;}s:27:"/usr/local/psa/bin/chrootsh";a:3:{s:4:"name";s:20:"/bin/bash (chrooted)";s:5:"empty";b:0;s:8:"chrooted";b:1;}s:10:"/bin/rbash";a:3:{s:4:"name";s:10:"/bin/rbash";s:5:"empty";b:0;s:8:"chrooted";b:0;}}
server.os.emptyShell /bin/false
server.os.isHardQuotaEnabled false
server.os.synced 1373128029
server.packages.awstats 7.1.1-13040115.swsoft
server.packages.bind 9.3.6-20.P1.el5_8.6
server.packages.courier-imap 3.0.8-cos5.build1013120126.11
server.packages.health-monitor 11.0.9-cos5.build110120606.19
server.packages.httpd 2.2.17-1.el5.art
server.packages.mailman 2.1.9-6.el5_6.1
server.packages.mod_bw 0.8-12051014
server.packages.mod_perl 2.0.4-6.el5
server.packages.mod_python 3.2.8-4.el5
server.packages.mysql 5.5.32-18.el5.art
server.packages.nginx 1.3.0-1.12051815.centos5
server.packages.perl-Apache-ASP 2.59-0.93298
server.packages.php 5.3.25-18.el5.art
server.packages.postfix 2.8.4-12052415
server.packages.postgresql-server 8.1.23-6.el5_8
server.packages.PPSitebuilder 11.0.10-38713.12081600
server.packages.psa 11.0.9-cos5.build110120608.16
server.packages.psa-api-rpc 11.0.9-cos5.build110120608.16
server.packages.psa-atmail 1.05-5.el5.art
server.packages.psa-autoinstaller 3.12.1-120703.11
server.packages.psa-backup-manager 11.0.9-cos5.build110120608.16
server.packages.psa-horde 3.3.13-cos5.build110120606.19
server.packages.psa-imp 4.3.11-cos5.build110120606.19
server.packages.psa-logrotate 3.7-cos5.build1013111101.14
server.packages.psa-migration-manager 11.0.9-cos5.build110120608.16
server.packages.psa-mod-fcgid-configurator 2.0.0-cos5.build1013111101.14
server.packages.psa-proftpd 1.3.4c-4.el5.art
server.packages.psa-spamassassin 10.12.0-cos5.build1012110629.18
server.packages.psa-tomcat-configurator 11.0.9-cos5.build110120606.19
server.packages.psa-turba 2.3.6-cos5.build110120606.19
server.packages.spamassassin 3.3.2-7.el5.art
server.packages.SSHTerm 0.2.2-10.12012310
server.packages.synced 1373036039
server.packages.tomcat 5.5.23-0jpp.40.el5_9
server.packages.webalizer 2.01_10-30.1
server.webserver.httpPort 80
server.webserver.httpsPort 443
 
Why did you skip serviceNodeId column from this query? Do you even have it?

SELECT * FROM ServiceNodeProperties WHERE name LIKE 'server.webserver.%' OR name LIKE 'server.nginx.%';

Edit: please also post output of desc ServiceNodeProperties;
 
Last edited:
Mh didn't take care of the service nodes:
#SELECT * FROM ServiceNodeProperties WHERE name LIKE 'server.webserver.%' OR name LIKE 'server.nginx.%';
| 1 | server.nginx.enabled | false |
| 1 | server.webserver.httpPort | 80 |
| 1 | server.webserver.httpsPort | 443 |
 
Back
Top