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

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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 Error with Plesk & Aptitude

Servus

Basic Pleskian
Hi everyone,
I always use aptitude for updates & upgrades over CLi on Ubuntu18.04.2 with Plesk Onyx 17.8.11.
Today I opened aptitude console directly since weeks.
So I saw a package libcurl3 and wondered about the status p before the package name [screenshot].
For the reason that I'm not so much familiar with the console itself I updated the cache and klicked the "+".
Then I stopped and left the console and tried to install over CLI.
Couldn't believe that it showed me that ALL PLESK PACKAGES WILL BE REMOVED BY INSTALLATION OF LIBCURL3
I didn't install libcurl3 and by normal CLI actions like "aptitude update" the following errors are displayed:
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
[2 code box in detail]
E: Couldn't rebuild package cache
Don't know what to do now. In aptitude console p and i are shown now.
Think there is a process running or the install was half made.
Please, could you help me solve this. How can I remove the libcurl3 package without destroying plesk or Ubuntu.

Code:
root@server:~# apt install libcurl3
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
  curl libapache2-mod-passenger-plesk libcurl4 libpam-plesk libxmlrpc-core-c3 passenger passenger-dev php-curl php7.2-curl
  plesk-base plesk-completion plesk-config-troubleshooter plesk-core plesk-dovecot plesk-dovecot-imap-driver
  plesk-dovecot-pigeonhole plesk-engine plesk-ext-catalog plesk-ext-rest-api plesk-git-http plesk-l10n
  plesk-mail-pc-driver plesk-management-node plesk-php72 plesk-php72-bcmath plesk-php72-cli plesk-php72-dba
  plesk-php72-enchant plesk-php72-fpm plesk-php72-gd plesk-php72-imagick plesk-php72-imap plesk-php72-intl
  plesk-php72-ioncube-loader plesk-php72-ldap plesk-php72-mbstring plesk-php72-mysql plesk-php72-odbc plesk-php72-opcache
  plesk-php72-pdo plesk-php72-pear plesk-php72-pgsql plesk-php72-process plesk-php72-pspell plesk-php72-redis
  plesk-php72-snmp plesk-php72-soap plesk-php72-sodium plesk-php72-tidy plesk-php72-xdebug plesk-php72-xml
  plesk-php72-xmlrpc plesk-php73 plesk-php73-bcmath plesk-php73-cli plesk-php73-dba plesk-php73-enchant plesk-php73-fpm
  plesk-php73-gd plesk-php73-imagick plesk-php73-imap plesk-php73-intl plesk-php73-ioncube-loader plesk-php73-ldap
  plesk-php73-mbstring plesk-php73-mysql plesk-php73-odbc plesk-php73-opcache plesk-php73-pdo plesk-php73-pear
  plesk-php73-pgsql plesk-php73-process plesk-php73-pspell plesk-php73-redis plesk-php73-snmp plesk-php73-soap
  plesk-php73-sodium plesk-php73-tidy plesk-php73-xdebug plesk-php73-xml plesk-php73-xmlrpc plesk-repair-kit plesk-resctrl
  plesk-roundcube plesk-service-node-utilities plesk-web-hosting plesk-wp-upgrade pollinate pp17.8.11-bootstrapper
  psa-drweb-configurator psa-firewall psa-health-monitor psa-horde psa-imp psa-ingo psa-kronolith psa-libxml-proxy
  psa-locale-base-en-us psa-logrotate psa-mail-driver-common psa-mnemo psa-passwd psa-php-configurator psa-phpmyadmin
  psa-proftpd psa-pylibplesk psa-spamassassin psa-turba psa-updates psa-vhost sw-collectd sw-engine sw-engine-cli-2.24
  ubuntu-server
The following NEW packages will be installed:
  libcurl3
0 upgraded, 1 newly installed, 114 to remove and 0 not upgraded.
Need to get 214 kB of archives.
After this operation, 702 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
root@server:~#

1.jpg

Code:
root@server:~# aptitude clean
root@server:~# aptitude update
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
W: Could not lock the cache file; this usually means that dpkg or another apt tool is already installing packages.  Opening in read-only mode; any changes you make to the states of packages will NOT be preserved!
Hit http://autoinstall.plesk.com/ubuntu/PMM_0.1.10 bionic InRelease
Hit http://autoinstall.plesk.com/ubuntu/PSA_17.8.11 bionic InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP72_17 bionic InRelease
Hit http://autoinstall.plesk.com/ubuntu/PHP73_17 bionic InRelease
Ign https://artifacts.elastic.co/packages/6.x/apt stable InRelease
Hit https://artifacts.elastic.co/packages/6.x/apt stable Release
Hit http://mirror.host.ag/mariadb/repo/10.2/ubuntu bionic InRelease
Hit http://mirror.eu.oneandone.net/ubuntu/ubuntu bionic InRelease
Hit http://mirror.eu.oneandone.net/ubuntu/ubuntu bionic-updates InRelease
Hit http://mirror.eu.oneandone.net/ubuntu/ubuntu bionic-backports InRelease
Get: 1 http://mirror.eu.oneandone.net/ubuntu/ubuntu bionic-security InRelease [88.7 kB]
Fetched 88.7 kB in 4s (21.5 kB/s)

Current status: 0 (-91961) new.
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?
E: Couldn't rebuild package cache
 
I came further. However the problem with lock is away. I finally checked the process with and there was no error any longer. Also aptitude update/upgrade are running normal without errors and notices.
Running
Code:
dpkg --configure -a
without results. Seems okay.
Finally running:
Code:
root@server:~# dpkg -s libcurl3
dpkg-query: package 'libcurl3' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
root@server:~#
It's greet to get the message that libcurl3 is NOT installed ! ! !
Also okay from my point of view.
BUT WHY DOES APTITUDE SHOWING p and i (for installed) in APTITUDE CONSOLE ???
(Watch screenshot in the thread above)
Would be great if someone could me tell what to do with this package. Perhaps to remove it?
Greets
 
It seems that this is related to your other case where wrong installer information was shown. So probably this case here is solved by now as you wrote that you reinstalled the server?
 
Yea...most of my 8 sites are running again. Worked the whole night and today. Redis <3 and more....
You are absolutely right @Peter Debik. It's related to my stupid action in aptitude. Sooo unnecessary, so pretty dumb, there was no need to do anything with libcurl3.
It's two years ago that I made such a brainless action. Libcurl3 (I think) was half installed. Web installer cache was destroyed. Glad, that I was able to make up-to-date backups of server, so it was quite easy to bring him back in a healthy state.
Thanks for help. :) Berlin sucks... ;) Hugs.
 
Back
Top