Upgrade fails with polkitd error

Quote from Elektritter

hope this helps somebody

Oh yes, it did! Thanks buddy, you saved my life.

I really had the nerv to upgrade my main OMV NAS in location A, remotely from lcation B (in a different country), of course whiteout reading anything about this before doing it. Don't ask me why . Ok, Ok, both are running on a PI and I have cloned SD cards as backup, where someone could just replace it.

Thanks!!!!

Quote from Elektritter

Hi,

today I upgraded my omv6 to omv7.

It went the firt moment as expected but after a while I got

Setting up polkitd (122-3) ...

Failed to check if group polkitd already exists: Connection refused

id: ‘polkitd’: no such user

chown: invalid user: ‘polkitd:root’

dpkg: error processing package polkitd (--configure):

when you see this error: DON'T REBOOT

I have no idea while installation of polkitd doesn't create the user (may be because the usual user-id was already used), before moving on you can simply create the user:

addgroup --gid 901 polkitd

adduser --uid 901 --ingroup polkitd polkitd --no-create-home --shell /sbin/nologin --home /nonexistent --disabled-password

(of course take uid/gid not used on your system but should less than 1000)

then run

omv-upgrade

omv-salt stage run deploy

and everything should be fine and you can reboot safely hope this helps somebody

Display More

Thank you helped me too!

Hi,

I did the upgrade from 6 to 7 too and I had the same issue with this polkitd error. I tried first the way from elektritter and create the missing group and user but after that I got the error "failed to start systemd-networkd-wait-online.service". I would like to uninstall polkitd now. What is the best way to do this especially to uninstall all dependencies too? I found this command but I'm careful with using commands which I don't understand:

sudo apt-get -y autoremove --purge polkitd

I used your command "sudo apt-get purge polkitd" but I couldn't fix my issue "failed to start systemd-networkd-wait-online.service". Maybe polkitd is not the problem or should I answer yes after the command?

Here is the output from the command above:

Reading package lists... Done

Building dependency tree... Done

Reading state information... Done

The following packages were automatically installed and are no longer required:

libduktape207 libpolkit-agent-1-0 libpolkit-gobject-1-0 xml-core

Use 'apt autoremove' to remove them.

The following packages will be removed:

pkexec* policykit-1* polkitd*

0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.

And this is the output from "systemctl status systemd-networkd-wait-online.service":

systemd-networkd-wait-online.service -Wait for Network to be configured

Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; present: disabled)

Active: failed (Result: exit-code) since Sun 2024-07-21 21:25:21 CEST; 28s ago

Docs: man:systemd-networkd-wait-online.service(8)

Process: 255 ExecStart=/lib/systemd/systemd-networkd-wait-online.service (code=excited, status=1/FAILURE)

Main PID: 255 (code=excited, status=1/FAILURE)

CPU: 56ms

After run "systemctl restart systemd-networkd-wait-online.service":

polkit-agent-helper-1: pam_authenticate failed: Authentication failure

This is the reason why I think that polkit is the problem

I know that it is hard to help me with this few informations but I don't know what kind of output I should send you. Maybe I should step back to the beginning of the problem:

I did the upgrade from omv6 to omv7 and used this guide RE: Is there a guide to in place upgrade?. After that I got the error polkitd error as it is mentioned above. After group and user creation like elektritter said I reboot the server. Now I couldn't find the server in my network (no ping answer). During boot I see now that there is the error "failed to start systemd-networkd-wait-online.service" and the hint to get more information with "systemctl status systemd-networkd-wait-online.service". The output of that is here:

systemd-networkd-wait-online.service -Wait for Network to be configured

Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; present: disabled)

Active: failed (Result: exit-code) since Sun 2024-07-21 21:25:21 CEST; 28s ago

Docs: man:systemd-networkd-wait-online.service(8)

Process: 255 ExecStart=/lib/systemd/systemd-networkd-wait-online.service (code=excited, status=1/FAILURE)

Main PID: 255 (code=excited, status=1/FAILURE)

CPU: 56ms

Now I removed polkitd by "sudo apt-get purge polkitd" but it doesnt't fix the problem. The output of "systemctl status systemd-networkd-wait-online.service" is very similar:

systemd-networkd-wait-online.service -Wait for Network to be configured

Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; preset: disabled)

Active: failed (Result: exit-code) since Sun 2024-07-22 26:25:41 CEST; 15s ago

Docs: man:systemd-networkd-wait-online.service(8)

Process: 252 ExecStart=/lib/systemd/systemd-networkd-wait-online.service (code=excited, status=1/FAILURE)

Main PID: 252 (code=excited, status=1/FAILURE)

CPU: 55ms

By the way, I use a raspberry pi 4.

Now I removed the dependencies, too and I delete also user and group polkitd which I created before. The error is still the same. I attached two photos of my screen. I hope this helps a bit more.

This is the status after boot:

and after command "systemctl status systemd-networkd-wait-online.service":

Please, see this post (read the whole thread if you like, it's only 3 pages) on issues with the wait-network.service.

Post

RE: Clean Install of OMV7 Hangs - Multiple attempts

[…]

Wasn't aware of this script.

I have a mixed of end0 and eth0 refs on the upgraded CM4, and also on the fresh Pi5 with OMV7
Haven't felt any issues with it. All services run as they should but if it can be "fixed/cleared", it would feel more "clean".

Any catches by trying this remotely?
Other than the reboot, of course.

I'm still one week away of going home so, not much willing to loose connection to the server.

Heck, I'll go for the Pi5 and see what happens. This one is just for experiments and…

Soma

Feb 3rd 2024

Check how the NIC is named on omv-firstaid and on the OMV GUI.

If you have it named different on both places, the trick is to delete it on the GUI but creating a new one with the same name that it's shown on omv-firstaid BEFORE applying the changes.

Post

RE: Clean Install of OMV7 Hangs - Multiple attempts

After Script:
Everything the same,

First, ssh to the Pi5.
Went on GUI and created a "new" ethernet, while still having the end0.
Pointed to the eth0 and configured the same way has the end0.

Before applying the yellow banner, deleted the end0.
Applied settings and reboot.

Now, only eth0 is seen on the system.

On GUI, my SMART widget stopped showing any info.
Realized that the monitoring of the disks was disabled by some reason, go figure

Soma

Feb 3rd 2024

I could find a solution for my problem now. I used the omvfirstaid tool and configured the network interface again, After that the error was gone and I could connect to omv gui again. Thank you for your support and I hope that my way could help someone.