Resolved Migration issue [when admin username differs from "admin"]

[LevelupMedia]

Server operating system version

Debian 12.4

Plesk version and microupdate number

Version 18.0.57

Hi,

We are migrating server over new year, and we are having migration error, can't solve it:

We are migrating from latest to latest plesk, just debian versions are different, Debian 12.4 new one, and old is Debian 10.13

ERROR:
Failed to create the remote configuration dump on the target server. Not all settings may be migrated.
Error message: Command execution failed on the local server with non-zero exit code.
command: rsync -l --chmod=Fug=rw,Dug=rwx,o= --timeout=30 -e 'ssh -i /usr/local/psa/var/modules/panel-migrator/sessions/20231231004810/ssh-keys/id_rsa.000.71 -p 22 -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o GSSAPIAuthentication=no' [email protected]:/root/plesk_migrator/plesk_migrator-f653vqgl448cjnuhpsmhalyzdsyeq1fi/backup.tar /usr/local/psa/var/modules/panel-migrator/sessions/20231231004810/plesk.backup.source.downloaded.dump.tar
exit code: 23
stdout:
stderr: rsync: link_stat "/root/plesk_migrator/plesk_migrator-f653vqgl448cjnuhpsmhalyzdsyeq1fi/backup.tar" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1865) [Receiver=3.2.7]
rsync: [Receiver] write error: Broken pipe (32)

 

[Peter Debik]

Please try to update backup permissions:
# chown root:root /backups/plesk_backup_tmp/
# chmod 1777 /backups/plesk_backup_tmp/
Then restart the migration. Does this solve the issue?

 

[Peter Debik]

You could also check on the target server whether the following error is found in a migration's session log files in folder /usr/local/psa/var/modules/panel-migrator/sessions/<datetime>/:
"The following subscriptions do not exist: exam<200b>ple.com" (or similar)
In that case, DNS records contain invalid zero-width character. Could that be the case?

 

[LevelupMedia]

Please try to update backup permissions:
# chown root:root /backups/plesk_backup_tmp/
# chmod 1777 /backups/plesk_backup_tmp/
Then restart the migration. Does this solve the issue?

Hi, for this particular issue issue was that on old server there was setting if there was no 400 gb of space that backup would not start, when we removed it it was resolved.

 

[LevelupMedia]

But we can't find solution for these two issues and we couldn't find anything on forum or documentation;


Main one is that database users are not created (many sites tried):

"START: Deploy database users
2023-12-31 07:19:04 Warning
Database user 'wp_sbk56' belongs to database 'admin_aishmgzz' which is not registered in Plesk, but already exists in Plesk database server, so skip the database user"

Second one is:

"Attempt #1 failed with the following error:
Restoration of hosting settings (addon domains, mailboxes, PHP settings, etc) of subscription failed.
Check PMM restoration logs for more details.
Error code: 1000
Error message: PHP Warning: Attempt to read property "guid" on null; File: /opt/psa/admin/plib/backup/Conflicts/Detector.php, Line: 439

PHP Warning: Attempt to read property "guid" on null in /opt/psa/admin/plib/backup/Conflicts/Detector.php on line 439
Error: Can not find IP addresses for owner specified as [2023-12-31 07:14:26.690] 175116:659106c2a79ff ERR [panel] PleskUserException: Can not find IP addresses for owner specified as in /opt/psa/admin/plib/backup/Conflicts/PleskDataManager.php:702
Stack trace:
#0 /opt/psa/admin/plib/backup/Conflicts/Detector.php(439): backup_Conflicts_PleskDataManager->getIpsByOwnerGuid(NULL)
#1 /opt/psa/admin/plib/backup/Conflicts/Detector.php(384): backup_Conflicts_Detector->_getIpAddressesForMapping(Object(DOMDocument))
#2 /opt/psa/admin/plib/backup/Conflicts/Detector.php(45): backup_Conflicts_Detector->_findConflicts(Object(DOMDocument))
#3 /opt/psa/admin/plib/backup/Conflicts/ConflictsRunner.php(81): backup_Conflicts_Detector->findConflicts()
#4 /opt/psa/admin/plib/backup/Conflicts/Runner.php(16): ConflictsRunner::run(Array)
#5 {main}"

 

[Peter Debik]

This is now a completely different issue. The reason for the database issue is that a migration was attempted before, so parts of migrated data are already present on the target system. You'll need to clear those parts. For example, if Migrator claims a database or a database user already exist, you will need to remove them before you try a fresh migration.

 

[LevelupMedia]

I understand that, but there are nothing to clean, we get this on first import, i have checked everything.

Second error is located in section "Restore hosting settings of subscription"

 

[LevelupMedia]

This is now a completely different issue. The reason for the database issue is that a migration was attempted before, so parts of migrated data are already present on the target system. You'll need to clear those parts. For example, if Migrator claims a database or a database user already exist, you will need to remove them before you try a fresh migration.

We found what's causing both issues and few more smaller issues.

Migrator is expecting to have admin user with username admin and if not found it's causing those issues, after fixing username all issues disappeared.

In log file: line: +|2023-12-31_06:00:59,029|D|ST1|core.utils.mysql|domain.com||Query: SELECT guid FROM clients WHERE type = 'admin' AND login = 'admin'

It would be good to open ticket about this, we already sent this to support.

 

[LevelupMedia]

Fixed: Migrating from a Plesk server no longer fails with the “Can not find IP addresses for owner” error if that server’s administrator account has a username other than “admin”. (PPPM-14240)