Resolved plesk is not compatible with libopendkim update

[Linulex]

on centos 6.8 plesk dependency is libopendkim.so.10

update = libopendkim.so.11
centos 7 is also 2.11, this might have this problem as well

The full error is

[root@kvmtest242 ~]# yum -y update --skip-broken
Loaded plugins: fastestmirror, priorities
Setting up Update Process
Loading mirror speeds from cached hostfile
 * base: mirror.widexs.nl
 * epel: epel.mirror.nucleus.be
 * extras: mirror.sitbv.nl
 * updates: mirror.sitbv.nl
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-driv                                            er-common-17.0.17-cos6.build1700161124.17.x86_64
---> Package libopendkim.x86_64 0:2.11.0-0.1.el6 will be an update
epel/filelists_db                                        | 7.8 MB     00:00

Packages skipped because of dependency problems:
    libopendkim-2.11.0-0.1.el6.x86_64 from epel

regards
Jan

 

[Bitpalast]

Confirmed by https://talk.plesk.com/threads/plesk-12-5-30-to-onyx-upgrade-problem.340985/

 

[Barungar]

Same here... I have multiple VPS with Plesk Oynx on CentOS 6.x and 7.x, all of them want to update the libopendkim library from version 2.10.3 to version 2.11.0. The dependency check fails on "psa-mail-driver-common-17.0.17".

 

[josie333]

I have the same error and unsure what steps to take to fix

 

[froggift]

Same issue here! How to fix this?

Abhängigkeiten werden aufgelöst
--> Transaktionsprüfung wird ausgeführt
---> Paket libopendkim.x86_64 0:2.10.3-7.el7 markiert, um aktualisiert zu werden
--> Abhängigkeit libopendkim.so.10()(64bit) wird für Paket psa-mail-driver-common-17.0.17-cos7.build1700161124.17.x86_64 verarbeitet
---> Paket libopendkim.x86_64 0:2.11.0-0.1.el7 markiert, um eine Aktualisierung zu werden
--> Abhängigkeitsauflösung beendet
Fehler: Paket: psa-mail-driver-common-17.0.17-cos7.build1700161124.17.x86_64 (@PLESK_17_0_17-dist)
            Benötigt: libopendkim.so.10()(64bit)
            Entfernen: libopendkim-2.10.3-7.el7.x86_64 (@epel)
                libopendkim.so.10()(64bit)
            Aktualisiert durch: libopendkim-2.11.0-0.1.el7.x86_64 (epel)
               ~libopendkim.so.11()(64bit)
 Sie können versuchen, mit --skip-broken das Problem zu umgehen.
 Sie könnten Folgendes versuchen: rpm -Va --nofiles --nodigest

 

[IgorG]

I confirm this bug PPPM-5517. Fix is expected in MU#13

 

[petrogazz]

In case some else encounters the same problem, I got it resolved following these 2 steps:

1. Remove epel repo
2. yum remove libopendkim.x86_64

 

[tech01]

I have no any exact ETA, but you can use this workaround now - https://support.plesk.com/hc/en-us/articles/115000514285 -IgorG, Tuesday at 2:54 AM

-From Thread: https://talk.plesk.com/threads/plesk-12-5-30-to-onyx-upgrade-problem.340985/

 

[Linulex]

removing epel repositry can lead to an unsecure installation because non of the by epel installed rpm's will get updates anymore. It if far better to only exclude
libopendkim. Do this by adding

exclude=libopendkim*

to the [epel] section of

/etc/yum.repos.d/epel.repo

regards
Jan

 

[froggift]

Hi it's not yet fixed in

Plesk Onyx
Version 17.0.17 Update #12

is there an ETA for a fix (not a workaround).

 

[IgorG]

is there an ETA for a fix

MU#13 expected next week.

 

[decanet]

Hi Igor,

MU#13 is applied on our test server, but I still have the problem:

# plesk version
Product version: Plesk Onyx 17.0.17 Update #13
    Update date: 2017/01/23 09:21
    Build date: 2016/11/17 16:00
    OS version: CentOS 7
      Revision: ab6766191d3ba26e7b21255ab007fc7fc56d84c6
   Architecture: 64-bit
Wrapper version: 1.2

# yum update
...
Erreur : Paquet : psa-mail-driver-common-17.0.17-cos7.build1700161124.17.x86_64 (@PLESK_17_0_17-dist)
            Requiert : libopendkim.so.10()(64bit)
            Suppression  : libopendkim-2.10.3-7.el7.x86_64 (@epel)
                libopendkim.so.10()(64bit)
            Mis à jour par : libopendkim-2.11.0-0.1.el7.x86_64 (epel)
                ~libopendkim.so.11()(64bit)
 Vous pouvez essayer d'utiliser --skip-broken pour contourner le problème
 Vous pouvez essayer d'exécuter : rpm -Va --nofiles --nodigest

 

[IgorG]

MU#13 is applied on our test server, but I still have the problem:

Yes, I confirm the problem was not fixed. I discuss this right now with the developers.

 

[RobHost]

Any ETA for the next MU #14 with the fix included, finally?

 

[IgorG]

Who can send me in PM login credentials (root ssh access) on affected server? We will check this issue directly on your server.

 

[RobHost]

No problem, please send us your SSH PubKey to support {at} robhost.de

 

[IgorG]

No problem, please send us your SSH PubKey to support {at} robhost.de

https://support.plesk.com/hc/en-us/articles/115000120205

 

[RobHost]

Ok, added - please contact me directly to get the servers IP. Don't want to post it on this public forums. Thanks.

 

[IgorG]

@RobHost , thank you for cooperation. We have gathered necessary information and going to fix this issue in the next MU.

 

[RobHost]

You're welcome! Good news ;-)