Article ID: 124098, created on Dec 30, 2014, last review on May 12, 2016

  • Applies to:
  • Plesk 12.5 for Linux
  • Plesk 12.0 for Linux
  • Plesk 11.0 for Linux
  • Plesk 11.5 for Linux
  • Plesk 12.0 for Windows
  • Plesk 11.5 for Windows


Migration finished with the following warning:

An error occurred during domain update: An error occurred during changing of hosting settings: System user update is failed: User <username> already exists.

Subscription deployment is implemented with no/partial physical hosting or content on the destination server as a result.


Plesk was unable to create local/FTP user during deployment, since it's already created.


  1. Log in to Plesk database:

    # plesk db
  2. Check 'accounts' table on the source server for blank passwords:

    mysql> select * from accounts where password='';
  3. Make sure the user exists on the destination server:

    # grep <username> /etc/passwd
    # grep ftp <username> /etc/passwd` --for ftp user
  4. Delete that user from the destination server:

    # userdel <username>
  5. To be rest assured that no orphaned records of this user are still in Plesk's database perform:

    # plesk db
    DELETE FROM sys_users WHERE login = '<username>';
  6. Resume to transfering.

Search Words


Migration failed [P5]

An error occurred during changing of hosting settings

user already exists

unable to migrate

Broken referencial integrity: Database id 34 is not found in data_bases

unable to update system user

sdd fdsfdsfefwef

backup restore


User already exists

Error: Fatal error: plesk::mail::postfix::PostfixConfigurationError(postmap: fatal: open database /var/spool/postfix/plesk/virtual.db: No such file or directory )

85a92ca67f2200d36506862eaa6ed6b8 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c aea4cd7bfd353ad7a1341a257ad4724a 29d1e90fd304f01e6420fbe60f66f838 0a53c5a9ca65a74d37ef5c5eaeb55d7f 01bc4c8cf5b7f01f815a7ada004154a2 46a8e394d6fa13134808921036a34da8 bd7fc88cf1b01f097749ae6f87272128 2a5151f57629129e26ff206d171fbb5f e335d9adf7edffca6a8af8039031a4c7 742559b1631652fadd74764ae8be475e ed7be2b984f9c27de1d2dc349dc19c6d a766cea0c28e23e978fa78ef81918ab8

Email subscription for changes to this article
Save as PDF