Bug 89289

Summary:	emergency mode: Error getting authority ... Could not connect
Product:	systemd	Reporter:	Michael Biebl <mbiebl>
Component:	general	Assignee:	systemd-bugs
Status:	RESOLVED NOTOURBUG	QA Contact:	systemd-bugs
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Michael Biebl 2015-02-23 21:07:30 UTC

Version: 219

When being dropped into emergency mode (e.g. if you have a missing
device from fstab), and you run "systemctl daemon-reload", one gets the
following error message:

Error getting authority: Error initializing authority: Could not
connect: No such file or directory (g-io-error-quark, 1)

The above looks like polkit related connection attempts via dbus and
dbus.service not running in emergency mode.

This is a recent regression. I can't reproduce this issue with v215.

"systemctl daemon-reload" itself seems to work.

Comment 1 rektide 2015-04-10 14:51:00 UTC

Seeing this trying to do a `systemctl disable foo.service` in emergency mode as well. Appreciate the analysis on polkit, mb.

Comment 2 Lennart Poettering 2015-04-10 15:04:19 UTC

This is the policykit tty agent, not systemctl itself.

the tty agent should be fixed to not log any error like this. Please file a bug against PK for this.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.