• 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

Issue mariadb upgrade problem on deb jessie (oldstable)

mow

Silver Pleskian
Hello,

on 17.0.17 on debian oldstable (jessie), the automatic plesk component update of mariadb failed:
[...]
Preparing to unpack .../mariadb-server-10.0_10.0.32-0+deb8u1_amd64.deb ...
17698
There is a MySQL server running, but we failed in our attempts to stop it.
Stop it yourself and try again!
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
17698
There is a MySQL server running, but we failed in our attempts to stop it.
Stop it yourself and try again!
dpkg: error processing archive /var/cache/apt/archives/mariadb-server-10.0_10.0.32-0+deb8u1_amd64.deb (--unpack):
subprocess new pre-removal script returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/mariadb-server-10.0_10.0.32-0+deb8u1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

[...]

Subsequent mails from PUM contain this:
Some problems occurred with the System Updates tool on your server whatever.com. Please resolve them manually.

Reason: 2017-08-23 06:25:52 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']


2017-08-23 06:25:52 ERROR: Previous Plesk installer call finished unsuccessfully. PUM will not perform any update operations until Plesk installation is fixed.


2017-08-23 06:25:52 ERROR: Exited with returncode 50.


Manual apt-get upgrade produced the same result as above.
Additionally, those appeared:
N: Ignoring file 'plesk.list.ai_back' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
N: Ignoring file 'plesk.list.ai_back' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension


Manual service mysql stop worked, but then:
# apt-get update
[...]
W: Duplicate sources.list entry http://autoinstall.plesk.com/debian/PMM_0.1.10/ jessie/all amd64 Packages (/var/lib/apt/lists/autoinstall.plesk.com_debian_PMM%5f0.1.10_dists_jessie_all_binary-amd64_Packages)
W: You may want to run apt-get update to correct these problems

# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
mariadb-server : Depends: mariadb-server-10.0 (>= 10.0.32-0+deb8u1) but 10.0.30-0+deb8u2 is installed
N: Ignoring file 'plesk.list.ai_back' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
N: Ignoring file 'plesk.list.ai_back' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
E: Unmet dependencies. Try using -f.


So I did
# apt-get install mariadb-server-10.0
as asked, which worked.

However, System Updates now keeps telling me
Error: Unable to get packages list: 2017-08-24 18:11:58 INFO: pum is called with arguments: ['--list', '--repo-info', '--json'] 2017-08-24 18:11:58 ERROR: Previous Plesk installer call finished unsuccessfully. PUM will not perform any update operations until Plesk installation is fixed. 2017-08-24 18:11:58 ERROR: Exited with returncode 50.

How do I get that cleaned up?
And why did it fail in the first place?

On our almost identical test server, jessie without Plesk, the mariadb upgrade installed without trouble:
Setting up mariadb-common (10.0.32-0+deb8u1) ...
(Reading database ... 60797 files and directories currently installed.)
Preparing to unpack .../mariadb-server-10.0_10.0.32-0+deb8u1_amd64.deb ...
4295
There is a MySQL server running, but we failed in our attempts to stop it.
Stop it yourself and try again!
dpkg: warning: subprocess old pre-removal script returned error exit status 1
dpkg: trying script from the new package instead ...
dpkg: ... it looks like that went OK
Unpacking mariadb-server-10.0 (10.0.32-0+deb8u1) over (10.0.30-0+deb8u2) ...

[...]
 
As "edit" throws an error, I'm posting this as followup:
plesk repair installation helped, System Updates shows no error and everything seems up to date.
 
Problem: After plesk repair installation as above, postfix uses an old (expired) certificate, although the correct certificate appears to be selected for securing mail in :8443/admin/ssl-certificate/list.
After going to :8443/admin/ssl-certificate/secure-mail-server and just pressing OK so that selected certificate is reinstalled, it seems to work again with the correct certificate

So, bug in plesk repair installation?
 
Back
Top