• 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

Resolved how to verify packages? (The update of Plesk has failed.)

geehaa

Basic Pleskian
i got an email with "The update of Plesk has failed."

i followed the link to the log which ends with:

Code:
Detecting installed product components.
OK
Synchronizing the Debian APT package index files...
Hit:1 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:2 http://autoinstall.plesk.com/ubuntu/PSA_17.5.3 xenial InRelease
Hit:3 http://autoinstall.plesk.com/debian/NODE_0.0.1 all InRelease
Hit:4 http://autoinstall.plesk.com/ubuntu/PMM_0.1.10 xenial InRelease
Hit:5 http://autoinstall.plesk.com/ubuntu/PHP56_17 xenial InRelease
Hit:6 http://autoinstall.plesk.com/ubuntu/PHP70_17 xenial InRelease
Hit:7 http://autoinstall.plesk.com/ubuntu/PHP71_17 xenial InRelease
Get:8 http://autoinstall.plesk.com/ubuntu/NGINX17 xenial InRelease [5642 B]
Hit:11 https://apt.dockerproject.org/repo ubuntu-xenial InRelease
Hit:13 https://repos.sonar.digitalocean.com/apt main InRelease
Hit:9 http://ams2.mirrors.digitalocean.com/ubuntu xenial InRelease
Hit:10 http://ams2.mirrors.digitalocean.com/ubuntu xenial-updates InRelease
Hit:12 http://ams2.mirrors.digitalocean.com/ubuntu xenial-backports InRelease
Get:14 http://autoinstall.plesk.com/ubuntu/NGINX17 xenial/all amd64 Packages [838 B]
Fetched 6480 B in 3s (1862 B/s)
Reading package lists...
Retrieving information about the installed license key...
Launching component and product checkers...
Downloading file PSA_17.5.3/examiners/disk_space_check.sh: 0%
Downloading file PSA_17.5.3/examiners/disk_space_check.sh: 100% was finished.
Downloading file PSA_17.5.3/examiners/panel_preupgrade_checker.php: 0%
Downloading file PSA_17.5.3/examiners/panel_preupgrade_checker.php: 100% was finished.
Downloading file PSA_17.5.3/examiners/php_launcher.sh: 0%
Downloading file PSA_17.5.3/examiners/php_launcher.sh: 100% was finished.
Checking whether the package dependencies are resolved.
Installing packages
is running
Stopping sw_engine service... done
===> Cumulative APS controller database (apsc) upgrade has been started.
===> Cumulative upgrade of APS controller database has been completed.
===> Cumulative Plesk database upgrade (revertable stage) has been started.
===> Preparing Plesk database upgrade (revertable stage).
===> Cumulative upgrade of Plesk database (revertable stage) has been completed.
===> Plesk database scheme upgrade has been started.
Applying migrations from: /opt/psa/bootstrapper/pp17.5.3-bootstrapper/migrations/
===> Plesk database scheme upgrade has been completed.
E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
Plesk is down, performing full restart.
Starting sw_engine service... done
Starting sw_cp_server service... already started
Starting mysql service... already started
Starting named service... already started
Starting mailer service... already started
Starting spamfilter service... not installed
Starting tomcat service... not installed
Starting apache service... already started
Starting xinetd service... already started

ERROR: An error occurred on attempt to install packages.
Attention! Your software might be inoperable.
Please contact product technical support.

system seems functional but how do i know for sure?

how can i check if there are packages half installed?

im afraid of restarting because that would mean that processes that still are running with old package version will try to start with maybe incompleted code bases?


i already ran debsums but i would like to know if there is a spcific plesk command which does a complete integrity verification of all packages to see if everything is still ok.

thank you
 
This error

E: Could not get lock /var/lib/dpkg/lock - open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?

occurs if another dpkg process is running during update.

To solve this problem perform following steps:
  1. Complete dpkg task OR cancel/kill it if it is hanged

  2. Delete the file /var/lib/dpkg/lock

  3. Run the following command to reinstall Plesk updates:

    # plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
 
thanks!

if that command gives no errors, can i then be 100% sure everything is in order and safely reboot?
 
if that command gives no errors, can i then be 100% sure everything is in order and safely reboot?
I can say only that if last command will be completed successfully - that means that all latest updates were installed correctly for your Plesk.
After that you can perform upgrade your Plesk to next version, reboot server and whatever you want :)
 
i wasnt upgrading, i t was just a regular auto-update i think. judging from the system email:
---
subject: Plesk update failed

Attention,

The update of Plesk has failed.

You can download Plesk Installer logs at the following link: ....
Contact your Hosting Provider for support assistance.

This message was sent automatically by Plesk Installer.
---
 
So, please follow my suggestions above and let me know if last command

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components

will not completed successfully.
 
i guess this is good:


...
Patching file (275 of 278) /usr/local/psa/admin/plib/Service/Agent/Transport/Local/Exec.php
Patching file (276 of 278) /usr/local/psa/admin/plib/Service/Agent/Transport/Util.php
Patching file (277 of 278) /usr/local/psa/admin/plib/Service/Odbc/Dsn/Manager.php
Patching file (278 of 278) /usr/local/psa/admin/plib/class.ODBC.php


All patches were applied.
Patches were installed successfully.
The changes were applied successfully.
 
Back
Top