Policykit not starting after update...

[intrax]

After returning from sleep my VM's were unresponsive so I decided to reboot.

Suddenly policykit is not starting anymore:

error:

polkitd[2100]: Lost the name org.freedesktop.PolicyKit1 - exiting

I ran ; apt update && apt upgrade no difference

kernel: 6.8.12-2-pve

Looks like dbus is not providing the org.freedesktop.PolicyKit1 named connection....

I've tried to search for a solution, but cannot find anything.

What can be wrong here ?

 

[fiona]

Hi,

Suddenly policykit is not starting anymore:

error:

polkitd[2100]: Lost the name org.freedesktop.PolicyKit1 - exiting

Anything interesting in the parts of the full journal around this message? What does journalctl -b -u polkit.service say?

I ran ; apt update && apt upgrade no difference

Please always use dist-upgrade or full-upgrade: https://lore.proxmox.com/pve-devel/20240909102050.40220-1-f.ebner@proxmox.com/

kernel: 6.8.12-2-pve

Looks like dbus is not providing the org.freedesktop.PolicyKit1 named connection....

I've tried to search for a solution, but cannot find anything.

What can be wrong here ?

Note that polkitd is not installed by default and not managed by Proxmox VE, so you might want to look at Debian's bug tracker/etc. too.

 

[intrax]

Hi,

Anything interesting in the parts of the full journal around this message? What does journalctl -b -u polkit.service say?


Please always use dist-upgrade or full-upgrade: https://lore.proxmox.com/pve-devel/20240909102050.40220-1-f.ebner@proxmox.com/


Note that polkitd is not installed by default and not managed by Proxmox VE, so you might want to look at Debian's bug tracker/etc. too.

Hi Fiona,

It makes me happy to see someone from the team took the time to reply to my post!

journalctl -b -u
Finished loading, compiling and executing 8 rules
Lost the name org.freedesktop.PolicyKit1 - exiting

dist-upgrade or full-upgrade didn't make any difference.

Will investigate further also through debian's bugtracker.

What I find strange is that after returning from sleep mode, which happened many times before, all my vm's were frozen and couldn't be restarted. I rebooted (no update/upgrade) and than polkit and networkmanager failed to start.
Only than I decided to update.

I've installed proxmox ontop of a regular debian bookworm install with kde and it has been running without any issues for over 6 months with multiple VM's and LXC's

I could revert to a snapshot or a backup, but I'm curious as to what happened here.

It looks like there is something wrong with DBus as the org.freedesktop.PolicyKit1 is shown as activatable in BUSCTL, but apparently fails to do so. Any DBus changes in proxmox ?

Bye

 

[fiona]

journalctl -b -u
Finished loading, compiling and executing 8 rules
Lost the name org.freedesktop.PolicyKit1 - exiting

dist-upgrade or full-upgrade didn't make any difference.

Will investigate further also through debian's bugtracker.

What I find strange is that after returning from sleep mode, which happened many times before, all my vm's were frozen and couldn't be restarted. I rebooted (no update/upgrade) and than polkit and networkmanager failed to start.
Only than I decided to update.

You could test further and see if the issue happens only after sleep mode, so it could be related to that. Note that Proxmox VE is intended for servers. Note that using networkmanager is not advisable, because Proxmox VE uses ifupdown2 currently: https://forum.proxmox.com/threads/i...ompletely-broke-networking.134973/post-627182

It looks like there is something wrong with DBus as the org.freedesktop.PolicyKit1 is shown as activatable in BUSCTL, but apparently fails to do so. Any DBus changes in proxmox ?

The Proxmox VE stack uses DBus for certain things, one is when starting VMs to create a systemd scope. So it might be that DBus itself got issues. The dbus package is also provided by Debian.

 

[fiona]

journalctl -b -u
Finished loading, compiling and executing 8 rules
Lost the name org.freedesktop.PolicyKit1 - exiting

Is this output somehow filtered? It's missing timestamps and process names/IDs for example. Also, the command is incomplete as shown.

The full system journal from the current boot might be interesting journalctl -b > /tmp/journal.txt

 

[intrax]

Is this output somehow filtered? It's missing timestamps and process names/IDs for example. Also, the command is incomplete as shown.

The full system journal from the current boot might be interesting journalctl -b > /tmp/journal.txt

Thanks your reply!

found foll and will investigate further, seems to be a known problem:

qq

Proxmox Policykit Error After Update​

After updating Proxmox VE, some users have reported issues with PolicyKit (polkit) not starting or functioning correctly, resulting in errors when attempting to install updates or access certain features. The error messages often include:

• “Lost the name org.freedesktop.PolicyKit1 - exiting” or similar
• “pkexec must be setuid root”
• “polkitd[2100]: Lost the name org.freedesktop.PolicyKit1 - exiting”

Possible Causes​

1. Inconsistent package state: The update process might have left some packages in an inconsistent state, causing PolicyKit to malfunction.
2. Missing or corrupted dependencies: Dependencies required by PolicyKit might be missing or corrupted, preventing it from functioning correctly.
3. Conflicting configurations: Changes to system configurations or package installations might have caused conflicts with PolicyKit’s settings.

Troubleshooting Steps​

1. Run apt --fix-broken install: This command will attempt to repair any broken package dependencies.
2. Reinstall PolicyKit: Try reinstalling PolicyKit using apt install policykit-1 or apt install polkit.
3. Check system logs: Review system logs (e.g., /var/log/syslog) for any errors or warnings related to PolicyKit or package installations.
4. Verify package sources: Ensure that your package sources are up-to-date and correct. You can do this by running apt update and checking the output for any errors.
5. Try a manual update: Instead of using the graphical update tool, try running apt full-upgrade or apt dist-upgrade from the command line to update your system.

Workarounds​

1. Create a “polkit:root” user: As a temporary workaround, some users have reported success by creating a “polkit:root” user before or during the update process and then removing it afterwards.
2. Use sudo instead of pkexec: If you’re experiencing issues with pkexec, try using sudo instead to perform tasks that require elevated privileges.

Additional Tips​

1. Monitor Proxmox VE forums and documentation: Keep an eye on the Proxmox VE community forums and documentation for any known issues or updates related to PolicyKit errors.
2. Consider seeking support: If you’re unable to resolve the issue using the above steps, consider reaching out to Proxmox VE support or a qualified system administrator for further assistance.

unqq

Bye