2026-05-02 09:01:34,632 - DEBUG - Starting the stage 'Update Plesk extensions'
2026-05-02 09:01:34,632 - INFO - Start stage 'Update Plesk extensions'.
2026-05-02 09:01:34,632 - DEBUG - Invoking action 'update Plesk extensions: docker, grafana, panel-migrator, ruby, site-import'
2026-05-02 09:01:34,632 - INFO - Do: update Plesk extensions: docker, grafana, panel-migrator, ruby, site-import
2026-05-02 09:01:42,613 - DEBUG - Currently installed extensions: {'monitoring', 'configurations-troubleshooter', 'mail-log', 'sslit', 'letsencrypt', 'git', 'composer', 'docker', 'laravel', 'nodejs', 'google-authenticator', 'revisium-antivirus', 'grafana', 'ssh-terminal', 'panel-migrator', 's3-backup', 'ssh-keys', 'plesk-sitejet', 'scheduled-backups-list', 'site-import', 'imunify360', 'sectigo', 'log-browser', 'firewall', 'xovi', 'repair-kit', 'wp-toolkit', 'joomla-toolkit', 'advisor'}
2026-05-02 09:01:42,613 - DEBUG - Going to update extensions: ['docker', 'grafana', 'panel-migrator', 'site-import']
2026-05-02 09:01:42,613 - INFO - Running: ['/usr/sbin/plesk', 'bin', 'extension', '-i', 'docker']. Output:
2026-05-02 09:02:16,136 - INFO - stderr: [2026-05-02 09:02:16.136] 32780:69f5bd771861d ERR [extension/docker] The execution of post-install.php has failed with the following message:
2026-05-02 09:02:16,548 - INFO - stderr: Execution installer has failed with exit code 1, stdout: , stderr: ERROR: ld.so: object 'libgcc_s.so.1' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
2026-05-02 09:02:16,549 - INFO - stderr: Cannot enable deb repository required for Docker engine
2026-05-02 09:02:16,549 - INFO - stderr: The execution of post-install.php has failed with the following message:
2026-05-02 09:02:16,568 - INFO - stderr: Execution installer has failed with exit code 1, stdout: , stderr: ERROR: ld.so: object 'libgcc_s.so.1' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
2026-05-02 09:02:16,569 - INFO - stderr: Cannot enable deb repository required for Docker engine
2026-05-02 09:02:16,569 - INFO - stderr:
2026-05-02 09:02:16,569 - INFO - stderr: exit status 1
2026-05-02 09:02:16,569 - ERROR - Command ['/usr/sbin/plesk', 'bin', 'extension', '-i', 'docker'] failed with return code 1
2026-05-02 09:02:16,578 - DEBUG - Disable systemd 'plesk-dist-upgrade-resume.service' service after conversion failure
2026-05-02 09:02:16,597 - INFO - Running: ['/bin/systemctl', 'disable', 'plesk-dist-upgrade-resume.service']. Output:
2026-05-02 09:02:16,617 - INFO - stderr: Removed /etc/systemd/system/multi-user.target.wants/plesk-dist-upgrade-resume.service.
2026-05-02 09:02:16,913 - INFO - Command ['/bin/systemctl', 'disable', 'plesk-dist-upgrade-resume.service'] finished successfully
2026-05-02 09:02:16,914 - ERROR - Failed: update Plesk extensions: docker, grafana, panel-migrator, ruby, site-import. The reason: Command '['/usr/sbin/plesk', 'bin', 'extension', '-i', 'docker']' returned non-zero exit status 1.
2026-05-02 09:02:17,375 - DEBUG - Going to write json '/usr/local/psa/var/debian11to12/actions.json' with new data
2026-05-02 09:02:17,439 - DEBUG - Sent error report
2026-05-02 09:02:17,454 - DEBUG - Trying to send status of conversion by report-update utility '/var/cache/parallels_installer/report-update'
2026-05-02 09:02:18,150 - ERROR - debian11to12 process has failed. Error: Failed: update Plesk extensions: docker, grafana, panel-migrator, ruby, site-import. The reason: Command '['/usr/sbin/plesk', 'bin', 'extension', '-i', 'docker']' returned non-zero exit status 1.
2026-05-02 09:02:18,151 - INFO - Going to free lockfile '/usr/local/psa/var/debian11to12/debian11to12.lock'...
2026-05-02 09:02:18,151 - INFO - Create signals handler with keep MOTD: True
So I was able to complete the upgrade, but wanted to make you aware of this potential bug/issue in the upgrade script.
Describe the bug
I ran the upgrade script and it failed at the
Update Plesk extensionsphase, specifically on the Docker extension:I then ran
/usr/sbin/plesk bin extension -i dockermanually on the command line, which finished successfully. After that I ran./debian11to12 --resumeto resume the process where it left off. This time, it was able to finish the upgrade.So I was able to complete the upgrade, but wanted to make you aware of this potential bug/issue in the upgrade script.
Feedback archive
debian11to12_feedback.zip