NetworkManager.service failed to start (PolicyKit timeout?)

penguin42 · June 30, 2013, 1:53pm

Hi,
I installed openSUSE 12.3 on my core2 laptop last week, and was having some problems where I had to manually start
Networkmanager, that problem went away, and I’d been using it for a few days, and I updated to Tumbleweed yesterday,
and today I had the same problem with Network Manager not starting.

Today I decided to look at systemctl and it said:

NetworkManager.service loaded failed failed Network Manager

Restarting it worked, so then with journalctl I had a dig and there are multiple timeouts:

Jun 30 12:16:38 davros.home.treblig.org systemd[1]: Started Purge old kernels.
Jun 30 12:16:48 davros.home.treblig.org dbus-daemon[503]: dbus[503]: [system] Activating systemd to hand-off: service name=‘org.freedesktop.UPower’ unit=‘upower.service’
Jun 30 12:16:48 davros.home.treblig.org dbus[503]: [system] Activating systemd to hand-off: service name=‘org.freedesktop.UPower’ unit=‘upower.service’
Jun 30 12:16:51 davros.home.treblig.org dbus-daemon[503]: dbus[503]: [system] Failed to activate service ‘org.freedesktop.PolicyKit1’: timed out
Jun 30 12:16:51 davros.home.treblig.org dbus-daemon[503]: dbus[503]: [system] Failed to activate service ‘org.freedesktop.systemd1’: timed out
Jun 30 12:16:51 davros.home.treblig.org dbus-daemon[503]: process 503: arguments to dbus_message_set_reply_serial() were incorrect, assertion “reply_serial != 0” failed in file dbus-message.c line 1070.
Jun 30 12:16:51 davros.home.treblig.org dbus-daemon[503]: This is normally a bug in some application using the D-Bus library.
Jun 30 12:16:51 davros.home.treblig.org dbus-daemon[503]: D-Bus not built with -rdynamic so unable to print a backtrace
Jun 30 12:16:51 davros.home.treblig.org dbus[503]: [system] Failed to activate service ‘org.freedesktop.PolicyKit1’: timed out
Jun 30 12:16:51 davros.home.treblig.org dbus[503]: [system] Failed to activate service ‘org.freedesktop.systemd1’: timed out
Jun 30 12:16:51 davros.home.treblig.org NetworkManager[508]: <error> [1372591011.690606] [nm-manager-auth.c:87] pk_authority_get(): Failed to initialize PolicyKit: (24) Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached
Jun 30 12:16:51 davros.home.treblig.org avahi-daemon[481]: Disconnected from D-Bus, exiting.
Jun 30 12:16:51 davros.home.treblig.org avahi-daemon[481]: Got SIGTERM, quitting.
Jun 30 12:16:51 davros.home.treblig.org avahi-daemon[481]: avahi-daemon 0.6.31 exiting.
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: dbus.service: main process exited, code=killed, status=6/ABRT
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Unit dbus.service entered failed state
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Failed to start Login Service.
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Unit systemd-logind.service entered failed state
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Stopping Login Service…
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Starting Login Service…
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Starting D-Bus System Message Bus…
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Started D-Bus System Message Bus.
Jun 30 12:16:51 davros.home.treblig.org systemd-logind[774]: New seat seat0.
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Started Login Service.
Jun 30 12:16:51 davros.home.treblig.org systemd-logind[774]: Watching system buttons on /dev/input/event4 (Power Button)
Jun 30 12:16:51 davros.home.treblig.org systemd-logind[774]: Watching system buttons on /dev/input/event5 (Video Bus)
Jun 30 12:16:51 davros.home.treblig.org systemd-logind[774]: Watching system buttons on /dev/input/event3 (Power Button)
Jun 30 12:16:51 davros.home.treblig.org systemd-logind[774]: Watching system buttons on /dev/input/event2 (Lid Switch)
Jun 30 12:16:51 davros.home.treblig.org systemd-logind[774]: New session 1 of user dg.
Jun 30 12:16:51 davros.home.treblig.org systemd-logind[774]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.
Jun 30 12:16:51 davros.home.treblig.org NetworkManager[508]: <info> Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc. To report bugs please use the NetworkManager mailing list.
Jun 30 12:16:51 davros.home.treblig.org NetworkManager[508]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Jun 30 12:16:51 davros.home.treblig.org NetworkManager[508]: keyfile: parsing Wired connection 1 …
Jun 30 12:16:51 davros.home.treblig.org NetworkManager[508]: keyfile: ipv4.addresses1: Deprecated semicolon at the end of value.
Jun 30 12:16:51 davros.home.treblig.org NetworkManager[508]: keyfile: ipv4.addresses1: address 192.168.66.25/25 gateway 192.168.66.1
Jun 30 12:16:51 davros.home.treblig.org NetworkManager[508]: keyfile: read connection ‘Wired connection 1’
Jun 30 12:16:51 davros.home.treblig.org NetworkManager[508]: <warn> NameHasOwner request failed: Connection was disconnected before a reply was received
Jun 30 12:16:51 davros.home.treblig.org dbus-daemon[775]: dbus[775]: [system] Activating via systemd: service name=‘org.freedesktop.PolicyKit1’ unit=‘polkit.service’
Jun 30 12:16:51 davros.home.treblig.org dbus[775]: [system] Activating via systemd: service name=‘org.freedesktop.PolicyKit1’ unit=‘polkit.service’
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Starting Authorization Manager…
Jun 30 12:16:51 davros.home.treblig.org polkitd[776]: Started polkitd version 0.110
Jun 30 12:16:51 davros.home.treblig.org polkitd[776]: Loading rules from directory /etc/polkit-1/rules.d
Jun 30 12:16:51 davros.home.treblig.org polkitd[776]: Loading rules from directory /usr/share/polkit-1/rules.d
Jun 30 12:16:52 davros.home.treblig.org polkitd[776]: Finished loading, compiling and executing 2 rules
Jun 30 12:16:52 davros.home.treblig.org dbus-daemon[775]: dbus[775]: [system] Successfully activated service ‘org.freedesktop.PolicyKit1’
Jun 30 12:16:52 davros.home.treblig.org dbus[775]: [system] Successfully activated service ‘org.freedesktop.PolicyKit1’
Jun 30 12:16:52 davros.home.treblig.org systemd[1]: Started Authorization Manager.
Jun 30 12:16:52 davros.home.treblig.org polkitd[776]: Acquired the name org.freedesktop.PolicyKit1 on the system bus
Jun 30 12:16:52 davros.home.treblig.org NetworkManager[508]: <info> monitoring kernel firmware directory ‘/lib/firmware’.
Jun 30 12:16:52 davros.home.treblig.org NetworkManager[508]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.2/0000:05:00.0/ieee80211/phy0/rfkill0) (driver iwl3945)
Jun 30 12:16:52 davros.home.treblig.org NetworkManager[508]: <warn> failed to request default Bluetooth adapter.
Jun 30 12:16:52 davros.home.treblig.org NetworkManager[508]: <info> WiFi hardware radio set enabled
Jun 30 12:16:52 davros.home.treblig.org NetworkManager[508]: <warn> NameHasOwner request failed: Disconnected from D-Bus (or argument error during call)
Jun 30 12:16:52 davros.home.treblig.org NetworkManager[508]: <warn> NameHasOwner request failed: Disconnected from D-Bus (or argument error during call)
Jun 30 12:16:52 davros.home.treblig.org NetworkManager[508]: <error> [1372591012.515131] [nm-dbus-manager.c:332] nm_dbus_manager_start_service(): Could not acquire the NetworkManager service.
Jun 30 12:16:52 davros.home.treblig.org NetworkManager[508]: <error> [1372591012.515175] [main.c:599] main(): failed to start the dbus service.
Jun 30 12:16:52 davros.home.treblig.org NetworkManager[508]: <info> exiting (error)
Jun 30 12:16:52 davros.home.treblig.org systemd[1]: NetworkManager.service: main process exited, code=exited, status=1/FAILURE
Jun 30 12:16:52 davros.home.treblig.org systemd[1]: Failed to start Network Manager.
Jun 30 12:16:52 davros.home.treblig.org systemd[1]: Dependency failed for Network Manager Wait Online.
Jun 30 12:16:52 davros.home.treblig.org systemd[1]: Job NetworkManager-wait-online.service/start failed with result ‘dependency’.
Jun 30 12:16:52 davros.home.treblig.org systemd[1]: Unit NetworkManager.service entered failed state

Thanks in advance,

Dave

robin_listas · June 30, 2013, 2:13pm

On 2013-06-30 13:56, penguin42 wrote:
>
> Hi,
> I installed openSUSE 12.3 on my core2 laptop last week, and was
> having some problems where I had to manually start
> Networkmanager, that problem went away, and I’d been using it for a few
> days, and I updated to Tumbleweed yesterday,

Then you have to ask in the tumbleweed forum. Please ask a moderator to
move your thread (report button at bottom left).

> Jun 30 12:16:38 davros.home.treblig.org systemd[1]: Started Purge old
> kernels.

Please use code tags for printouts and commands. Advanced forum editor,
‘#’ button. Posting in Code Tags - A Guide

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

penguin42 · June 30, 2013, 2:31pm

Then you have to ask in the tumbleweed forum. Please ask a moderator to
move your thread (report button at bottom left).

OK, have done - although note that as I stated I was having to start nm manually
some of the time on my 12.3 install; so it might be more general.

Thanks for the advice on formatting logs; I’ll try and remember for next time.

Dave

knurpht · June 30, 2013, 3:25pm

If the issue was already there on 12.3 I don’t see why it should be moved to Tumbleweed. If you use KDE, you’re using the openSUSE 12.3 packages anyway, since there are no TW KDE packages.
What I’m interested in, is the output of


zypper lr -d

plus, how you perform your updates / upgrades.

robin_listas · June 30, 2013, 3:23pm

On 2013-06-30 14:36, penguin42 wrote:
> OK, have done - although note that as I stated I was having to start nm
> manually
> some of the time on my 12.3 install; so it might be more general.

Maybe, but tumbleweed has specific problems.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

penguin42 · June 30, 2013, 4:07pm

Knurpht:

If the issue was already there on 12.3 I don’t see why it should be moved to Tumbleweed. If you use KDE, you’re using the openSUSE 12.3 packages anyway, since there are no TW KDE packages.
What I’m interested in, is the output of
zypper lr -d


dg@davros:~> sudo zypper lr -d
root's password:
#  | Alias                     | Name                               | Enabled | Refresh | Priority | Type   | URI                                                                      | Service
---+---------------------------+------------------------------------+---------+---------+----------+--------+--------------------------------------------------------------------------+--------
 1 | Tumbleweed                | Tumbleweed                         | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ |        
 2 | X11:Utilities             | X11:Utilities                      | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/X11:/Utilities/openSUSE_12.3   |        
 3 | openSUSE Current OSS      | openSUSE Current OSS               | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/openSUSE-current/repo/oss/     |        
 4 | openSUSE Current non-OSS  | openSUSE Current non-OSS           | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/openSUSE-current/repo/non-oss/ |        
 5 | openSUSE Current updates  | openSUSE Current updates           | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/openSUSE-current/                    |        
 6 | repo-debug                | openSUSE-12.3-Debug                | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/distribution/12.3/repo/oss/           |        
 7 | repo-debug-update         | openSUSE-12.3-Update-Debug         | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/update/12.3/                          |        
 8 | repo-debug-update-non-oss | openSUSE-12.3-Update-Debug-Non-Oss | No      | Yes     |   99     | NONE   | http://download.opensuse.org/debug/update/12.3-non-oss/                  |        
 9 | repo-non-oss              | openSUSE-12.3-Non-Oss              | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/12.3/repo/non-oss/             |        
10 | repo-oss                  | openSUSE-12.3-Oss                  | Yes     | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/12.3/repo/oss/                 |        
11 | repo-source               | openSUSE-12.3-Source               | No      | Yes     |   99     | NONE   | http://download.opensuse.org/source/distribution/12.3/repo/oss/          |        
12 | repo-update               | openSUSE-12.3-Update               | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/12.3/                                |        
13 | repo-update-non-oss       | openSUSE-12.3-Update-Non-Oss       | Yes     | Yes     |   99     | rpm-md | http://download.opensuse.org/update/12.3-non-oss/                        |

plus, how you perform your updates / upgrades.

Mostly using the upgrade GUI on KDE, to upgrade to Tumbleweed I followed the manual set of instructions at Portal:Tumbleweed - openSUSE Wiki

Thanks for the help,

Dave

tsu2 · June 30, 2013, 5:51pm

Regardless where this thread belongs,

According to your journal log, it looks like there is a problem starting system components in the correct order.

First systemd tries to start but fails.
Later systemd tries to start again and is successful.
But, when NM tries to start, it’s missing a dependency related to “NameHasOwner request failed”

Googling “NameHasRequest failed” returns several hits.
The following solution might band-aid your situation but something is very different and wrong about your system, maybe it’s time to run a “zypper up” or avoid Tumbleweed?
[solved] Network Manager fails on boot - Chakra 2011.04 Ms 4 - x64 (Page 1) / Support - Platform / The Chakra Project - Forums](http://chakra-project.org/bbs/viewtopic.php?pid=31324)

TSU

penguin42 · June 30, 2013, 6:11pm

Well, I’m happy to stick with Tumbleweed and would prefer to file bugs/maybe understand more of what’s going on.
(Manually starting nm is annoying but not difficult); that link suggests an ordering issue with starting dbus after NetworkManager
but then I just spotted the following in the logs that looks like some other dbus issue:


Jun 30 12:16:48 davros.home.treblig.org dbus[503]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
Jun 30 12:16:51 davros.home.treblig.org dbus-daemon[503]: dbus[503]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
Jun 30 12:16:51 davros.home.treblig.org dbus-daemon[503]: dbus[503]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Jun 30 12:16:51 davros.home.treblig.org dbus-daemon[503]: process 503: arguments to dbus_message_set_reply_serial() were incorrect, assertion "reply_serial != 0" failed in file dbus-message.c line 1070.
Jun 30 12:16:51 davros.home.treblig.org dbus-daemon[503]: This is normally a bug in some application using the D-Bus library.
Jun 30 12:16:51 davros.home.treblig.org dbus-daemon[503]: D-Bus not built with -rdynamic so unable to print a backtrace
Jun 30 12:16:51 davros.home.treblig.org dbus[503]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
Jun 30 12:16:51 davros.home.treblig.org dbus[503]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Jun 30 12:16:51 davros.home.treblig.org NetworkManager[508]: <error> [1372591011.690606] [nm-manager-auth.c:87] pk_authority_get(): Failed to initialize PolicyKit: (24) Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached
Jun 30 12:16:51 davros.home.treblig.org avahi-daemon[481]: Disconnected from D-Bus, exiting.
Jun 30 12:16:51 davros.home.treblig.org avahi-daemon[481]: Got SIGTERM, quitting.
Jun 30 12:16:51 davros.home.treblig.org avahi-daemon[481]: avahi-daemon 0.6.31 exiting.
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: dbus.service: main process exited, code=killed, status=6/ABRT
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Unit dbus.service entered failed state
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Failed to start Login Service.
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Unit systemd-logind.service entered failed state
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Stopping Login Service...
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Starting Login Service...
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Starting D-Bus System Message Bus...
Jun 30 12:16:51 davros.home.treblig.org systemd[1]: Started D-Bus System Message Bus.

So is that dbus dieing?

Dave

wolfi323 · June 30, 2013, 6:37pm

Well, at least it is a problem with dbus.

Googling for your dbus assertion I found this:
https://bugzilla.redhat.com/show_bug.cgi?id=708866
where they fixed it by manually starting the ConsoleKit daemon.

But ConsoleKit is not installed by default anymore on 12.3 AFAIK.
So was this a new install or an upgrade?

Do you have ConsoleKit installed?

rpm -qa | grep ConsoleKit

Is ConsoleKit enabled?

systemctl status console-kit-daemon.service

If it is not enabled, try to enable it.

sudo systemctl enable console-kit-daemon.service

Or try to uninstall it if it is installed. Normally on 12.3 systemd-logind takes over its functionality.

And if it is not installed, maybe try to install (and enable) it?

penguin42 · June 30, 2013, 6:57pm

wolfi323:

Well, at least it is a problem with dbus.

Googling for your dbus assertion I found this:
https://bugzilla.redhat.com/show_bug.cgi?id=708866
where they fixed it by manually starting the ConsoleKit daemon.

But ConsoleKit is not installed by default anymore on 12.3 AFAIK.
So was this a new install or an upgrade?

Do you have ConsoleKit installed?
rpm -qa | grep ConsoleKit

12.3 fresh install last week, upgrade to Tumbleweed yesterday. 12.3 did have similar symptoms
intermittently (and I don’t yet know how repeatable this is on Tumbleweed)
That rpm returns nothing (rpm -qa ConsoleKit is easier as well)

Is ConsoleKit enabled?

systemctl status console-kit-daemon.service

If it is not enabled, try to enable it.

sudo systemctl enable console-kit-daemon.service

Or try to uninstall it if it is installed. Normally on 12.3 systemd-logind takes over its functionality.

And if it is not installed, maybe try to install (and enable) it?

But is it the same bug as the RH 708866? In that bug the original reporter had a message about
ConsoleKit starting/failing to start - I’ve got no mention of consolekit in the log at all.

It seems odd for dbus to provide no details in it’s error about what process it was performing the
action for when it barfed (especailly since it then says ‘This is normally a bug in some application using the D-Bus
library’ so we’re left not knowing who kicked it.

Dave

wolfi323 · June 30, 2013, 7:22pm

No, “rpm -qa ConsoleKit” is NOT the same.

But is it the same bug as the RH 708866? In that bug the original reporter had a message about
ConsoleKit starting/failing to start - I’ve got no mention of consolekit in the log at all.

You’re right, but in comment 8 there is no mention of consolekit in the log either.
Anyway, it was just a thought after reading this, that maybe ConsoleKit might be interfering somehow.

It seems odd for dbus to provide no details in it’s error about what process it was performing the
action for when it barfed (especailly since it then says ‘This is normally a bug in some application using the D-Bus
library’ so we’re left not knowing who kicked it.

I guess “sudo systemd-journalctl --unit=dbus.service” doesn’t provide more information?

Maybe polkit.service is not running? (the first failure is “Failed to activate service ‘org.freedesktop.PolicyKit1’: timed out”)

systemctl status polkit.service
sudo systemd-journalctl --unit=polkit.service