• 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 Ubuntu: Plesk Obsidian 18.0.47 after Update 5: inconsistencies were detected in the system's package manager database

ArmReu

New Pleskian
Server operating system version
Ubuntu 20.04.5 LTS
Plesk version and microupdate number
Plesk Obsidian 18.0.47 Web Pro Edition Update 5
Hi everyone!

I am running Plesk Obsidian 18.0.47 Web Pro Edition on Ubuntu 20.04.5 LTS for about a year now without any problems/issues at all.

Since the (automatic) Plesk Update 5 about a week ago I keep getting messages in the system updates panel within Plesk:

Warning: Information on some packages might not be actual: inconsistencies were detected in the system's package manager database. Please resolve this issue manually.

After a little bit of research in here I ran this command to find out more: dpkg --audit

The output says:

Die folgenden Pakete sind nur halb konfiguriert, wahrscheinlich durch
Probleme während der ersten Konfiguration. Die Konfiguration sollte mit
dpkg --configure <Paket> oder mit dem Konfigurations-Menüeintrag in
dselect erneut versucht werden:

grub-efi-amd64-signed GRand Unified Bootloader, version 2 (EFI-AMD64 version,

Translated via deepl:
The following packages are only half configured, probably due to
problems during the initial configuration. The configuration should be done with
dpkg --configure <package> or with the configuration menu entry in
dselect should be tried again:

grub-efi-amd64-signed GRand Unified Bootloader, version 2 (EFI-AMD64 version,

All system updates are set to automatic with safe updates enabled and no customs changes to update sources or such. I know sometimes updates deliver outdated repos and such and it's usually fixed by the next update. But as it is bootloader related this somehow scares me a little.

Has anyone else experienced this issue? Is it already know by the plesk support? Any fix available?

Kindest regards from Germany!

Armin
 
I forget to add the info coming after the update process:

Grund: 2022-10-31 09:45:34 INFO: pum is called with arguments: ['--update', '--json']
2022-10-31 09:45:35 INFO: no packages to update
2022-10-31 09:45:37 ERROR: installArchives() failed
2022-10-31 09:45:37 ERROR: Exited with returncode 1.
 
Plesk does not interfere with such very basic operating system settings. However, when a "general" update of packages is done, the package manager checks for issues with other packages as well. That behavior is built into package management. Grub is so specific to the individual system that I doubt it will be possible to give you the correct advice what steps you will need to take to resolve this.
 
Back
Top