• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Error on upgrading to 10.1.1

P

PaulG

Guest
--------------------------------------------------------------
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk 10.0.1, CentOS5, 64 Bit, mySQL 5.5.8, PHP 5.2.17, Apache 2.2.17

PROBLEM DESCRIPTION AND STEPS TO REPRODUCE

Trying to upgrade to 10.1.1

ACTUAL RESULT

Fails with mySQL errors, see below

EXPECTED RESULT

Successful upgrade

ANY ADDITIONAL INFORMATION
--------------------------------------------------------------




===> Upgrading database

Trying to start service mysqld... mysqld (pid 23892) is running...
done
Trying to establish test connection... connected
done
Trying to find psa database... version is 01090
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.10.9.0-10.10.1.20110131-095319.dump.gz
no upgrade for 80
no upgrade for 81
no upgrade for 82
no upgrade for 83
no upgrade for 84
no upgrade for 86
no upgrade for 90
no upgrade for 92
no upgrade for 93
no upgrade for 95
no upgrade for 100
no upgrade for 101
no upgrade for 107
no upgrade for 108
===> Perform upgrade to 109
ERROR 1064 (42000) at line 25: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=InnoDB' at line 7
ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'innodb status' at line 1

ERROR while trying to upgrade SQL database from 1090
Check the error reason(see log file: /tmp/pp10.10.1-bootstrapper.110131.09.53.log), fix and try again


===> Restoring database from backup /var/lib/psa/dumps/mysql.preupgrade.10.9.0-10.10.1.20110131-095319.dump.gz


**** Product prep-install failed.

***** problem report *****
ERROR while trying to upgrade SQL database from 1090
Check the error reason(see log file: /tmp/pp10.10.1-bootstrapper.110131.09.53.log), fix and try again
 
Do you have any more detailed information from /tmp/pp10.10.1-bootstrapper.110131.09.53.log ?
 
Actually the file I quoted is where I got the above quote, there wasn't any more detail in it. Here's the whole thing:

**** 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
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


Trying to start service mysqld... mysqld (pid 23892) is running...
done
Checking for the system groups and users necessary for Apache...
Checking for the group 'apache'...
Group 'apache' already exists

Checking for the user 'apache'...
User 'apache' 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 'apache'... 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 mysqld... mysqld (pid 23892) 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.10.9.0-10.10.1.20110131-095317.dump.gz
Checking that /usr/local/psa/bin/chrootsh registered as login shell...
/usr/local/psa/bin/chrootsh already registered as a 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 'apache'... already there

===> Performing safe prep-install database actions

===> Checking MySQL DB consistency

===> Upgrading database

Trying to start service mysqld... mysqld (pid 23892) is running...
done
Trying to establish test connection... connected
done
Trying to find psa database... version is 01090
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.10.9.0-10.10.1.20110131-095319.dump.gz
no upgrade for 80
no upgrade for 81
no upgrade for 82
no upgrade for 83
no upgrade for 84
no upgrade for 86
no upgrade for 90
no upgrade for 92
no upgrade for 93
no upgrade for 95
no upgrade for 100
no upgrade for 101
no upgrade for 107
no upgrade for 108
===> Perform upgrade to 109
ERROR 1064 (42000) at line 25: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=InnoDB' at line 7
ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'innodb status' at line 1

ERROR while trying to upgrade SQL database from 1090
Check the error reason(see log file: /tmp/pp10.10.1-bootstrapper.110131.09.53.log), fix and try again


===> Restoring database from backup /var/lib/psa/dumps/mysql.preupgrade.10.9.0-10.10.1.20110131-095319.dump.gz


**** Product prep-install failed.

***** problem report *****
ERROR while trying to upgrade SQL database from 1090
Check the error reason(see log file: /tmp/pp10.10.1-bootstrapper.110131.09.53.log), fix and try again


The major part is here:

===> Perform upgrade to 109
ERROR 1064 (42000) at line 25: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'TYPE=InnoDB' at line 7
ERROR 1064 (42000) at line 1: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'innodb status' at line 1

ERROR while trying to upgrade SQL database from 1090
 
Last edited by a moderator:
It looks like some misconfiguration in /etc/my.cnf or wrong mysql version. Contact support team for investigation directly on your server.
 
How do I contact support and is there a charge for that?
 
I'd really like a fix from Parallels on this too. I don't feel like paying for support for something like this.
 
Its mysql 5.5, you can see the error coming from mysql up there in your logs. It doesnt recognize the format of the SQL response.
 
Back
Top