NetworkManager doesn't start automatically on boot

[limasxgoesto0]

My network manager recently stopped launching on boot and I couldn't even connect with ethernet. After digging around I found I can fix this at the terminal by putting in:

sudo systemctl restart NetworkManager.service

However, I have to keep doing this each time I restart, and it's annoying to have to keep doing that. Is there any way to fix this? I also tried putting the above command in gnome-session-properties to try to run it on boot with no success.

[boydrice]

Hi please check this page http://fedoraproject.org/wiki/Systemd

To enable a service to be started on boot:
systemctl enable foo.service

[limasxgoesto0]

Sorry for not getting back to you sooner

So I tried running sudo systemctl enable NetworkManager.service at the terminal, and it actually didn't even let me auto-complete that so it doesn't seem to be a valid option. It did auto-complete to NetworkManager-wait-online.service, and I'm not sure if that will do anything.

I tried running it before and after restarting NetworkManager.service and nothing came up.

If I can even just find a way to run systemctl restart NetworkManager.service at bootup (because apparently inputting that to gnome-session-properties doesn't work) or just any temporary solution become permanent, that'd be a great improvement.

[alexeik]

I also have this issue. I have Fedora 16 installed:

[alexei@localhost ~]$ uname -a
Linux localhost.localdomain 3.6.6-1.fc16.x86_64 #1 SMP Mon Nov 5 16:56:43 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

I solveed it (temp) by running a script when I first log in into my user:
"
systemctl |grep NetworkManager
sudo systemctl restart NetworkManager.service
systemctl |grep NetworkManager
"
It responds:

[alexei@localhost ~]$ ./ff.sh
NetworkManager.service loaded active running Network Manager
[sudo] password for alexei:
NetworkManager.service loaded active running Network Manager

last time i did the following:

1. I login to user
2. wait for a while
3. insert a wifi usb dongle
4. wait for a while
5. run this ff.sh script

Then I collected dmesg and did a timing:

93.416713 - before point 3
209.798343 - before point 5
and the rest

Maybe it helps to diagnose the issue.

Meanwhile I have workaround - I run that ff.sh script.

[marko]

Originally Posted by limasxgoesto0

Sorry for not getting back to you sooner

So I tried running sudo systemctl enable NetworkManager.service at the terminal, and it actually didn't even let me auto-complete that so it doesn't seem to be a valid option. It did auto-complete to NetworkManager-wait-online.service, and I'm not sure if that will do anything.

I tried running it before and after restarting NetworkManager.service and nothing came up.

If I can even just find a way to run systemctl restart NetworkManager.service at bootup (because apparently inputting that to gnome-session-properties doesn't work) or just any temporary solution become permanent, that'd be a great improvement.

I've noticed recently that systemctl will not auto-complete some commands which are correct and valid commands. I'm not sure why autocomplete doesn't work for it but I can assure you that this is command below is correct and needs to be run for your NetworkManager to run at boot:

systemctl enable NetworkManager.service

go ahead and run it, then try running status:

systemctl status NetworkManager.service

if that worked, you should see something similar to this (note the bolded "enabled", the effect of running "enable" should make "enabled" show in the status output, note I substituted some # signs where
you will have different digits than me for pids):

NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: active (running) since Thu, 15 Nov 2012 12:12:36 -0500; 0h 01min ago
Main PID: ### (NetworkManager)
CGroup: name=systemd:/system/NetworkManager.service
├ ### /usr/sbin/NetworkManager --no-daemon
└ ### /sbin/dhclient -d -4 -sf /usr/libexec/nm-dhcp-client.action -pf /var/run/dhclient-wlan0.pid -lf /var/lib/dhclient/dhclient-59...

[limasxgoesto0]

...I forgot about this again. I apologize to everyone who was waiting for feedback.

Originally Posted by alexeik

I also have this issue. I have Fedora 16 installed:

[alexei@localhost ~]$ uname -a
Linux localhost.localdomain 3.6.6-1.fc16.x86_64 #1 SMP Mon Nov 5 16:56:43 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

I solveed it (temp) by running a script when I first log in into my user:
"
systemctl |grep NetworkManager
sudo systemctl restart NetworkManager.service
systemctl |grep NetworkManager
"
It responds:

[alexei@localhost ~]$ ./ff.sh
NetworkManager.service loaded active running Network Manager
[sudo] password for alexei:
NetworkManager.service loaded active running Network Manager

last time i did the following:

1. I login to user
2. wait for a while
3. insert a wifi usb dongle
4. wait for a while
5. run this ff.sh script

Then I collected dmesg and did a timing:

93.416713 - before point 3
209.798343 - before point 5
and the rest

Maybe it helps to diagnose the issue.

Meanwhile I have workaround - I run that ff.sh script.

Sorry, what is the ff.sh script? If it's in a USB Wifi stick, I don't have one.

Running systemctl |grep NetworkManager before and after restarting NetworkManager.service gives me this:

NetworkManager.service loaded active running Network Manager


So, it's running even before restarting, I just don't see the icon that lets me connect to different connections until I restart.

Originally Posted by marko

I've noticed recently that systemctl will not auto-complete some commands which are correct and valid commands. I'm not sure why autocomplete doesn't work for it but I can assure you that this is command below is correct and needs to be run for your NetworkManager to run at boot:
go ahead and run it, then try running status:
if that worked, you should see something similar to this (note the bolded "enabled", the effect of running "enable" should make "enabled" show in the status output, note I substituted some # signs where
you will have different digits than me for pids):

I ran systemctl enable, and on bootup I see this before running restart:

Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled)
Active: active (running) since Wed, 21 Nov 2012 12:34:20 -0800; 1min 10s ago
Main PID: 1030 (NetworkManager)
CGroup: name=systemd:/system/NetworkManager.service
├ 1030 /usr/sbin/NetworkManager --no-daemon
└ 1508 /sbin/dhclient -d -4 -sf /usr/libexec/nm-dhcp-clie...

which seems consistent with what you provided. I think the process is starting but I just don't see the icon.

[alexeik]

Sorry, I was not clear enough 8(
>cat ff.sh

systemctl |grep NetworkManager
sudo systemctl restart NetworkManager.service
systemctl |grep NetworkManager

>

[limasxgoesto0]

Ah, that's what you meant.

Yeah I've been running the restart service command at each bootup, I'm just hoping to find something more permanent.

[alexeik]

The strange thing is that if I do not run that script, I still have an access to internet. And everything looks almost OK. But if I want to do "Software update" - I have nothing. "Software update" does not work without this script.