[Bug 1140121] New: Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found
http://bugzilla.opensuse.org/show_bug.cgi?id=1140121 Bug ID: 1140121 Summary: Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: opensuse@mike.franken.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Starting a few weeks (at least 4) agao, I get the message "Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found" in my journal. It seems to stem from NetworkManager start, but I'm not really sure. Starting the service systemd-resolved.service stops this message, but gives lots of other errors including a partial break of connecivity. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140121 http://bugzilla.opensuse.org/show_bug.cgi?id=1140121#c1 Michael Pujos <pujos.michael@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pujos.michael@gmail.com --- Comment #1 from Michael Pujos <pujos.michael@gmail.com> --- I'm also seeing this. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140121 http://bugzilla.opensuse.org/show_bug.cgi?id=1140121#c4 --- Comment #4 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Franck Bui from comment #2)
It sounds like NetworkManager is trying to contact systemd-resolved even if it's not enabled on your system.
Does enabling systemd-resolved [1] fixes your isssue ?
[1] systemctl enabled systemd-resolved
As I wrote in the original report: "Starting the service systemd-resolved.service stops this message, but gives lots of other errors including a partial break of connecivity." -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140121 http://bugzilla.opensuse.org/show_bug.cgi?id=1140121#c5 Adam Mizerski <adam@mizerski.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adam@mizerski.pl --- Comment #5 from Adam Mizerski <adam@mizerski.pl> --- Activating systemd-resolved might collide with nscd, which is used by openSUSE by default. Another option is to tell NetworkManager not to use systemd-resolved: https://wiki.archlinux.org/index.php/NetworkManager#Unit_dbus-org.freedeskto... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140121 http://bugzilla.opensuse.org/show_bug.cgi?id=1140121#c6 --- Comment #6 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Adam Mizerski from comment #5)
Activating systemd-resolved might collide with nscd, which is used by openSUSE by default.
Another option is to tell NetworkManager not to use systemd-resolved: https://wiki.archlinux.org/index.php/NetworkManager#Unit_dbus-org. freedesktop.resolve1.service_not_found
Sounds promising - I'm going to try this one. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140121 http://bugzilla.opensuse.org/show_bug.cgi?id=1140121#c7 --- Comment #7 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Michael Hirmke from comment #6)
(In reply to Adam Mizerski from comment #5)
Activating systemd-resolved might collide with nscd, which is used by openSUSE by default.
Another option is to tell NetworkManager not to use systemd-resolved: https://wiki.archlinux.org/index.php/NetworkManager#Unit_dbus-org. freedesktop.resolve1.service_not_found
Sounds promising - I'm going to try this one.
Works like a charme. Wouldn't that be a good idea to add it to some Tumbleweed package? At least until NetworkManager should really use resolved? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140121 http://bugzilla.opensuse.org/show_bug.cgi?id=1140121#c8 Suse User <forumino@riseup.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |forumino@riseup.net --- Comment #8 from Suse User <forumino@riseup.net> --- I am experiencing the same on a freshly installed 32-bit Tumblweed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140121 Michael K <f4tmike@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |f4tmike@web.de -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140121 http://bugzilla.opensuse.org/show_bug.cgi?id=1140121#c9 Tilman Vogel <tilman.vogel@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tilman.vogel@web.de --- Comment #9 from Tilman Vogel <tilman.vogel@web.de> --- Is this still current? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140121 http://bugzilla.opensuse.org/show_bug.cgi?id=1140121#c10 --- Comment #10 from Michael Hirmke <opensuse@mike.franken.de> --- (In reply to Tilman Vogel from comment #9)
Is this still current?
Since using the mentioned workoraound I didn't have this problem any longer. -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com