• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

Issue Problem updating to the new version of Plesk

karyo

New Pleskian
Hello
The following error occurs when updating to the new version in Plesk Installer

Code:
Configuration file '/usr/share/psa-roundcube/config/config.inc.php'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
==> Keeping old config file as default.
Processing triggers for systemd (237-3ubuntu10.45) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for rsyslog (8.32.0-1ubuntu4) ...
Processing triggers for ureadahead (0.100.0-21) ...
Processing triggers for libc-bin (2.27-3ubuntu1.4) ...
Errors were encountered while processing:
amavisd-new
E: Sub-process /usr/bin/dpkg returned an error code (1)
Launching component and product checkers...
Downloading file report-update: 0%
Downloading file report-update: 100% was finished.
Downloading file pool/PSA_18.0.34_5691/examiners/py_launcher.sh: 0%
Downloading file pool/PSA_18.0.34_5691/examiners/py_launcher.sh: 100% was finished.
Error: An error occurred on attempt to install packages.
Attention! Your software might be inoperable.
Visit https://support.plesk.com/ to search for a solution.

Where does the problem come from and how is it solved?
 
The issue is caused by corrupted amavis installation, that prevented the package from being installed/updated properly.
To resolve the issue try to remove amavis completely with:

# dpkg --purge amavisd-new

and then repeat the upgrade procedure.
 
Back
Top