![[BunsenLabs Logo]](/img/bl.svg)
You are not logged in.
- Topics: Active | Unanswered
#1 2016-09-21 19:53:34
- august
- Member
- Registered: 2016-09-21
- Posts: 6
[SOLVED] A start job is running for network manager 1m 30sec
Running BunSid and everything is running smoothly except I get "A start job is running for Network Manager" with a one minute thirty second timeout. Doing some googling I found ways to reduce the timeout but I don't know what an appropriate time is and don't want to go tinkering with something I don't understand without asking here.
Last edited by Head_on_a_Stick (2016-11-15 21:45:52)
Offline
#2 2016-09-21 20:38:06
- Head_on_a_Stick
- Member
- From: London
- Registered: 2015-09-29
- Posts: 9,093
- Website
Re: [SOLVED] A start job is running for network manager 1m 30sec
Hello and welcome 
Can we see the output of:
systemctl status NetworkManager
systemctl --failed
systemd-analyze critical-chainPlease also post the full content of /etc/network/interfaces
As you have probably found out, it is possible to reduce the timeout by editing /etc/systemd/system.conf but we should probably try to find out the cause of the error rather than simply ignoring it.
Offline
#3 2016-09-21 20:51:53
- august
- Member
- Registered: 2016-09-21
- Posts: 6
Re: [SOLVED] A start job is running for network manager 1m 30sec
anton@minicrunch:~$ systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2016-09-21 16:46:37 EDT; 1min 49s ago
Docs: man:NetworkManager(8)
Main PID: 359 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
├─359 /usr/sbin/NetworkManager --no-daemon
└─673 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient-63f04723-a678-42bb-9
lines 1-8/8 (END)
anton@minicrunch:~$ anton@minicrunch:~$ systemctl status NetworkManager
bash: anton@minicrunch:~$: command not found
anton@minicrunch:~$ ● NetworkManager.service - Network Manager
bash: ●: command not found
anton@minicrunch:~$ Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
bash: syntax error near unexpected token `('
anton@minicrunch:~$ Active: active (running) since Wed 2016-09-21 16:46:37 EDT; 1min 49s ago
bash: syntax error near unexpected token `('
anton@minicrunch:~$ Docs: man:NetworkManager(8)
bash: syntax error near unexpected token `('
anton@minicrunch:~$ Main PID: 359 (NetworkManager)
bash: syntax error near unexpected token `('
anton@minicrunch:~$ CGroup: /system.slice/NetworkManager.service
bash: CGroup:: command not found
anton@minicrunch:~$ ├─359 /usr/sbin/NetworkManager --no-daemon
bash: ├─359: command not found
anton@minicrunch:~$ └─673 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient-63f04723-a678-42bb-9
bash: └─673: command not found
anton@minicrunch:~$ lines 1-8/8 (END)
bash: syntax error near unexpected token `('
anton@minicrunch:~$ anton@minicrunch:~$ systemctl status NetworkManager
bash: anton@minicrunch:~$: command not found
anton@minicrunch:~$ ● NetworkManager.service - Network Manager
bash: ●: command not found
anton@minicrunch:~$ Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
bash: syntax error near unexpected token `('
anton@minicrunch:~$ Active: active (running) since Wed 2016-09-21 16:46:37 EDT; 1min 49s ago
bash: syntax error near unexpected token `('
anton@minicrunch:~$ Docs: man:NetworkManager(8)
bash: syntax error near unexpected token `('
anton@minicrunch:~$ Main PID: 359 (NetworkManager)
bash: syntax error near unexpected token `('
anton@minicrunch:~$ CGroup: /system.slice/NetworkManager.service
bash: CGroup:: command not found
anton@minicrunch:~$ ├─359 /usr/sbin/NetworkManager --no-daemon
bash: ├─359: command not found
anton@minicrunch:~$ └─673 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient-63f04723-a678-42bb-9
bash: └─673: command not found
anton@minicrunch:~$ lines 1-8/8 (END)
bash: syntax error near unexpected token `('interfaces:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopbackOffline
#4 2016-09-21 21:19:00
- Head_on_a_Stick
- Member
- From: London
- Registered: 2015-09-29
- Posts: 9,093
- Website
Re: [SOLVED] A start job is running for network manager 1m 30sec
There seems to have been a copy/paste error with the last two commands, could you try again please?
Also, what are the details of your networking set up?
Is it wired or wireless? Do you use a proxy? etc
Offline
#5 2016-09-22 20:40:49
- august
- Member
- Registered: 2016-09-21
- Posts: 6
Re: [SOLVED] A start job is running for network manager 1m 30sec
Oops! Let me try again:
anton@minicrunch:~$ 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'.
anton@minicrunch:~$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @21.910s
└─multi-user.target @21.910s
└─ntp.service @21.876s +33ms
└─network-online.target @21.861s
└─NetworkManager-wait-online.service @21.520s +341ms
└─NetworkManager.service @852ms +20.663s
└─dbus.service @758ms
└─basic.target @666ms
└─sockets.target @663ms
└─uuidd.socket @663ms
└─sysinit.target @639ms
└─systemd-backlight@backlight:acpi_video0.service @2.304s +16ms
└─system-systemd\x2dbacklight.slice @2.288s
└─system.slice @106ms
└─-.slice @94msWireless, no proxy.
Offline
#6 2016-09-23 06:25:09
- Head_on_a_Stick
- Member
- From: London
- Registered: 2015-09-29
- Posts: 9,093
- Website
Re: [SOLVED] A start job is running for network manager 1m 30sec
OK, let's see if the journal has anything.
What does this say:
sudo journalctl -u NetworkManager.serviceOffline
#7 2016-09-23 15:45:43
- august
- Member
- Registered: 2016-09-21
- Posts: 6
Re: [SOLVED] A start job is running for network manager 1m 30sec
anton@minicrunch:~$ sudo journalctl -u NetworkManager.service
-- Logs begin at Fri 2016-09-23 11:43:49 EDT, end at Fri 2016-09-23 11:45:06 EDT. --
Sep 23 11:43:49 minicrunch systemd[1]: Starting Network Manager...
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8269] NetworkManager (version 1.4.0) is starting...
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8269] Read config: /etc/NetworkManager/NetworkManager.conf
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8361] manager[0xb24050]: monitoring kernel firmware directory '/lib/firmware'.
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8362] monitoring ifupdown state file '/run/network/ifstate'.
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8418] dns-mgr[0xb1c830]: init: dns=default, rc-manager=resolvconf
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8445] rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/ieee8
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8448] manager[0xb24050]: WiFi hardware radio set enabled
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8448] manager[0xb24050]: WWAN hardware radio set enabled
Sep 23 11:44:01 minicrunch systemd[1]: Started Network Manager.
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8975] init!
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8977] interface-parser: parsing file /etc/network/interfaces
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8977] interface-parser: source line includes interfaces file(s) /etc/network/interfaces.d/*
Sep 23 11:44:01 minicrunch NetworkManager[353]: <warn> [1474645441.8978] interfaces file /etc/network/interfaces.d/* doesn't exist
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8978] interface-parser: finished parsing file /etc/network/interfaces
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8978] management mode: unmanaged
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8982] devices added (path: /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/net/wlan0, iface: wlan0)
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8982] device added (path: /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/net/wlan0, iface: wlan0):
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8982] devices added (path: /sys/devices/virtual/net/lo, iface: lo)
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8982] device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8982] end _init.
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8983] settings: loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the Network
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8983] settings: loaded plugin keyfile: (c) 2007 - 2015 Red Hat, Inc. To report bugs please use the Ne
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8983] (11828048) ... get_connections.
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.8983] (11828048) ... get_connections (managed=false): return empty list.
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.9232] keyfile: new connection /etc/NetworkManager/system-connections/The Palisades (63f04723-a678-42bb
Sep 23 11:44:01 minicrunch NetworkManager[353]: <info> [1474645441.9263] get unmanaged devices count: 0
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0309] settings: hostname: using hostnamed
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0309] settings: hostname changed from (none) to "minicrunch"
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0312] dhcp-init: Using DHCP client 'dhclient'
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0312] manager: WiFi enabled by radio killswitch; enabled by state file
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0313] manager: WWAN enabled by radio killswitch; enabled by state file
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0313] manager: Networking is enabled by state file
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0313] Loaded device plugin: NMVxlanFactory (internal)
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0314] Loaded device plugin: NMVlanFactory (internal)
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0314] Loaded device plugin: NMVethFactory (internal)
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0314] Loaded device plugin: NMTunFactory (internal)
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0314] Loaded device plugin: NMMacvlanFactory (internal)
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0315] Loaded device plugin: NMIPTunnelFactory (internal)
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0315] Loaded device plugin: NMInfinibandFactory (internal)
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0315] Loaded device plugin: NMEthernetFactory (internal)
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0315] Loaded device plugin: NMBridgeFactory (internal)
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0315] Loaded device plugin: NMBondFactory (internal)
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0375] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugi
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0385] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0423] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugi
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0491] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plug
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0513] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugi
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0531] device (lo): link connected
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0542] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/0)
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0548] (wlan0): using nl80211 for WiFi device control
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0551] device (wlan0): driver supports Access Point (AP) mode
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0567] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/1)
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0590] device (wlan0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0770] device (wlan0): set-hw-addr: set MAC address to 02:CC:E1:3D:58:62 (scanning)
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.0997] ModemManager available in the bus
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.1434] supplicant: wpa_supplicant running
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.1434] device (wlan0): supplicant interface state: init -> starting
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.1899] sup-iface[0xb5b970,wlan0]: supports 4 scan SSIDs
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.1914] device (wlan0): supplicant interface state: starting -> ready
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.1914] manager: startup complete
Sep 23 11:44:02 minicrunch NetworkManager[353]: <info> [1474645442.1917] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.6677] device (wlan0): supplicant interface state: ready -> inactive
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.7824] policy: auto-activating connection 'The Palisades'
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.7844] device (wlan0): Activation: starting connection 'The Palisades' (63f04723-a678-42bb-9d4c-3fbe860
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.7850] device (wlan0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.7856] manager: NetworkManager state is now CONNECTING
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.7952] device (wlan0): set-hw-addr: set-cloned MAC address to 54:35:30:B2:65:D5 (permanent)
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8243] device (wlan0): supplicant interface state: inactive -> disabled
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8246] device (wlan0): state change: prepare -> config (reason 'none') [40 50 0]
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8249] device (wlan0): Activation: (wifi) access point 'The Palisades' has security, but secrets are re
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8249] device (wlan0): state change: config -> need-auth (reason 'none') [50 60 0]
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8302] device (wlan0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8306] device (wlan0): state change: prepare -> config (reason 'none') [40 50 0]
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8309] device (wlan0): Activation: (wifi) connection 'The Palisades' has security, and secrets exist.
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8310] Config: added 'ssid' value 'The Palisades'
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8310] Config: added 'scan_ssid' value '1'
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8310] Config: added 'key_mgmt' value 'WPA-PSK'
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8311] Config: added 'psk' value '<omitted>'
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8369] sup-iface[0xb5b970,wlan0]: config: set interface ap_scan to 1
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8375] device (wlan0): supplicant interface state: disabled -> inactive
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8616] device (wlan0): supplicant interface state: inactive -> authenticating
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8710] device (wlan0): supplicant interface state: authenticating -> associating
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.8886] device (wlan0): supplicant interface state: associating -> associated
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.9007] device (wlan0): supplicant interface state: associated -> 4-way handshake
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.9474] device (wlan0): supplicant interface state: 4-way handshake -> completed
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.9475] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wir
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.9476] device (wlan0): state change: config -> ip-config (reason 'none') [50 70 0]
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.9488] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Sep 23 11:44:05 minicrunch NetworkManager[353]: <info> [1474645445.9519] dhcp4 (wlan0): dhclient started with pid 674
Sep 23 11:44:05 minicrunch dhclient[674]: DHCPREQUEST of 192.168.1.2 on wlan0 to 255.255.255.255 port 67
Sep 23 11:44:10 minicrunch dhclient[674]: DHCPREQUEST of 192.168.1.2 on wlan0 to 255.255.255.255 port 67
Sep 23 11:44:10 minicrunch dhclient[674]: DHCPACK of 192.168.1.2 from 192.168.1.1
Sep 23 11:44:10 minicrunch NetworkManager[353]: <info> [1474645450.1453] dhcp4 (wlan0): address 192.168.1.2
Sep 23 11:44:10 minicrunch NetworkManager[353]: <info> [1474645450.1453] dhcp4 (wlan0): plen 24 (255.255.255.0)
Sep 23 11:44:10 minicrunch NetworkManager[353]: <info> [1474645450.1454] dhcp4 (wlan0): gateway 192.168.1.1
Sep 23 11:44:10 minicrunch NetworkManager[353]: <info> [1474645450.1454] dhcp4 (wlan0): server identifier 192.168.1.1
Sep 23 11:44:10 minicrunch NetworkManager[353]: <info> [1474645450.1454] dhcp4 (wlan0): lease time 86400
Sep 23 11:44:10 minicrunch NetworkManager[353]: <info> [1474645450.1454] dhcp4 (wlan0): nameserver '192.168.1.1'
Sep 23 11:44:10 minicrunch NetworkManager[353]: <info> [1474645450.1454] dhcp4 (wlan0): state changed unknown -> bound
Sep 23 11:44:10 minicrunch NetworkManager[353]: <info> [1474645450.1478] device (wlan0): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Sep 23 11:44:10 minicrunch NetworkManager[353]: <info> [1474645450.1484] device (wlan0): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Sep 23 11:44:10 minicrunch NetworkManager[353]: <info> [1474645450.1503] device (wlan0): state change: secondaries -> activated (reason 'none') [90 100 0]
Sep 23 11:44:10 minicrunch NetworkManager[353]: <info> [1474645450.1511] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 23 11:44:10 minicrunch NetworkManager[353]: <info> [1474645450.1588] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 23 11:44:10 minicrunch NetworkManager[353]: <info> [1474645450.1589] policy: set 'The Palisades' (wlan0) as default for IPv4 routing and DNS
Sep 23 11:44:10 minicrunch dhclient[674]: bound to 192.168.1.2 -- renewal in 35796 seconds.
Sep 23 11:44:10 minicrunch NetworkManager[353]: <info> [1474645450.1612] device (wlan0): Activation: successful, device activated.Offline
#8 2016-09-24 16:37:06
- Head_on_a_Stick
- Member
- From: London
- Registered: 2015-09-29
- Posts: 9,093
- Website
Re: [SOLVED] A start job is running for network manager 1m 30sec
Well that all looks fine to me, the startup time is roughly 20 seconds or so which is fairly typical for NM.
Does the timeout always continue for the full 90 seconds?
The `systemd-analyze` output suggests not and if this is the case then editing /etc/systemd/system.conf will not change the situation.
You could try switching to ifupdown instead, as outlined in this post:
https://forums.bunsenlabs.org/viewtopic … 416#p36416
That is a little quicker than NM but it still sometimes shows a message, this time about "LSB Interfaces" or some such nonsense...
The quickest solution is a custom unit file using `ip` & `wpa_supplicant`
https://github.com/Head-on-a-Stick/conf … 40.service
(Adjust executable paths to suit Debian)
Offline
#9 2016-11-12 17:21:39
- hap
- Member
- Registered: 2016-11-12
- Posts: 6
Re: [SOLVED] A start job is running for network manager 1m 30sec
I have the same problem, which started a few month ago.
Booting stops at "A start job is running for Network Manager" - 1m30s wait time
$ journalctl -u NetworkManager.service
lis 12 18:07:36 bunsen systemd[1]: Starting Network Manager...
lis 12 18:09:06 bunsen systemd[1]: NetworkManager.service: Start operation timed out. Terminating.
lis 12 18:09:06 bunsen systemd[1]: Failed to start Network Manager.
lis 12 18:09:06 bunsen systemd[1]: NetworkManager.service: Unit entered failed state.
lis 12 18:09:06 bunsen systemd[1]: NetworkManager.service: Failed with result 'timeout'.
lis 12 18:09:06 bunsen systemd[1]: NetworkManager.service: Service hold-off time over, scheduling restart.
lis 12 18:09:06 bunsen systemd[1]: Stopped Network Manager.
lis 12 18:09:06 bunsen systemd[1]: Starting Network Manager...
lis 12 18:09:08 bunsen NetworkManager[911]: <info> [1478970548.8727] NetworkManager (version 1.4.2) is starting...
(...)
$ systemd-analyze critical-chain
graphical.target @1min 30.989s
└─multi-user.target @1min 30.989s
└─sendmail.service @1min 30.937s +51ms
└─network-online.target @1min 30.930s
└─network.target @1min 30.912s
$ systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● networking.service loaded failed failed Raise network interfaces
Bold added by me, red color by stdout. Sendmail looks strange as:
$ dpkg -la sendmail
un sendmail
Last edited by Head_on_a_Stick (2016-11-12 18:21:11)
Offline
#10 2016-11-12 18:20:45
- Head_on_a_Stick
- Member
- From: London
- Registered: 2015-09-29
- Posts: 9,093
- Website
Re: [SOLVED] A start job is running for network manager 1m 30sec
I have the same problem
Is your system also tracking testing/unstable?
What is the output of:
apt-cache policy
journalctl -u networking.service
systemctl list-unit-files | grep enabledAlso, please use code tags when posting terminal output.
Offline
#11 2016-11-12 21:25:33
- hap
- Member
- Registered: 2016-11-12
- Posts: 6
Re: [SOLVED] A start job is running for network manager 1m 30sec
apt-cache policy
100 /var/lib/dpkg/status
release a=now
100 http://www.deb-multimedia.org jessie/non-free amd64 Packages
release v=8.6,o=Unofficial Multimedia Packages,a=stable,n=jessie,l=Unofficial Multimedia Packages,c=non-free,b=amd64
origin www.deb-multimedia.org
100 http://www.deb-multimedia.org jessie/main amd64 Packages
release v=8.6,o=Unofficial Multimedia Packages,a=stable,n=jessie,l=Unofficial Multimedia Packages,c=main,b=amd64
origin www.deb-multimedia.org
500 http://pkg.bunsenlabs.org/debian bunsen-hydrogen/main amd64 Packages
release o=bunsenlabs,n=bunsen-hydrogen,l=bunsenlabs,c=main,b=amd64
origin pkg.bunsenlabs.org
100 http://pkg.bunsenlabs.org/debian jessie-backports/main amd64 Packages
release o=bunsenlabs,n=jessie-backports,l=bunsenlabs,c=main,b=amd64
origin pkg.bunsenlabs.org
500 http://security.debian.org jessie/updates/main amd64 Packages
release v=8,o=Debian,a=stable,n=jessie,l=Debian-Security,c=main,b=amd64
origin security.debian.org
500 http://security.debian.org jessie/updates/contrib amd64 Packages
release v=8,o=Debian,a=stable,n=jessie,l=Debian-Security,c=contrib,b=amd64
origin security.debian.org
500 http://ftp.debian.org/debian jessie/main amd64 Packages
release v=8.6,o=Debian,a=stable,n=jessie,l=Debian,c=main,b=amd64
origin ftp.debian.org
500 http://ftp.debian.org/debian jessie/contrib amd64 Packages
release v=8.6,o=Debian,a=stable,n=jessie,l=Debian,c=contrib,b=amd64
origin ftp.debian.org
500 http://ftp.debian.org/debian jessie/non-free amd64 Packages
release v=8.6,o=Debian,a=stable,n=jessie,l=Debian,c=non-free,b=amd64
origin ftp.debian.org
500 http://ftp.debian.org/debian jessie-updates/main amd64 Packages
release o=Debian,a=stable-updates,n=jessie-updates,l=Debian,c=main,b=amd64
origin ftp.debian.org
500 http://ftp.debian.org/debian jessie-updates/non-free amd64 Packages
release o=Debian,a=stable-updates,n=jessie-updates,l=Debian,c=non-free,b=amd64
origin ftp.debian.org
500 http://ftp.pl.debian.org/debian testing/main amd64 Packages
release o=Debian,a=testing,n=stretch,l=Debian,c=main,b=amd64
origin ftp.pl.debian.org
500 http://ftp.pl.debian.org/debian testing/contrib amd64 Packages
release o=Debian,a=testing,n=stretch,l=Debian,c=contrib,b=amd64
origin ftp.pl.debian.org
500 http://ftp.pl.debian.org/debian testing/non-free amd64 Packages
release o=Debian,a=testing,n=stretch,l=Debian,c=non-free,b=amd64
origin ftp.pl.debian.orgjournalctl -u networking.service
lis 12 18:52:20 bunsen systemd[1]: Starting Raise network interfaces...
lis 12 18:52:21 bunsen systemd[1]: Started Raise network interfaces.systemctl list-unit-files | grep enabled
avahi-daemon.service enabled
binfmt-support.service enabled
console-setup.service enabled
cron.service enabled
dbus-org.freedesktop.Avahi.service enabled
dbus-org.freedesktop.ModemManager1.service enabled
dbus-org.freedesktop.nm-dispatcher.service enabled
display-manager.service enabled
getty@.service enabled
keyboard-setup.service enabled
lightdm.service enabled
live-tools.service enabled
lm-sensors.service enabled
minissdpd.service enabled
ModemManager.service enabled
network-manager.service enabled
networking.service enabled
NetworkManager-dispatcher.service enabled
NetworkManager-wait-online.service enabled
NetworkManager.service enabled
rsync.service enabled
rsyslog.service enabled
ssh.service enabled
sshd.service enabled
syslog.service enabled
systemd-timesyncd.service enabled
vnstat.service enabled
avahi-daemon.socket enabled
uuidd.socket enabled
remote-fs.target enabled
apt-daily.timer enabled cat /proc/version
Linux version 4.7.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.4.1 20160904 (Debian 5.4.1-2) ) #1 SMP Debian 4.7.8-1 (2016-10-19)cat /etc/debian_version
stretch/sidThank you for your interst and fast answer.
Last edited by hap (2016-11-12 21:34:55)
Offline
#12 2016-11-13 15:37:21
- Head_on_a_Stick
- Member
- From: London
- Registered: 2015-09-29
- Posts: 9,093
- Website
Re: [SOLVED] A start job is running for network manager 1m 30sec
You appear to be running what is known as a "FrankenDebian" system, which is a Debian stable machine with added testing/unstable/non-Debian repositories -- this is a bad thing and is unlikely to work for long.
See https://wiki.debian.org/DontBreakDebian … nkenDebian & http://217.196.43.138/viewtopic.php?f=2 … ea087a188f for more on this.
I would strongly recommend re-installing a stable-based system from scratch if you want to have a reliable system.
Otherwise, remove all of the "jessie" lines in /etc/apt/sources.list and then use:
sudo apt update
sudo apt-get dist-upgradeBe aware that this will convert your system to track Debian testing (stretch) and may break a few things; further user intervention may be required for a fully functional desktop.
Finally, I don't have a Debian box handy to check but this looks wrong:
network-manager.service enabled
To stop that .service from starting at the next boot, use:
sudo systemctl disable network-manager.serviceIf that breaks things further, reverse the effects with:
sudo systemctl enable network-manager.serviceOffline
#13 2016-11-13 21:33:28
- hap
- Member
- Registered: 2016-11-12
- Posts: 6
Re: [SOLVED] A start job is running for network manager 1m 30sec
sudo systemctl disable network-manager.serviceMakes nice 8 sek boot time. Unfortunately no network available and I have to manually:
sudo service network-manager startAny simple way to overcome that?
BTW: thank you for info about "FrankenDebian". I think I put some "jessie" lines for some software installing not knowing exactly what I was doing.
Offline
#14 2016-11-13 21:48:18
- Head_on_a_Stick
- Member
- From: London
- Registered: 2015-09-29
- Posts: 9,093
- Website
Re: [SOLVED] A start job is running for network manager 1m 30sec
sudo systemctl disable network-manager.serviceMakes nice 8 sek boot time. Unfortunately no network available and I have to manually:
sudo service network-manager start
All that command does is run `systemctl start network-manager.service` via a wrapper script and, that being the case, I think that you should re-enable the .service again and put up with the delay.
Any simple way to overcome that?
You could disable NetworkManager entirely and use the native Debian ifupdown system instead:
https://wiki.debian.org/NetworkConfigur … _Interface
https://wiki.debian.org/WiFi/HowToUse#W … d_WPA2-PSK
I think I put some "jessie" lines for some software installing not knowing exactly what I was doing.
You have it the wrong way around, BunsenLabs is based on Debian jessie and should have those lines -- adding stretch repositories to a jessie system causes breakage and the only way to proceed at that point is to either reinstall (restore from backup, ideally) or to remove the jessie lines and `dist-upgrade` to a development branch and accept that the system may then break at any time without warning.
Offline
#15 2016-11-13 22:11:18
- hap
- Member
- Registered: 2016-11-12
- Posts: 6
Re: [SOLVED] A start job is running for network manager 1m 30sec
I think that you should re-enable the .service again and put up with the delay.
How to do that?
I see I was fighting with /etc/network/interfaces when I experienced boot delay problem:
# source /etc/network/interfaces.d/* (boot delayed - testing 07/09/2016 by me)
# The loopback network interface
# changed from "auto lo" (boot delayed - testing 16/09/2016 by me)
allow-hotplug lo
iface lo inet loopbackAll jessie commented out. Is /etc/apt/sources.list correct now? (I see I added 2 lines in Jan/2016) :
# deb cdrom:[Debian GNU/Linux 8 _Jessie_ - Official Snapshot amd64 LIVE/INSTALL Binary 20150711-01:57]/ jessie contrib main non-free
# generated by debian source list generator
deb http://ftp.pl.debian.org/debian/ testing non-free contrib main
deb-src http://ftp.pl.debian.org/debian/ testing non-free contrib main
# all jessie lines commented out (11/2016 by me)
# deb http://ftp.debian.org/debian/ jessie-updates non-free contrib main
# deb-src http://ftp.debian.org/debian/ jessie-updates main contrib non-free
# added 2 lines (01/2016 by me)
# deb http://ftp.debian.org/debian/ jessie non-free contrib main
# deb-src http://ftp.debian.org/debian/ jessie main contrib non-free
# deb http://security.debian.org/ jessie/updates non-free contrib main
# deb-src http://security.debian.org/ jessie/updates non-free contrib mainOffline
#16 2016-11-13 22:19:11
- damo
- ....moderator....
- Registered: 2015-08-20
- Posts: 6,734
Re: [SOLVED] A start job is running for network manager 1m 30sec
Head_on_a_Stick wrote:I think that you should re-enable the .service again and put up with the delay.
How to do that?
sudo systemctl enable network-manager.serviceAlso, regarding testing, you should consider looking at how to use apt-listbugs, and how to hold packages before you next do an upgrade 
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
#17 2016-11-13 22:21:00
- Head_on_a_Stick
- Member
- From: London
- Registered: 2015-09-29
- Posts: 9,093
- Website
Re: [SOLVED] A start job is running for network manager 1m 30sec
Head_on_a_Stick wrote:I think that you should re-enable the .service again and put up with the delay.
How to do that?
sudo systemctl enable network-manager.serviceEDIT: ninja'd by damo...
# source /etc/network/interfaces.d/* (boot delayed - testing 07/09/2016 by me)
Which files are present in /etc/network/interfaces.d/?
That directory is empty in a stock BL system.
All jessie commented out. Is /etc/apt/sources.list correct now?
Only if you want to use Debian testing.
I do not recommend tracking Debian testing unless you are OK with your machine breaking randomly for no apparent reason and are prepared to invest significant time and effort into keeping it usable on a day-to-day basis.
Last edited by Head_on_a_Stick (2016-11-13 22:21:22)
Offline
#18 2016-11-13 23:32:32
- hap
- Member
- Registered: 2016-11-12
- Posts: 6
Re: [SOLVED] A start job is running for network manager 1m 30sec
How to do that?Actually I wanted to ask: "Is it possible to start network-manager with a delay as it seems to start properly after booting".
Which files are present in /etc/network/interfaces.d/?
It's empty.
I don't mind investing time due to Debian testing - I consider it as a learning opportunity.
ls /etc/network gives additional dir's: if-down.d, if-post-down.d, if-pre-up.d if-up.d
I think it left after I was testing ifupdown according these or similar links as suggested in post #14.
Offline
#19 2016-11-14 08:23:52
- Head_on_a_Stick
- Member
- From: London
- Registered: 2015-09-29
- Posts: 9,093
- Website
Re: [SOLVED] A start job is running for network manager 1m 30sec
Is it possible to start network-manager with a delay as it seems to start properly after booting
Hmmm, good question.
Try:
sudo SYSTEMD_EDITOR=vim systemctl edit network-manager.service(If you don't specify vim then nano is used 
)
Then add these lines to the drop-in snippet:
[Service]
ExecStartPre=/bin/sleep 60This should add a 1 minute delay.
I'm not sure if the BL version of systemd supports the `systemctl edit` option ha! you is on sid 
... , if not then simply create the drop-in file manually:
sudo mkdir -p /etc/systemd/network-manager.service.d
sudo tee /etc/systemd/network-manager.service.d/delay.conf << EOF
[Service]
ExecStartPre=/bin/sleep 60
EOFTo reverse the effects, delete the directory at /etc/systemd/network-manager.service.d (and all of the contents, obviously).
EDIT: there is also the option of reducing the 90 second timeout with
sudo tee /etc/systemd/network-manager.service.d/reducedelay.conf << EOF
[Service]
TimeoutStartSec=15
EOFOr globally in /etc/systemd/system.conf
TimeoutStartSec=15More ideas here:
http://unix.stackexchange.com/questions … -systemctl
Last edited by Head_on_a_Stick (2016-11-14 08:37:26)
Offline
#20 2016-11-15 16:44:49
- hap
- Member
- Registered: 2016-11-12
- Posts: 6
Re: [SOLVED] A start job is running for network manager 1m 30sec
(If you don't specify vim then nano is used
Sounds like invitation to editor flame war.
Or globally in /etc/systemd/system.conf
TimeoutStartSec=15
I believe I changed a different file with Timeout parameter in accordance to advices given to someone on a different forum. With no results.
And finally:
sudo SYSTEMD_EDITOR=vim systemctl edit network-manager.serviceand
[Service]
ExecStartPre=/bin/sleep 60... works!
Thank you for your help. I've seen that some users had the same problem and this thread can be helpful.
Last thing: as I understand start of network-manager.service is delayed for 60 sec. Why then network and Aplet NetworkManager starts immediately? Wasn't it a problem of doubling network start?
Offline