• We value your experience with Plesk during 2025
    Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025.
    Please take this short survey:

    https://survey.webpros.com/
  • On Plesk for Linux mod_status is disabled on upgrades to improve Apache security.
    This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.

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