• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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