• 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.

Issue Plesk Migrator returned non-zero exit code

Azurel

Silver Pleskian
Server operating system version
AlmaLinux 9.8
Plesk version and microupdate number
18.0.80#1
Why I get this error in `panel.log`?:
[2026-08-09 03:19:37.386] 403696:6a77d5a95aa66 ERR [panel] Plesk Migrator returned non-zero exit code

COMMAND: '/usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator' 'summarize-statistics' '--quiet'

EXIT CODE: 1

STDOUT:
plesk-migrator: execve failed for /usr/local/psa/admin/sbin/modules//panel-migrator/plesk-migrator: No such file or directory

System error 2: No such file or directory


STDERR:
plesk-migrator: execve failed for /usr/local/psa/admin/sbin/modules//panel-migrator/plesk-migrator: No such file or directory

System error 2: No such file or directory

[2026-08-09 08:17:09.423] 2542:6a780d53dac93 ERR [panel] Could not ping database connection: DB query failed: (2002) SQLSTATE[HY000] [2002] No such file or directory

The reason is:

Code:
# ls -la /usr/local/psa/admin/sbin/modules/panel-migrator/
total 32
drwxr-xr-x  2 root root 4096 Aug  4 03:58 .
drwxr-xr-x 31 root root 4096 Aug  8 16:18 ..
-rwxr-xr-x  1 root root 1555 Aug  4 03:58 plesk-migrator
-rwxr-xr-x  1 root root  621 Aug  4 03:58 plesk-migrator.bat
-rwxr-xr-x  1 root root  398 Aug  4 03:58 plesk-migrator-post-install-files.sh
-rwxr-xr-x  1 root root 2379 Aug  4 03:58 plesk-migrator-post-install-packages.sh
-rwxr-xr-x  1 root root  215 Aug  4 03:58 plesk-migrator-post-install-var-dir.sh
-rwxr-xr-x  1 root root   36 Aug  4 03:58 pre-uninstall.sh


# plesk bin extension --list | grep -i migrat
panel-migrator - Plesk Migrator

# head -1 /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator
#!/opt/plesk/python/3/bin/python

# ls -la /opt/plesk/python/3/bin
total 16
drwxr-xr-x 2 root root 4096 Aug  7 08:36 .
drwxr-xr-x 4 root root 4096 Aug  7 08:36 ..
-rwxr-xr-x 1 root root  234 Apr 22 03:50 inv
-rwxr-xr-x 1 root root  234 Apr 22 03:50 invoke

"python" is missing. How to fix this?
 
Sounds like the extension might be corrupted. Could you please try uninstalling/installing it:

Code:
plesk bin extension --uninstall panel-migrator

plesk bin extension --install panel-migrator
 
Thanks.

Code:
# plesk bin extension --uninstall panel-migrator
The extension was successfully removed.

# plesk bin extension --install panel-migrator
The extension was successfully installed.

# ls -la /opt/plesk/python/3/bin
total 3836
drwxr-xr-x 2 root root    4096 Aug 10 12:42 .
drwxr-xr-x 5 root root    4096 Aug 10 12:42 ..
-rwxr-xr-x 1 root root     234 Apr 22 03:50 inv
-rwxr-xr-x 1 root root     234 Apr 22 03:50 invoke
lrwxrwxrwx 1 root root       4 Feb  2  2026 pip -> pip3
-rwxr-xr-x 1 root root     235 Feb  2  2026 pip3
-rwxr-xr-x 1 root root     235 Feb  2  2026 pip3.10
lrwxrwxrwx 1 root root       7 Feb  2  2026 python -> python3
lrwxrwxrwx 1 root root      10 Feb  2  2026 python3 -> python3.10
-rwxr-xr-x 1 root root 3900624 Feb  2  2026 python3.10

I'll check over the next few days to see if the error message disappears from panel.log.

=========

Is anything else broken? Today I get first time in panel.log this:
[2026-08-10 01:48:07.275] 188479:6a7911b248800 ERR [extension/composer] Could not update plugin on the domain 'DomainA.de': Domain DomainA.de has standard forwarding configured. This operation is available only for domains with web hosting..
[2026-08-10 01:48:07.275] 188479:6a7911b248800 ERR [extension/composer] Could not update plugin on the domain 'DomainA.com': Domain DomainA.com has standard forwarding configured. This operation is available only for domains with web hosting..
[2026-08-10 01:48:07.275] 188479:6a7911b248800 ERR [extension/composer] Could not update plugin on the domain 'DomainB.de': Domain DomainB.de has standard forwarding configured. This operation is available only for domains with web hosting..
[2026-08-10 01:48:07.275] 188479:6a7911b248800 ERR [extension/composer] Could not update plugin on the domain 'DomainB.com': Domain DomainB.com has standard forwarding configured. This operation is available only for domains with web hosting..

I haven't installed the "PHP Composer" extension by myself (auto installed?), and domainA and domainB are forwarded domains. I have disabled the "PHP Composer" extension.
 
[2026-08-10 01:48:07.275] 188479:6a7911b248800 ERR [extension/composer] Could not update plugin on the domain 'DomainB.com': Domain DomainB.com has standard forwarding configured. This operation is available only for domains with web hosting..

If there's no physical hosting configured for the domain names, the behavior is expected. The extension is available by default and is installed out of the box as of Plesk Obsidian.
 
I understand that this is expected behavior for domains without physical hosting. However, logging this as an "ERR" in panel.log seems rather unnecessary to me, as I don't see any practical benefit in logging such an expected condition. In my case, I have disabled the Composer extension anyway, so it is not an issue for me.

One additional question: Does plesk repair also perform checks/repairs for Plesk extensions? If not, is such functionality planned for a future version?
 
Back
Top