Arch Linux

wolfdogg

Member

From: Portland, OR, USA

Registered: 2011-05-21

Posts: 545

upgrading systemd Error getting authority

Hmm, upgrading today  got me this

pacman -Syu bind
..
..
..
(12/41) upgrading systemd  
upgrading systemd Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)

does this mean an install broke, or what..

---

Node.js, PHP Software Architect and Engineer (Full-Stack/DevOps)
GitHub  | LinkedIn

Sanctanimus

Member

Registered: 2015-01-11

Posts: 31

Re: upgrading systemd Error getting authority

This post seems to be related to your question.
https://bbs.archlinux.org/viewtopic.php?id=153610

wolfdogg

Member

From: Portland, OR, USA

Registered: 2011-05-21

Posts: 545

Re: upgrading systemd Error getting authority

thanks ill look into that to see if i can dig up something :-)

---

Node.js, PHP Software Architect and Engineer (Full-Stack/DevOps)
GitHub  | LinkedIn

davispuh

Member

From: Latvia

Registered: 2014-03-31

Posts: 10

Re: upgrading systemd Error getting authority

I got similar error. Basically some things would work while some would fail with permission and other weird errors. Some procceses would crash.

Here's errors I got:

systemd-networkd[433]: Could not connect to bus: Permission denied
systemd[1]: systemd-networkd.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start Network Service.
systemd[1]: systemd-networkd.service: Unit entered failed state.
systemd[1]: systemd-networkd.service: Failed with result 'exit-code'.
systemd[1]: systemd-networkd.service: Service has no hold-off time, scheduling restart.
systemd[1]: Stopped Network Service.
systemd[1]: Starting Network Name Resolution...
systemd[1]: systemd-networkd.service: Start request repeated too quickly.
systemd[1]: Failed to start Network Service.
systemd[1]: systemd-networkd.socket: Unit entered failed state.
systemd[1]: systemd-networkd.service: Failed with result 'start-limit'.
systemd-resolved[454]: Failed to watch hostname: Permission denied
systemd-resolved[454]: Could not create manager: Permission denied
systemd[1]: systemd-resolved.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start Network Name Resolution.
systemd[1]: systemd-resolved.service: Unit entered failed state.
systemd[1]: systemd-resolved.service: Failed with result 'exit-code'.
systemd[1]: systemd-resolved.service: Service has no hold-off time, scheduling restart.
systemd[1]: Stopped Network Name Resolution.
dbus-daemon[432]: Unable to reload configuration: Failed to open "/etc/dbus-1/system.conf": Permission denied
systemd[1]: Failed to subscribe to NameOwnerChanged signal: Operation not permitted
systemd[1]: Failed to subscribe to activation signal: Operation not permitted
systemd[1]: Failed to register name: Operation not permitted
systemd[1]: Failed to set up API bus: Operation not permitted

Only with root could login and trying to login with any other user would fail

systemd[438]: pam_mail(systemd-user:session): user unknown
login[443]: pam_tally(login:auth): pam_get_uid; no such user
login[443]: pam_unix(login:auth): check pass; user unknown
login[443]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=tty1 ruser= rhost=
login[443]: FAILED LOGIN 1 FROM tty1 FOR exit, Authentication failure

When trying
$ su user
would get
su: failed to execute /bin/bash: Permission denied

some programs would give errors like

GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PolicyKit1 was not provided by any .service files

and trying any systemd comand (couldn't even reboot/shutdown) it would show

Error getting authority: Error initializing authority: Exhausted all available authentication mechanisms (tried: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS) (available: EXTERNAL, DBUS_COOKIE_SHA1, ANONYMOUS)

You might think that my system is really hard fucked up , but actually I just installed it fresh so it was quite puzzling what could be wrong .
After trying a lot of things without success I noticed that I had incorrect permissions on "/"

$ ls -la /
drwxr-x---   1 root root  122 Aug 11 16:50 .

So just had to fix it with

$ chmod 755 /

and that's all, everything is now working perfectly

jancici

Member

From: svk

Registered: 2011-12-04

Posts: 192

Re: upgrading systemd Error getting authority

@davispuh thank you very much
I did install arch on new PC and had same problems as you.
I did spend cca 3 hours trying to find what is the problem, then I did find your comment.

strange thing was that not only permissions of  / was wrong but also owner was changed to username who I did add.