a start job is running for network manager

[peekaa]

After fresh new install debian unstable I have at boot message "a start job is running for network manager" which counts to 1m30s then is prints "failed", booting continues, the internet works fine, all is fine after that, when in gnome. If someone could help... Thank you.

[Head_on_a_Stick]

Please post the output of:

Code: Select all

systemctl --failed
# journalctl -u NetworkManager.service

[peekaa]

Code: Select all

root@chietech:/home/omega# systemctl --failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

Code: Select all

root@chietech:/home/omega# journalctl -u NetworkManager.service
-- Logs begin at St 2016-10-19 16:06:50 CEST, end at St 2016-10-19 16:09:47 CEST. --
říj 19 16:06:51 chietech systemd[1]: Starting Network Manager...
říj 19 16:08:21 chietech systemd[1]: NetworkManager.service: Start operation timed out. Terminating.
říj 19 16:08:21 chietech systemd[1]: Failed to start Network Manager.
říj 19 16:08:21 chietech systemd[1]: NetworkManager.service: Unit entered failed state.
říj 19 16:08:21 chietech systemd[1]: NetworkManager.service: Failed with result 'timeout'.
říj 19 16:08:21 chietech systemd[1]: NetworkManager.service: Service hold-off time over, scheduling restart.
říj 19 16:08:21 chietech systemd[1]: Stopped Network Manager.
říj 19 16:08:21 chietech systemd[1]: Starting Network Manager...
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9086] NetworkManager (version 1.4.2) is starting...
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9088] Read config: /etc/NetworkManager/NetworkManager.conf
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9172] manager[0x14860a0]: monitoring kernel firmware directory '/lib/firmware'.
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9173] monitoring ifupdown state file '/run/network/ifstate'.
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9224] dns-mgr[0x147e810]: init: dns=default, rc-manager=resolvconf
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9246] manager[0x14860a0]: WiFi hardware radio set enabled
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9246] manager[0x14860a0]: WWAN hardware radio set enabled
říj 19 16:08:21 chietech systemd[1]: Started Network Manager.
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9758] init!
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9764]       interface-parser: parsing file /etc/network/interfaces
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9765]       interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*
říj 19 16:08:21 chietech NetworkManager[501]: <warn>  [1476886101.9766] interfaces file /etc/network/interfaces.d/* doesn't exist
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9766]       interface-parser: finished parsing file /etc/network/interfaces
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9767] management mode: unmanaged
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9772] devices added (path: /sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0/net/enp3s0, iface: enp3s0)
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9773] device added (path: /sys/devices/pci0000:00/0000:00:1c.2/0000:03:00.0/net/enp3s0, iface: enp3s0): no ifu
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9773] devices added (path: /sys/devices/virtual/net/lo, iface: lo)
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9773] device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9773] end _init.
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9774] settings: loaded plugin ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager 
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9775] settings: loaded plugin keyfile: (c) 2007 - 2015 Red Hat, Inc.  To report bugs please use the NetworkMan
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9775] (21633952) ... get_connections.
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9775] (21633952) ... get_connections (managed=false): return empty list.
říj 19 16:08:21 chietech NetworkManager[501]: <info>  [1476886101.9993] keyfile: new connection /etc/NetworkManager/system-connections/Wired connection 1 (6641eedb-4c40-4de5-8b
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.0002] get unmanaged devices count: 0
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1516] settings: hostname: using hostnamed
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1517] settings: hostname changed from (none) to "chietech"
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1522] dhcp-init: Using DHCP client 'dhclient'
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1523] manager: WiFi enabled by radio killswitch; enabled by state file
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1524] manager: WWAN enabled by radio killswitch; enabled by state file
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1525] manager: Networking is enabled by state file
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1526] Loaded device plugin: NMVxlanFactory (internal)
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1527] Loaded device plugin: NMVlanFactory (internal)
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1527] Loaded device plugin: NMVethFactory (internal)
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1528] Loaded device plugin: NMTunFactory (internal)
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1529] Loaded device plugin: NMMacvlanFactory (internal)
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1530] Loaded device plugin: NMIPTunnelFactory (internal)
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1530] Loaded device plugin: NMInfinibandFactory (internal)
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1531] Loaded device plugin: NMEthernetFactory (internal)
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1532] Loaded device plugin: NMBridgeFactory (internal)
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1532] Loaded device plugin: NMBondFactory (internal)
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1652] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluet
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1675] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1740] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-team.s
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1759] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wwan.s
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1783] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-wifi.s
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1804] device (lo): link connected
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1825] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/0)
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1861] manager: (enp3s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/1)
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.1888] device (enp3s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
říj 19 16:08:22 chietech NetworkManager[501]: <info>  [1476886102.2415] ModemManager available in the bus
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8289] device (enp3s0): link connected
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8298] device (enp3s0): state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8310] policy: auto-activating connection 'Wired connection 1'
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8332] device (enp3s0): Activation: starting connection 'Wired connection 1' (6641eedb-4c40-4de5-8bbc-73ed78485
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8335] device (enp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8338] manager: NetworkManager state is now CONNECTING
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8346] device (enp3s0): state change: prepare -> config (reason 'none') [40 50 0]
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8354] device (enp3s0): state change: config -> ip-config (reason 'none') [50 70 0]
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8371] dhcp4 (enp3s0): activation: beginning transaction (timeout in 45 seconds)
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8466] dhcp4 (enp3s0): dhclient started with pid 566
říj 19 16:08:23 chietech dhclient[566]: DHCPREQUEST of 192.168.1.106 on enp3s0 to 255.255.255.255 port 67
říj 19 16:08:23 chietech dhclient[566]: DHCPACK of 192.168.1.106 from 192.168.1.1
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8931] dhcp4 (enp3s0):   address 192.168.1.106
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8931] dhcp4 (enp3s0):   plen 24 (255.255.255.0)
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8932] dhcp4 (enp3s0):   gateway 192.168.1.1
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8932] dhcp4 (enp3s0):   server identifier 192.168.1.1
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8933] dhcp4 (enp3s0):   lease time 7200
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8933] dhcp4 (enp3s0):   nameserver '172.16.1.1'
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8934] dhcp4 (enp3s0):   nameserver '172.16.1.254'
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8934] dhcp4 (enp3s0): state changed unknown -> bound
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8963] device (enp3s0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.8984] device (enp3s0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.9001] device (enp3s0): state change: secondaries -> activated (reason 'none') [90 100 0]
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.9006] manager: NetworkManager state is now CONNECTED_LOCAL
říj 19 16:08:23 chietech dhclient[566]: bound to 192.168.1.106 -- renewal in 3431 seconds.
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.9079] manager: NetworkManager state is now CONNECTED_GLOBAL
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.9082] policy: set 'Wired connection 1' (enp3s0) as default for IPv4 routing and DNS
říj 19 16:08:23 chietech NetworkManager[501]: <info>  [1476886103.9093] device (enp3s0): Activation: successful, device activated.
říj 19 16:08:24 chietech NetworkManager[501]: <info>  [1476886104.9086] bluez: use BlueZ version 5
říj 19 16:08:29 chietech NetworkManager[501]: <info>  [1476886109.5177] manager: startup complete
lines 46-90/90 (END)

IPV6 is disabled. To be accurate, its debian testing, not unstable

Code: Select all

root@chietech:/home/omega# uname -a
Linux chietech 4.7.0-1-amd64 #1 SMP Debian 4.7.6-1 (2016-10-07) x86_64 GNU/Linux

[Bulkley]

This is most likely a Network-Manager issue, not your Debian install. When it works properly Network-Manager is a beautiful tool. When it causes problems it can drive you absolutely nuts. Somewhere during the install you gave Network-Manager permission to do what it is doing. Tracking that down may be difficult.

Did Network-Manager create a user file in the hidden files? If so, rename it and reboot. It should make a new one which you can configure from scratch. If that doesn't work, it might be easier to remove Network-Manager and install Wicd.

[peekaa]

Well I think its the systemd issue.... If you think, please move topic to appropriate forum.

[GarryRicketson]

I doubt it is entirely a "systemd" issue, probably more of
a combination, network manager, and how to configure
on a systemd system, I can't offer any real help, because
I do not use the newer systems, but the best place I know
of to get help with "network manager",

Send networkmanager-list mailing list submissions to:
networkmanager-list@gnome.org
=====================
To subscribe or unsubscribe via the World Wide Web, visit:
https://mail.gnome.org/mailman/listinfo ... nager-list
or, via email, send a message with subject or body 'help' to:
networkmanager-list-request@gnome.org
You can reach the person managing the list at
networkmanager-list-owner@gnome.org

They are pretty up to date on the both most recent issues, and
past, old problems .
-------------- edit--offtopic------------
Just some additional comments, not trying to argue,
but some logical thoughts. (at least logical to me)

But by saying it is a systemd issue, kind of brings up another topic,
and

To be accurate, its debian testing, not unstable

All though I do not use the newer Debian versions as my main system,
I do keep them on a VM, and first off:
The stable version Jessie, when it was first released, I did have some
problems with network manager, in fact I ended up using "WICD" ,
and that solved the problem, later fairly recently, when I upgraded it
to the current release 8.6, there are no problems with network manager
and I am using it again , on that.
As far as Debian testing goes, it certainly seems far from stable to
me, I did not have any problems with network manager, but all kinds
of other problems, mostly with some of Desktop Environments,
at first no,
but then later, yes,... to many problems, and all ways changing, it
might work good this week, but next week, after any updates, or
if I installed any new packages,...something else breaks,...I am not
that skilled, or advanced, to try to keep that kind of mess working,
I don't mean to be derogatory, or sound like I am putting the "testing" version down, I am not,....it is a necessary version , in order to develop,
and get the planned new version "stretch" working, as a stable version,
how ever , Debian testing, is far from being stable, or reliable, the only thing it is good for, is "testing", I guess that is why they give it that name.

[peekaa]

Thank you, I just give a try to that wicd, it seems to work for now.

[Head_on_a_Stick]

With NetworkManager running, can we see the output of:

Code: Select all

systemd-analyze critical-chain

According to the journal, NM only takes ~2 seconds to come up and works correctly

[peekaa]

Well I just switched to wicd....

[peekaa]

...Debian testing, is far from being stable, or reliable, the only thing it is good for, is "testing", I guess that is why they give it that name.

Well, somewhere else i read that for new motherboads and laptops is testing version much better, cause it might include much more things for newers hw that the old one.

[Thorny]

Well, somewhere else i read that for new motherboads and laptops is testing version much better, cause it might include much more things for newers hw that the old one.

Will you please tell us where you read that.

The best advice for users new to Debian is to use stable, Garry is correct, the testing version is for testing and new users often do not yet have the skills to deal with problems that happen and with things that are broken for a while. Testing is not "just a newer version of Debian", it is where what will become the newer version (in this case Stretch), is well, tested before release.

Have a look at the Debian GNU/Linux FAQ Chapter 3 Choosing a Debian distribution.
https://www.debian.org/doc/manuals/debi ... ng.en.html

[peekaa]

Will you please tell us where you read that.

I really dont know now, it is a long while ago. Thank you for another advice.

[GarryRicketson]

Actually there are a couple of threads here on this forum
where they had very new hardware, and the only option was to use testing, or "stretch".
, off hand though I don't remember where they are though.

[sunrat]

Newer hardware can usually be made to work in Jessie by adding selected packages from backports, particularly kernel, video drivers and firmware.
I have a recent Skylake system working nicely with kernel 4.7, nvidia 352.79 and intel-microcode from backports.
I did have that "start job is running for network manager" problem once. Think it was because the USB wifi dongle wasn't initialized in time. Eventually I purged network-manager and configured interfaces file manually. No problem now. YMMV.

[Bulkley]

Actually there are a couple of threads here on this forum
where they had very new hardware, and the only option was to use testing, or "stretch".

Newer hardware sometimes needs a newer kernel and maybe a newer driver or two. That's not the same as using Testing.

Eventually I purged network-manager and configured interfaces file manually.

Me too. It cuts out the middleman so to speak. The active Wifi program is wpa-supplicant. We really don't need Network-Manager or Wicd to mediate, particularly on a desktop that only uses one connection.

[peekaa]

Are you trying to tell that I can even uninstall wicd and my internet connection will stay?

[Bulkley]

Are you trying to tell that I can even uninstall wicd and my internet connection will stay?

No, you have to set it up. Study this.

[peekaa]

I have never said I have wifi. I have have cable rj45 connection.

[sunrat]

Even easier with no wifi. You probably just need to edit the file /etc/network/interfaces and add something like this_

Code: Select all

auto eth0
    allow-hotplug eth0
    iface eth0 inet dhcp

Lots more here - https://wiki.debian.org/NetworkConfiguration but only the first bit applies for basic configuration.