• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Inconsistencies were detected in the system's package manager database

Mato

New Pleskian
Server operating system version
Almalinux 8.9
Plesk version and microupdate number
Plesk Obsidian 18.0.59 Update #2
Hi,
this error message has already been answered many times for Debian, but my system is Almalinux 8.9 .
So I can't just type dpkg --audit and find out... And I failed to find such a clean command with dnf.

There are 53 system packages to upgrade, but they are the most important : grub, MariaDB, glibc... So I am not sure about the right method.

What should I do with these updates ?
Could someone point me to a log file where I could find the inconsistency reported by Plesk ?

Best regards,
-Mato
 
Hi, it says :
Problem: problem with installed package mariadb-gssapi-server-3:10.3.39-1.module_el8.8.0+3609+204d4ab0.x86_64
- nothing provides mariadb-server(x86-64) = 3:10.3.39-1.module_el8.8.0+3609+204d4ab0 needed by mariadb-gssapi-server-3:10.3.39-1.module_el8.8.0+3609+204d4ab0.x86_64 from @System
There is no mention of the other 52 packages.
I remember using the new tool earlier this year to upgrade the MariaDB server from v10.3 to v10.5.
It went without any issue. Could this be related anyhow?
 
Hi, I still have the problem presented above.
As already said, I upgraded to MariaDB 10.5 without problem, but it seems that one of the previous 10.3 package is still here and stops any update because it has unmet depdendancies.
Is the package mariadb-gssapi-server.x86_64, which seems to have no 10.5 version.
Is it safe to remove it ?
 
I removed the offending packet (which only exists for Active Directoy/Kerberos authentication) and all upgrades went smoothly.
Conclusion : the MariaDB script should remove the mariadb-gssapi-server.x86_64 packet automatically when upgrading from 10.3 to 10.5.
 
Back
Top