• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

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