• 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 libopendkim / psa-mail-driver-common error MU#13

Willem Janssen

New Pleskian
I keep getting this error (even after updating to #13). How can this be resolved?

Loaded plugins: fastestmirror
Setting up Update Process
Determining fastest mirrors
epel/metalink | 23 kB 00:00
* base: mirror.prolocation.net
* epel: ftp.nluug.nl
* extras: centos.mirror.transip.nl
* updates: centos.mirror.transip.nl
PHP52_17 | 2.9 kB 00:00
PHP52_17/primary_db | 14 kB 00:00
PHP53_17 | 2.9 kB 00:00
PHP53_17/primary_db | 14 kB 00:00
PLESK_17_0_17-extras | 2.9 kB 00:00
PLESK_17_0_17-extras/primary_db | 29 kB 00:00
PLESK_17_PHP54 | 2.9 kB 00:00
PLESK_17_PHP54/primary_db | 14 kB 00:00
PLESK_17_PHP55 | 2.9 kB 00:00
PLESK_17_PHP55/primary_db | 14 kB 00:00
PLESK_17_PHP56 | 2.9 kB 00:00
PLESK_17_PHP56/primary_db | 14 kB 00:00
PLESK_17_PHP70 | 2.9 kB 00:00
PLESK_17_PHP70/primary_db | 14 kB 00:00
PLESK_17_PHP71 | 2.9 kB 00:00
PLESK_17_PHP71/primary_db | 14 kB 00:00
base | 3.7 kB 00:00
base/primary_db | 4.7 MB 00:00
epel | 4.3 kB 00:00
epel/primary_db | 5.9 MB 00:00
extras | 3.4 kB 00:00
extras/primary_db | 37 kB 00:00
plesk-letsencrypt | 2.9 kB 00:00
plesk-letsencrypt/primary_db | 7.0 kB 00:00
plesk-letsencrypt-tp | 2.9 kB 00:00
plesk-letsencrypt-tp/primary_db | 1.2 kB 00:00
updates | 3.4 kB 00:00
updates/primary_db | 4.3 MB 00:00
Resolving Dependencies
--> Running transaction check
---> Package libopendkim.x86_64 0:2.10.3-7.el6 will be updated
--> Processing Dependency: libopendkim.so.10()(64bit) for package: psa-mail-driver-common-17.0.17-cos6.build1700161124.17.x86_64
---> Package libopendkim.x86_64 0:2.11.0-0.1.el6 will be an update
--> Finished Dependency Resolution
Error: Package: psa-mail-driver-common-17.0.17-cos6.build1700161124.17.x86_64 (@PLESK_17_0_17-dist)
Requires: libopendkim.so.10()(64bit)
Removing: libopendkim-2.10.3-7.el6.x86_64 (@epel)
libopendkim.so.10()(64bit)
Updated By: libopendkim-2.11.0-0.1.el6.x86_64 (epel)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
 
Hi Peter,

Update 13 is already installed :)

  • Product: Plesk Onyx 17.0.17 Update #13 , last updated at Jan 23, 2017 09:03 AM
Very persistent error :(
 
O.k., I've updated my test machine to #13 and were able to reproduce the error, too. It seems that currently we can only wait on another MU, using one of the suggested workarounds (disabling the epel repository or excluding the libary from updates temporarily).
 
Yes, I confirm the problem was not fixed. I discuss this right now with the developers.
 
I can confirm a severe issue with downloaded mails. Much worse and much more urgent than the libopendkim issue that was fixed. Now the mail header is broken. Still researching this here.
 
Still problems:

--> Finished Dependency Resolution
Error: Package: psa-mail-driver-common-17.0.17-cos6.build1700161124.17.x86_64 (@PLESK_17_0_17-dist)
Requires: libopendkim.so.10()(64bit)
Removing: libopendkim-2.10.3-7.el6.x86_64 (@epel)
libopendkim.so.10()(64bit)
Updated By: libopendkim-2.11.0-0.1.el6.x86_64 (epel)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
 
Still problems:

--> Finished Dependency Resolution
Error: Package: psa-mail-driver-common-17.0.17-cos6.build1700161124.17.x86_64 (@PLESK_17_0_17-dist)
Requires: libopendkim.so.10()(64bit)
Removing: libopendkim-2.10.3-7.el6.x86_64 (@epel)
libopendkim.so.10()(64bit)
Updated By: libopendkim-2.11.0-0.1.el6.x86_64 (epel)
Not found
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

Try to run

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
 
Thanks Igor, that fixed the mentioned Dependency Resolution.
However, when using the Plesk update Product Components, it keeps displaying that there are updates for: Mail hosting > SMTP servers > Postfix
Even when updating components it displays Success. But it keeps telling that there are updates.
Seems it is not causing any problems, though.
 
Back
Top