Le 15/08/2019 ? 13:49, Ulf Volmer a ?crit?:> No issues here. libadmsslutil.so.0 comes from 389-adminutil. > Do you have a recently updated system?I'm using yum-cron on all my CentOS servers, so yes. -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Site : https://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 Mob. : 06 51 80 12 12
On 15.08.19 14:31, Nicolas Kovacs wrote:> Le 15/08/2019 ? 13:49, Ulf Volmer a ?crit?: >> No issues here. libadmsslutil.so.0 comes from 389-adminutil. >> Do you have a recently updated system? > > I'm using yum-cron on all my CentOS servers, so yes.Could you post the output of yum info 389-adminutil Best regards Ulf
Le 15/08/2019 ? 14:51, Ulf Volmer a ?crit?:> Could you post the output of > > yum info 389-adminutilI just installed a vanilla CentOS 7.6 on a sandbox machine. Left configuration as is. Upgraded system : yum update. Configured EPEL without customizing anything. And all the 389-related packages installed successfully. So I guess the problem comes from my base configuration. Here's what I usually modify: 1. Activate the Yum CR Community Repository. 2. Install Yum Priorities Plugin. 3. Configure official and CR repository with a priority of 1. 4. Configure EPEL repository with a priority of 10. My suspicion is that some stuff from CR broke dependencies. I have to investigate this further. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Site : https://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 Mob. : 06 51 80 12 12