networkmanager won't start, nm-applet visible

ham bone · 10-31-2018, 02:32 AM

Greetings all and thanks for reading.
I have the folllowing error:

Code:

"Job for NetworkManager.service failed. See 'systemctl status NetworkManager.service' and 'journalctl -xn' for details."

It might have been

Code:

journal -xe

, not

Code:

 'journalctl -xn

,' I am not logged into that systm for obvious reasons. I will gladly post any code required. System in question: Openbox3 tint2, standard quadcore, radeon 5000 series, boot from .xinitrc, Arch Linux, kernel 4.18.

Dhcpcd was removed and replaced with dhclient. However, I've done this before without this problem occurring. nm-applet does appear courtesy of openbox auto start. Everything should be working, and it was until a few updates ago.
Again, thanks for reading.

ondoho · 10-31-2018, 03:09 AM

Quote:

Originally Posted by ham bone

I am not logged into that systm for obvious reasons. I will gladly post any code required.

please do.
the commands are in the output you quoted.

ham bone · 11-02-2018, 01:39 AM

Quote:

Originally Posted by ondoho

please do.
the commands are in the output you quoted.

I apologize for the tardiness of my response.

What I did not provide in my original post is that the user account had been added to groupnetwork.
The systemctl enable and systemctl start network manager were the commands used and a restart had been done.
Here is the output of systemctl start networkmanager.service:

Code:

systemctl status NetworkManager.service
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
  Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
           └─NetworkManager-ovs.conf
   Active: failed (Result: exit-code) since Fri 2018-11-02 05:57:13 UTC; 1min 1s ago
     Docs: man:NetworkManager(8)
  Process: 1175 ExecStart=/usr/bin/NetworkManager --no-daemon (code=exited, status=1/FAILURE)
 Main PID: 1175 (code=exited, status=1/FAILURE)

Nov 02 05:57:13 dfknox23 systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling >
Nov 02 05:57:13 dfknox23 systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at >
Nov 02 05:57:13 dfknox23 systemd[1]: Stopped Network Manager.
Nov 02 05:57:13 dfknox23 systemd[1]: NetworkManager.service: Start request repeated too quickly.
Nov 02 05:57:13 dfknox23 systemd[1]: NetworkManager.service: Failed with result 'exit-code'.
Nov 02 05:57:13 dfknox23 systemd[1]: Failed to start Network Manager.

Here is the output of journalctl -xe

Code:

Nov 02 05:36:34 dfknox23 kernel: [UFW AUDIT] IN=enp1s0 OUT= MAC=30:b0:59:6f:9h:74:f0:3f:c7:1e:f5:88:03:00 >
Nov 02 05:36:43 dfknox23 kernel: [UFW AUDIT] IN= OUT=enp1s0 SRC=192.168.1.67 DST=72.21.91.29 LEN=52 TOS=0x>
Nov 02 05:36:55 dfknox23 kernel: [UFW AUDIT] IN= OUT=enp1s0 SRC=192.168.1.67 DST=34.209.9.71 LEN=52 TOS=0x>
Nov 02 05:36:55 dfknox23 kernel: [UFW AUDIT] IN=enp1s0 OUT= MAC=30:b0:59:6f:9h:74:f0:3f:c7:1e:f5:88:03:00 >
Nov 02 05:37:02 dfknox23 kernel: [UFW ALLOW] IN= OUT=enp1s0 SRC=192.168.1.67 DST=34.210.126.96 LEN=60 TOS=>
Nov 02 05:37:02 dfknox23 kernel: [UFW ALLOW] IN= OUT=enp1s0 SRC=192.168.1.67 DST=72.21.91.29 LEN=60 TOS=0x>
Nov 02 05:37:22 dfknox23 kernel: [UFW AUDIT] IN= OUT=enp1s0 SRC=192.168.1.67 DST=72.21.91.29 LEN=52 TOS=0x>
Nov 02 05:37:22 dfknox23 kernel: [UFW AUDIT] IN=enp1s0 OUT= MAC=30:b0:59:6f:9h:74:f0:3f:c7:1e:f5:88:03:00 >
Nov 02 05:37:42 dfknox23 kernel: [UFW AUDIT] IN= OUT=enp1s0 SRC=192.168.1.67 DST=72.21.91.29 LEN=52 TOS=0x>
Nov 02 05:37:42 dfknox23 kernel: [UFW AUDIT] IN=enp1s0 OUT= MAC=30:b0:59:6f:9h:74:f0:3f:c7:1e:f5:88:03:00 >
Nov 02 05:38:03 dfknox23 kernel: [UFW AUDIT] IN= OUT=enp1s0 SRC=192.168.1.67 DST=72.21.91.29 LEN=52 TOS=0x>
Nov 02 05:38:03 dfknox23 kernel: [UFW AUDIT] IN=enp1s0 OUT= MAC=30:b0:59:6f:9h:74:f0:3f:c7:1e:f5:88:03:00 >
Nov 02 05:38:23 dfknox23 kernel: [UFW AUDIT] IN= OUT=enp1s0 SRC=192.168.1.67 DST=72.21.91.29 LEN=52 TOS=0x>
Nov 02 05:38:23 dfknox23 kernel: [UFW AUDIT] IN=enp1s0 OUT= MAC=30:b0:59:6f:9h:74:f0:3f:c7:1e:f5:88:03:00 >
Nov 02 05:38:32 dfknox23 dhclient[452]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 8
Nov 02 05:38:32 dfknox23 dhclient[452]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 8
Nov 02 05:38:40 dfknox23 dhclient[452]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 10
Nov 02 05:38:40 dfknox23 dhclient[452]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 10
Nov 02 05:38:41 dfknox23 kernel: [UFW AUDIT] IN=enp1s0 OUT= MAC=30:b0:59:6f:9h:74:f0:3f:c7:1e:f5:88:03:00 >
Nov 02 05:38:41 dfknox23 kernel: [UFW AUDIT] IN= OUT=enp1s0 SRC=192.168.1.67 DST=52.32.209.197 LEN=87 TOS=>
Nov 02 05:38:50 dfknox23 dhclient[452]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 16
Nov 02 05:38:50 dfknox23 dhclient[452]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 16
Nov 02 05:38:55 dfknox23 kernel: [UFW AUDIT] IN= OUT=enp1s0 SRC=192.168.1.67 DST=34.210.126.96 LEN=52 TOS=>
Nov 02 05:38:55 dfknox23 kernel: [UFW AUDIT] IN=enp1s0 OUT= MAC=30:b0:59:6f:9h:74:f0:3f:c7:1e:f5:88:03:00 >
Nov 02 05:39:06 dfknox23 dhclient[452]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 12
Nov 02 05:39:06 dfknox23 dhclient[452]: DHCPDISCOVER on wlo1 to 255.255.255.255 port 67 interval 12

Thanks for reading.

ondoho · 11-02-2018, 02:47 AM

Quote:

Originally Posted by ham bone

Here is the output of systemctl start networkmanager.service:

Code:

Start request repeated too quickly.

this usually means that there is some networkmanager specific error that systemd did not catch.
yep, that's vague.
i don't use networkmanager; you will have to dig deeper.
could be something very simple in the end.

Quote:

Here is the output of journalctl -xe

it should've been -xn

ham bone · 11-04-2018, 11:48 PM

I uninstalled networkmanager and dhclient, to include config files. Installed dhcpcd and did the systemctl start/enable dhcpcd on the wired interface, which now works. I do not know if wpa_supplicant should be enabled. However, it is enabled on my system, wpa_supplicant@.service. As this is Arch Linux, there is a wiki. However, I'd call it cryptic and unhelpful when compared to the documentation from more than six years ago, hence my reason for posting here.

Although I can now see all wifi signals in nm-applet, the current problem now is 'temporary failure in name resolution, your network may be down.' This only applies to wifi so progress has been made. Incidentally, networking is functioning under the xfce4 install on another system.

Thanks for reading.

ondoho · 11-05-2018, 01:23 AM

well that's a little confusing.
how can you still be using nm-applet when you uninstalled networkmanager???

fwiw i always found archwiki extremely helpful.

anyhow, on your archlinux system, would you like to show us how the network, esp. wifi, is now configured, and which software actually handles it?