• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Resolved Server migration problem

Erwan

Regular Pleskian
HI,

We have a problem with a server migration. For one domain, we have this problem:

[17 Apr 17 23:23:09] [Migration] Failed to copy web files for subscription 'domainA.com'
Migration tools tried to perform operation in 3 attempts: Rsync failed to copy files from the source (the source server 'source' (x.x.x.x)) to the target server (target Plesk server): Command execution failed on the local server with non-zero exit code.
command: /usr/bin/rsync -e 'ssh -i /usr/local/psa/var/modules/panel-migrator/sessions/20170312212904/target-server/ssh-keys/id_rsa.x.x.x.x -p 22 -o PasswordAuthentication=no -o StrictHostKeyChecking=no -o GSSAPIAuthentication=no' --recursive --links --times --devices --specials --owner --group --perms --exclude=/logs --exclude=/conf --exclude=/statistics --exclude=/bin --exclude=/dev --exclude=/lib --exclude=/lib64 --exclude=/usr --exclude=/libexec --exclude=/etc --exclude=/tmp --exclude=/var [email protected]:/var/www/vhosts/domainA.com/ /var/www/vhosts/domainA.com/
exit code: 23
stdout: cannot delete non-empty directory: c2aa.domainA.com/current
cannot delete non-empty directory: www.domainA.com/current

stderr: could not make way for new symlink: c2aa.domainA.com/current
could not make way for new symlink: www.domainA.com/current
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1518) [generator=3.0.9]

This could happen because of a network connection issue. Run migration for that subscription once more.


Do you have an idea?
 
Are you using symbolic links in the domains in question? If the document root directory is a symbolic link instead of a real directory, migration will fail. However, in that case it is possible to ignore the error and create the symbolic links on the target manually.
 
Back
Top