• 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 Failed to update the Panel

Piekielko

Basic Pleskian
Przechwytywanie.PNG Server:
  • Plesk Onyx v17.5.3_build1705170317.16 os_Ubuntu 14.04
  • Ubuntu 14.04.5 LTS
---------------------------------
sources.list

###### Ubuntu Main Repos

deb http:// pl.archive.ubuntu.com/ubuntu/ trusty main restricted universe
deb-src http:// pl.archive.ubuntu.com/ubuntu/ trusty main restricted universe

###### Ubuntu Update Repos
deb http:// pl.archive.ubuntu.com/ubuntu/ trusty-security main restricted universe
deb http:// pl.archive.ubuntu.com/ubuntu/ trusty-updates main restricted universe
deb-src http:// pl.archive.ubuntu.com/ubuntu/ trusty-security main restricted universe
deb-src http:// pl.archive.ubuntu.com/ubuntu/ trusty-updates main restricted universe
deb Atomicorp trusty main

---------------------------------------------------------------------------------------------------------------------


I have a problem with updating components:


Installer Pleska 3.22.14 (revision cef153794d9f) started at (timezone CET) Thu Jul 25 06:39:40 2019
Command line arguments: /var/cache/parallels_installer/parallels_installer_Ubuntu_14.04_x86_64_3.22.14 upgrade plesk 17.8.11 --email [email protected]

Try to find rcfile ...
Autoinstaller found rcfile at /root/.autoinstallerrc
Checking hostname is sucessfull.

[...]

Reading package lists ...
Warning: not connected 'multiverse' repository section
repository: Get brief packages info for all sources
Detection of installed product components.
Component plesk / panel: mode upgrade, installed_buildtime = 0, available_buildtime = 0
Checking if the key update required for component plesk / panel
Config allows upgrade from version 17.0 without key update
Currently installed component version is 17.5.3-ubuntu14.04.build1705170317.16
No keyupdate need for this component

[...]

Component plesk/imunifyav: mode up2date, installed_buildtime = 0, available_buildtime = 0
add 'deb http://autoinstall.plesk.com/ubuntu/PSA_17.8.11 trusty all' to temporary source list
add 'deb http://autoinstall.plesk.com/ubuntu/PSA_17.8.11 trusty extras' is persistent source list
add 'deb http://autoinstall.plesk.com/ubuntu/PHP56_17 trusty all' is persistent source list
add 'deb http://autoinstall.plesk.com/PHP_7.2.18 trusty all' is persistent source list
OKAY
Synchronization of the Debian APT port index files ...
E: Could not get lock/var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
E: Unable to lock directory/var/lib/apt/lists /
Warning: there are errors in 'apt-get update'
Searching for information about the installed license key ..
KeyUpdateChecker :: doCheck: no components for check key update
Introduction of product and product correctors ...
Download file PSA_17.8.11/examiners/disk_space_check.sh: 0%
Download file PSA_17.8.11/examiners/disk_space_check.sh: 100% completed.
Download file PSA_17.8.11/examiners/panel_preupgrade_checker.php: 0%
Download file PSA_17.8.11/examiners/panel_preupgrade_checker.php: 100% completed.
Download file PSA_17.8.11/examiners/php_launcher.sh: 0%
Download file PSA_17.8.11/examiners/php_launcher.sh: 100% completed.
skip package 'postfix-2.11.0-1ubuntu1.2.amd64' from component postfix - same or newer version of this package is already installed (in system postfix-2.11.0-1ubuntu1.2.amd64)
skip package 'php5-fpm-5.5.9 + dfsg-1ubuntu4.29.amd64' from component phpgroup - same or newer version of this package is already installed (in php5-fpm-5.5.9 + dfsg-1ubuntu4.29. amd64)
skip package 'apache2-mpm-event-2.4.10-1ubuntu1.1 ~ ubuntu14.04.2.amd64' from component phpgroup - the system is already installed (in apache2-mpm-event-2.4.10- system 1ubuntu1.1 ~ ubuntu14.04.2.amd64)
Checking if package dependencies are resolved.
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?
--- X --- `apt-get` output ---------------------
~ empty
---------------------- `apt-get` output --- X ---
Collecting error details in a log file ...
Sources list:
Installed in system packages:
Error: Installation will not continue

Apg-get failed and sent the following message:

Not all packages have been installed.
Please contact the technical support of the product.


---
Plesk's installer.


------------------------------

Email notify:

Hello, Administrator
This notification message is a digest from System Updates for your server xxxx.com.

The following package updates are available:
- base-files 7.2ubuntu5.6 from Ubuntu for trusty-updates by Ubuntu repo (currently installed version: 7.2ubuntu5.5 from now repo)
- grub-common 2.02~beta2-9ubuntu1.17 from Ubuntu for trusty-updates by Ubuntu repo (currently installed version: 2.02~beta2-9ubuntu1.15 from now repo)
- grub-pc 2.02~beta2-9ubuntu1.17 from Ubuntu for trusty-updates by Ubuntu repo (currently installed version: 2.02~beta2-9ubuntu1.15 from now repo)
- grub-pc-bin 2.02~beta2-9ubuntu1.17 from Ubuntu for trusty-updates by Ubuntu repo (currently installed version: 2.02~beta2-9ubuntu1.15 from now repo)
- grub2-common 2.02~beta2-9ubuntu1.17 from Ubuntu for trusty-updates by Ubuntu repo (currently installed version: 2.02~beta2-9ubuntu1.15 from now repo)
- linux-libc-dev 3.13.0-170.220 from Ubuntu for trusty-security by Ubuntu repo (currently installed version: 3.13.0-153.203 from now repo)

You can update these packages in System Updates: https://xxxx.com:8443/admin/pum

If you don't want to receive these messages, configure notification settings: https://xxxx.com:8443/admin/pum/settings

View attachment 15715 Przechwytywanie1.PNG
 
Last edited:
I did not find anything like that (with ps aux / ps auxx)
Przechwytywanie.PNG

is it enough to delete the lock file?
Przechwytywanie12.PNG
 
Last edited:
Yes you can try that, but before you do check the file date of the lock file. That could give you any hints about when the lock was created.
Also do "fuser /var/lib/dpkg/lock" to see if there's any active process accessing the lock file.

If you're really sure that no process owns the lock file, then you can delete it.
 
lock.PNG
the last update was carried out over a month ago

I used "fuser /var/lib/dpkg/lock" but found nothing.

I changed the entry in sources.list because I noticed that access to the repositories was blocked
# deb http:// mirrors.online.net/ubuntu trusty-updates main restricted

my Ubuntu version (14.04.5 LTS) ceased to be supported in April 2019. Is the system upgrade necessary?
 
Back
Top