• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Upgrade to 11.0.9 failed

MTL-Services

New Pleskian
Hello,

we tried upgrading our Centos server to Plesk 11.0.9.
Unfortunately, it failed with "ERROR while trying to upgrade SQL database from 10120".
/usr/local/psa/bootstrapper/pp11.0.9-bootstrapper/bootstrapper.sh repair
failed with the same result.
The suggested /tmp/plesk_11.0.9_installation.log doesnt give much information either:
Pending reads 0
Pending writes: LRU 0, flush list 0, single page 0
Pages made young 47, not young 0
0.00 youngs/s, 0.00 non-youngs/s
Pages read 1000, created 279, written 5461
0.00 reads/s, 0.00 creates/s, 0.50 writes/s
Buffer pool hit rate 1000 / 1000, young-making rate 0 / 1000 not 0 / 1000
Pages read ahead 0.00/s, evicted without access 0.00/s, Random read ahead 0.00/s
LRU len: 1279, unzip_LRU len: 0
I/O sum[0]:cur[0], unzip sum[0]:cur[0]
--------------
ROW OPERATIONS
--------------
0 queries inside InnoDB, 0 queries in queue
1 read views open inside InnoDB
Main thread process no. 24811, id 139712585320192, state: sleeping
Number of rows inserted 129766, updated 910, deleted 27, read 745004
0.03 inserts/s, 0.61 updates/s, 0.03 deletes/s, 2509.12 reads/s
----------------------------
END OF INNODB MONITOR OUTPUT
============================


ERROR while trying to upgrade SQL database from 10120
Check the error reason(see log file: /tmp/plesk_11.0.9_installation.log), fix and try again


===> Restoring database from backup /var/lib/psa/dumps/mysql.preupgrade.10.12.0-11.0.9.20130110-145609.dump.gz


**** Product repair failed.

Any suggestions?
 
Last edited:
It looks like that Plesk database is corrupted. It can be fixed with restoring correct database for the same Plesk version from dumps in /var/lib/psa/dumps but I strongly recommend you contact Support Team for fixing this complex issue.
 
Thanks for getting back to me, Igor. Is the Parallels support free of charge even if the license was obtained from our ISP?
 
In other words: let the customer pay for fixing a poorly written software (or update script)? Ergo Parallels charges double.
Interesting business approach!
 
Please use forum search - this question was discussed a lot of times... In short - you will be refunded if it is really our bug.
 
Back
Top