• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved After enabling MSMTP: sw-service unable to start

dbitsch

New Pleskian
Server operating system version
Ubuntu 22.04.2 LTS
Plesk version and microupdate number
18.0.54
Hi,

We have just upgraded our Plesk installation to the latest version available (18.0.53 -> 18.0.54). Then after the successful installation we switched from Postfix to MSMTP according to your installation instructions on: https://support.plesk.com/hc/en-us/...to-configure-an-external-SMTP-server-in-Plesk

The installation worked fine. Unfortunately the Plesk panel didn't came back up. The websites still work fine though.

As a quick solution we tried apt update & update, and in fact apache2 packages were hold back, and a couple plesk packages were upgraded. Sadly this didn't change anything. Is it safe to reboot? I'm fearing that all websites will be also down after rebooting.

Log of "plesk repair installation":
Code:
Reconfiguring the Plesk installation
  
Started bootstrapper repair procedure. This may take a while.
Certain actions may be skipped if not applicable.

 Finishing up upgrade procedures and rerunning previously failed upgrade actions...
===> Cumulative Plesk database upgrade and repair (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade and repair of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /opt/psa/bootstrapper/pp18.0.54-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.
===> Cumulative Plesk upgrade and repair (final stage) has been started.
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
 Reconfiguring mail subsystem...
 Reconfiguring Apache web server...
 Reconfiguring ProFTPD FTP server...
===> Configuring ProFTPD server
 Reconfiguring AWStats web statistics...
 Reconfiguring WatchDog...
 Restoring SELinux contexts...
Job for sw-engine.service failed because the control process exited with error code.
See "systemctl status sw-engine.service" and "journalctl -xeu sw-engine.service" for details.
INFO: [Thu Aug  3 23:51:23 CEST 2023]: Service: sw-engine, Action: start
 Trying to start service sw-engine... activating


*****  problem report *****
Warning: start service sw-engine failed

 Reconfiguring SSL ciphers and protocols...
 Regenerating web servers' configuration files...
 Cleaning active Panel sessions...
 Fixing permissions on Panel packages files
ERROR:Unable to retrieve repository configuration from autoinstaller: autoinstaller is busy
Changing permissions on /usr/lib/python2.7/dist-packages/fail2ban/server/filterpyinotify.pyc to 0o644

Bootstrapper repair finished.
Errors occurred while performing the following actions: fix Plesk packages permissions.
Check '/var/log/plesk/install/plesk_18.0.54_repair.log' and '/var/log/plesk/install/plesk_18.0.54_repair_problems.log' for details.
If you can't resolve the issue on your own, please address Plesk support.

exit status 1

/var/log/plesk/install/plesk_18.0.54_repair.log:
Code:
INFO: Executing upgrade task: 2019-02-18-14-09-55 (forced)
SUCCESS: Upgrade step 2019-02-18-14-09-55_InstallEssentialExtensions.php was successfully done.
INFO: Executing upgrade task: 2019-04-25-14-46-58 (forced)
SUCCESS: Upgrade step 2019-04-25-14-46-58_ReportUsage.php was successfully done.
INFO: Executing upgrade task: 2020-03-19-17-13-39 (forced)
SUCCESS: Upgrade step 2020-03-19-17-13-39_UpgradeExtensions.php was successfully done.
done
===> Cumulative Plesk upgrade and repair (final stage) has been started.
Upgrade or repair for 'core' (stage 'post') is not required
===> Preparing Plesk upgrade (final stage).
===> Cumulative upgrade and repair of Plesk (final stage) has been completed.
 Reconfiguring mail subsystem...
/usr/lib/plesk-9.0/mailsrv_entities_dump isn't yet on its place. Deferring mail_restore execution to a later stage
 Reconfiguring Apache web server...
 Reconfiguring ProFTPD FTP server...
 Reconfiguring AWStats web statistics...
 Reconfiguring WatchDog...
 Restoring SELinux contexts...
 Trying to register service sw-cp-server...  Trying to enable automatic respawn for service sw-cp-server.service... done
done
 Trying to register service sw-engine...  Trying to enable automatic respawn for service sw-engine.service... done
done
 Trying to register service nginx...  Trying to enable automatic respawn for service nginx.service... done
done
 Trying to register service psa...  Trying to enable automatic respawn for service psa.service... done
done
 Reconfiguring SSL ciphers and protocols...
 Trying to configure SSL ciphers and protocols for: ... done
 Regenerating web servers' configuration files...
 Cleaning active Panel sessions...
 Fixing permissions on Panel packages files

Bootstrapper repair finished.
Errors occurred while performing the following actions: fix Plesk packages permissions.
Check '/var/log/plesk/install/plesk_18.0.54_repair.log' and '/var/log/plesk/install/plesk_18.0.54_repair_problems.log' for details.
If you can't resolve the issue on your own, please address Plesk support.
SUCCESS: Upgrade step Plesk\Upgrade\Action_UpgradeExtensions was successfully done.
done

**** Product repair completed successfully.

STOP Bootstrapper 18.0.54 repair AT Thu Aug  3 23:52:00 CEST 2023


Regards,
Dennis Bitsch
 
Unable to retrieve repository configuration from autoinstaller: autoinstaller is busy
--> Please wait a few minutes, then try again.

Reconfiguring mail subsystem...
/usr/lib/plesk-9.0/mailsrv_entities_dump isn't yet on its place. Deferring mail_restore execution to a later stage
--> Seems to be the same issue. Something is delaying or blocking a previous installation process.

What are the service status of sw-engine and sw-cp-server?
# systemctl status sw-engine
# systemctl status sw-cp-server

What is logged to /var/log/plesk/install/autoinstaller3.log for the installation processes?
 
You were right! A couple minutes after posting my thread, the panel started again.

Thanks! Thread can be closed.
 
Back
Top