• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

12.5 Upgrade: ALTER TABLE `db_users` CHANGE `login`

Powie

Regular Pleskian
Hello, at one of my machines the upgrade failes with these error:

ERROR while trying to execute SQL query, the query was: ALTER TABLE `db_users` CHANGE `login` `login` VARCHAR(128) NOT NULL
Check the error reason(see log file: /var/log/plesk/install/plesk_12.5.30_installation.log), fix and try again

In PMA I can see that this field always has this settings...
 
Hi,

have you had a look in the log file?
Are there any additional hints on why this might be failing?

Regards,
Kristian
 
Yes, it seems that this isn't the error, this is only what will be showed.

In the log file I found this error some lines before,



===> Cumulative upgrade of APS controller database has been completed.
===> Cumulative Plesk database upgrade (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
ERROR 1062 (23000) at line 1: Duplicate entry '1-88-austriangeeks' for key 'db_server_id'
InnoDB<><------>
=====================================
151023 7:11:01 INNODB MONITOR OUTPUT
=====================================
.....
 
Hi @Powie!

Thank you for reporting the issue. I confirm it is a bug with ID PPP-18219 in our internal tracker.

As a workaround I can recommend you to change one of logins to another one so the the don't match case insensitevly in Plesk 12.0 and after that upgrade to Plesk 12.5
 
Hio,

yes, after renaming one of the logins the upgrade was successfull

Thank you!
 
Back
Top