Issue [17.5.3] apt-get failed, Plesk (Auto)Update not working

[SigmundS]

Hello there, since a few days, Plesk will not make any updates. I tried to do it manually but I get an error msg giving zero information (see screenshot "failed.jpg").

Expand/Collapse Block: Error Log

Execution failed.
Command: autoinstaller
Arguments: Array
(
[0] => --select-product-id
[1] => plesk
[2] => --select-release-current
[3] => --upgrade-installed-components
)

Details: Doing restart of Plesk Installer...
Downloading file products.inf3: 0%
Downloading file products.inf3: 100% was finished.
Downloading file plesk.inf3: 0%
Downloading file plesk.inf3: 100% was finished.
Downloading file ppsmbe.inf3: 0%
Downloading file ppsmbe.inf3: 100% was finished.
Downloading file sitebuilder.inf3: 0%
Downloading file sitebuilder.inf3: 100% was finished.
Downloading file sso.inf3: 0%
Downloading file sso.inf3: 100% was finished.
.......
Ign ftp://ftp.myserver.net all/all Translation-en_GB
Get:34 ftp://ftp.myserver.net all/all Translation-de
Ign ftp://ftp.myserver.net all/all Translation-de
Fetched 7266 B in 4s (1462 B/s)
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?
Warning: there are errors in 'apt-get update'
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.
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 into the log file...

ERROR: Installation will not continue

The apg-get failed with the following message:

Not all packages were installed.
Please contact product technical support.

There is no process blocking the /dpkg folder. When I seach for it in htop nothing shows up.
On the other side there is a mailman update pending for a few days, but when I click "Install now" I get an error (see screenshot "failed_2.jpg")

Any Ideas?

Thx. 4 F1

st.

ps: this is not the complete log file as I am limited to 10000 caracters.......

 

[trialotto]

@SigmundS

You can safely do the following:

- run the command: ps aux | grep installer
- kill any process that still is associated with open update processes: kill -9 [PID] [PID] ...
- run the command: dpkg --configure -a

and afterwards, you can try to re-run the command: plesk sbin autoinstaller (which is a better and faster alternative to the web-based one).

Just let me know what happens.

Regards........

 

[SigmundS]

@trialotto
Ok, here is what happened:
root@:~# ps aux | grep installer
root 10153 0.0 0.0 15812 904 pts/4 S+ 15:28 0:00 grep --color=auto installer
root@:~# kill -9 10153
-bash: kill: (10153) - No such process
root@:~# dpkg --configure -a
Setting up linux-libc-dev:amd64 (3.13.0-137.186) ...
Setting up mailman (1:2.1.16-2ubuntu0.3) ...

Then nothing happens. I've waited 30min and killed the (mailman) process. This is what locks the dpkg folder. I think that the mailman configuration is waiting for something. Input most likely. How do I force the mailman update process to complete without the knowledge of the needed input?

Thx 4 F1.

st.

 

[trialotto]

@SigmundS

We are getting somewhere with

Then nothing happens. I've waited 30min and killed the (mailman) process. This is what locks the dpkg folder. I think that the mailman configuration is waiting for something. Input most likely. How do I force the mailman update process to complete without the knowledge of the needed input?

since that implies we have a problematic mailman installation.

It is very likely to be the case that a previous installation of mailman went wrong.

Normally, I would strongly recommend to re-install mailman, but that is not an option in this case: (on the one hand) installers are not working and (on the other hand) one will lose all data if mailman is re-installed.

I am pretty sure that your repos are outdated: on an Ubuntu 16.04 LTS machine, you should have package mailman_1%3a2.1.20-1ubuntu0.1_amd64.deb

So, run the commands:

- command: apt-get update
- again, try command: dpkg --configure -a

and just let me know.

By the way, are you on an OVH server by coincidence?

Regards.......

 

[SigmundS]

@trialotto It's Ubuntu 14.04.5. Does that matter?
And what is OVH? Because I don't know I would say no. It's a root server rooted in Frankfurt, germany, with Strato.

This is the output (last 5 rows):
Ign Index of / trusty/all Translation-en_GB.utf8
Ign Index of / trusty/all Translation-de
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
root@h2410219:~# dpkg --configure -a
Setting up mailman (1:2.1.16-2ubuntu0.3) ...

After that, nothing happens.
I've read that mailman is for Mailing Lists. As mailserver I use postfix anyway and I am pretty sure none of my clients uses Mailing Lists. Can I just deactivate it?

 

[trialotto]

@SigmundS

Can I just deactivate it?

Yes, you can. But you need to remove or repair the entire mailman installation, otherwise you would not be able to do system maintenance and upgrades.

First, try to run the command: /etc/init.d/mailman start

Afterwards, run the command: apt-get install --only-upgrade mailman

It can be required to run a dpkg --configure -a in between.

IF the above works, you can then safely remove mailman and the best way is to run the command: plesk sbin autoinstaller (and follow the wizard to remove mailman).

Note that using Plesk's autoinstaller will also automatically remove all other (related) packages, so this method is more easy than using apt-get.

Hope the above helps, just let me know.

Regards.......

 

[SigmundS]

@trialotto
Thank you for your help and patience. I now officially hate mailman!

Expand/Collapse Block: Log

root@myserver:~# htop
root@myserver:~# /etc/init.d/mailman start
* Site list for mailman missing (looking for list named 'mailman').
* Please create it; until then, mailman will refuse to start.
root@myserver:~# dpkg --configure -a
Setting up mailman (1:2.1.16-2ubuntu0.3) ...
dpkg: error processing package mailman (--configure):
subprocess installed post-installation script was killed by signal (Terminated)
Processing triggers for libc-bin (2.19-0ubuntu6.13) ...
Setting up linux-firmware (1.127.24) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-46-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-32-generic
Setting up python-libxml2 (2.9.1+dfsg1-3ubuntu4.11) ...
Errors were encountered while processing:
mailman
root@myserver:~# sudo newlist mailman [email protected] 123
To finish creating your mailing list, you must edit your /etc/aliases (or
equivalent) file by adding the following lines, and possibly running the
`newaliases' program:

## mailman mailing list
mailman: "|/var/lib/mailman/mail/mailman post mailman"
mailman-admin: "|/var/lib/mailman/mail/mailman admin mailman"
mailman-bounces: "|/var/lib/mailman/mail/mailman bounces mailman"
mailman-confirm: "|/var/lib/mailman/mail/mailman confirm mailman"
mailman-join: "|/var/lib/mailman/mail/mailman join mailman"
mailman-leave: "|/var/lib/mailman/mail/mailman leave mailman"
mailman-owner: "|/var/lib/mailman/mail/mailman owner mailman"
mailman-request: "|/var/lib/mailman/mail/mailman request mailman"
mailman-subscribe: "|/var/lib/mailman/mail/mailman subscribe mailman"
mailman-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe mailman"
Hit enter to notify mailman owner...


root@myserver:~# /etc/init.d/mailman start
* Starting Mailman master qrunner mailmanctl [ OK ]
root@myserver:~# apt-get install --only-upgrade mailman
Reading package lists... Done
Building dependency tree
Reading state information... Done
mailman is already the newest version.
The following packages were automatically installed and are no longer required:
gcc-4.8-base:i386 libstdc++6:i386 libxml2:i386 plesk-py27-pip
plesk-py27-setuptools plesk-py27-virtualenv plesk-wheel-cffi
plesk-wheel-cryptography plesk-wheel-psutil
Use 'apt-get autoremove' to remove them.
0 to upgrade, 0 to newly install, 0 to remove and 3 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up mailman (1:2.1.16-2ubuntu0.3) ...

dpkg: error processing package mailman (--configure):
subprocess installed post-installation script was killed by signal (Terminated)
Errors were encountered while processing:
mailman
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@myserver:~# dpkg --configure -a
Setting up mailman (1:2.1.16-2ubuntu0.3) ...


root@h2410219:~# apt-get install --only-upgrade mailman
Reading package lists... Done
Building dependency tree
Reading state information... Done
mailman is already the newest version.
The following packages were automatically installed and are no longer required:
gcc-4.8-base:i386 libstdc++6:i386 libxml2:i386 plesk-py27-pip
plesk-py27-setuptools plesk-py27-virtualenv plesk-wheel-cffi
plesk-wheel-cryptography plesk-wheel-psutil
Use 'apt-get autoremove' to remove them.
0 to upgrade, 0 to newly install, 0 to remove and 3 not to upgrade.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up mailman (1:2.1.16-2ubuntu0.3) ...
dpkg: error processing package mailman (--configure):
subprocess installed post-installation script was killed by signal (Terminated)
Errors were encountered while processing:
mailman

E: Sub-process /usr/bin/dpkg returned an error code (1)
root@h2410219:~# dpkg --configure -a
Setting up mailman (1:2.1.16-2ubuntu0.3) ...
dpkg: error processing package mailman (--configure):
subprocess installed post-installation script was killed by signal (Terminated)
Errors were encountered while processing:
mailman

root@h2410219:~# /etc/init.d/mailman start
* Starting Mailman master qrunner mailmanctl [ OK ]
root@h2410219:~# dpkg --configure -a
Setting up mailman (1:2.1.16-2ubuntu0.3) ...

I tried it the way you wrote it. As you can see from the log I always end up at the part where mailman is configuring itself. But it doesn't end. It is so frustrating. I set up an alias mailing list (found guide here) but it didn't help.
I get mailman to start, but the apt-get install --only-upgrade mailman as well as dpkg --configure -a end in the Setting up mailman part.
I didn't had any idea from the start what to do. I hope you don't run out of ideas as quick as I do .

As you can see in the screenshot, the server is doing something. But over 80% CPU to configure mailman?!?

st.

 

[trialotto]

@SigmundS

Eh, you are right when saying

I now officially hate mailman!

and I fully agree, although for me it is more a matter of security (mailman is notorious in that area).

Note that you do have to kill running processes if they are (unintendly) still active after running a previous command: that could explain the odd CPU usage.

Sure, it is becoming a time-consuming task...... and I want to offer you to have a look at the system directly: it will work faster if I can see what actually happens in real-time.

If you want to make use of that offer, just send me a private message.

Regards........