Page 1 of 1

[SOLVED] How do you restart the network?

PostPosted: Jul 5th, '13, 07:46
by mark9117
I'm getting frustrated and annoyed. Something that used to be so simple has gotten far to complicated.

I am trying to get my vpn to connect. It just stopped yesterday and now it simply will not connect. The whole situation is being complicated by the fact that I can't simply restart the network service!

I'm trying to restart it with the net_applet and not only is it having no effect, but everytime I try to turn disconnect the network, the Net_appliet in the tray crashes and I have to restart it.

Beyond that, what was wrong with "service network restart"? Why did we have to go to "systemctl restart network.service" which doesn't work either?!

Code: Select all
# systemctl restart network.service
Job for network.service failed. See 'systemctl status network.service' and 'journalctl -n' for details.

# systemctl status network.service
network.service - LSB: Bring up/down networking
          Loaded: loaded (/etc/rc.d/init.d/network)
          Active: failed (Result: exit-code) since Thu, 2013-07-04 23:42:35 MDT; 4s ago
         Process: 13646 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
          CGroup: name=systemd:/system/network.service
                  └ 1243 /sbin/ifplugd -I -b -i eth0

Jul 04 23:42:35 spike network[13646]: RTNETLINK answers: File exists
Jul 04 23:42:35 spike network[13646]: RTNETLINK answers: File exists
Jul 04 23:42:35 spike network[13646]: RTNETLINK answers: File exists
Jul 04 23:42:35 spike network[13646]: RTNETLINK answers: File exists
Jul 04 23:42:35 spike network[13646]: RTNETLINK answers: File exists
Jul 04 23:42:35 spike network[13646]: RTNETLINK answers: File exists
Jul 04 23:42:35 spike network[13646]: RTNETLINK answers: File exists
Jul 04 23:42:35 spike network[13646]: RTNETLINK answers: File exists
Jul 04 23:42:35 spike systemd[1]: Failed to start LSB: Bring up/down networking.
Jul 04 23:42:35 spike systemd[1]: Unit network.service entered failed state


Why is this failing and what do I have to do to troubleshoot it? I really do not find this helpful:

Code: Select all
# journalctl -n
-- Logs begin at Tue, 2013-05-28 17:26:53 MDT, end at Thu, 2013-07-04 23:44:05 MDT. --
Jul 04 23:42:35 spike network[13646]: RTNETLINK answers: File exists
Jul 04 23:42:35 spike network[13646]: RTNETLINK answers: File exists
Jul 04 23:42:35 spike network[13646]: RTNETLINK answers: File exists
Jul 04 23:42:35 spike network[13646]: RTNETLINK answers: File exists
Jul 04 23:42:35 spike systemd[1]: network.service: control process exited, code=exited status=1
Jul 04 23:42:35 spike systemd[1]: Failed to start LSB: Bring up/down networking.
Jul 04 23:42:35 spike systemd[1]: Unit network.service entered failed state
Jul 04 23:44:01 spike crond[13860]: pam_tcb(crond:session): Session opened for root by root(uid=0)
Jul 04 23:44:01 spike CROND[13861]: (root) CMD (/usr/local/bin/Xpwall.sh >/dev/null 2>&1)
Jul 04 23:44:05 spike CROND[13860]: pam_tcb(crond:session): Session closed for root


How about you? Can you point me in a reasonable direction on this?


Mark

Re: How do you restart the network?

PostPosted: Jul 5th, '13, 07:54
by isadora
~topic moved by moderator

Re: How do you restart the network?

PostPosted: Jul 5th, '13, 09:12
by mark9117
And more to the point in all this, why did my vpn (opevpn) stop creating a tun0 interface device?

Re: How do you restart the network?

PostPosted: Jul 5th, '13, 16:27
by digigold
mark9117 wrote:..what was wrong with "service network restart"? Why did we have to go to "systemctl restart network.service"

Because things are moving away from sysVinit to other init daemons like systemd (uses systemctl) or Upstart. systemd was developed by RedHat and Upstart by Canonical. systemd is actually much more robust than sysVinit which is limited by runlevels. systemd does take longer to learn, but you can do a lot more with it. (such as unit groups etc.)

See your other post for my comments about your vpn issue.

Re: How do you restart the network?

PostPosted: Jul 5th, '13, 19:27
by mark9117
So, how do you restart the network?

systemctl restart network.service (and various permutations thereof) does not work.

Attempting to disconnect the eth0 intervace via the net_applet does not work either.

Respectfully, WTF?


Mark

Re: How do you restart the network?

PostPosted: Jul 6th, '13, 01:31
by mark9117
Just thought I'd offer this:

Code: Select all
# systemctl status network.service
network.service - LSB: Bring up/down networking
          Loaded: loaded (/etc/rc.d/init.d/network)
          Active: failed (Result: exit-code) since Fri, 2013-07-05 17:29:09 MDT; 17s ago
         Process: 9250 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
          CGroup: name=systemd:/system/network.service

Jul 05 17:29:09 spike network[9250]: RTNETLINK answers: File exists
Jul 05 17:29:09 spike network[9250]: RTNETLINK answers: File exists
Jul 05 17:29:09 spike network[9250]: RTNETLINK answers: File exists
Jul 05 17:29:09 spike network[9250]: RTNETLINK answers: File exists
Jul 05 17:29:09 spike network[9250]: RTNETLINK answers: File exists
Jul 05 17:29:09 spike network[9250]: RTNETLINK answers: File exists
Jul 05 17:29:09 spike network[9250]: RTNETLINK answers: File exists
Jul 05 17:29:09 spike network[9250]: RTNETLINK answers: File exists
Jul 05 17:29:09 spike systemd[1]: Failed to start LSB: Bring up/down networking.
Jul 05 17:29:09 spike systemd[1]: Unit network.service entered failed state


No idea what systemctl is trying to tell me.

Mark

Re: How do you restart the network?

PostPosted: Jul 6th, '13, 17:35
by doktor5000
Probably due to your vpn connection or something related. Works perfectly fine here, as expected:

Code: Select all
[doktor5000@Mageia3 ~]$ sudo systemctl status network.service
network.service - LSB: Bring up/down networking
          Loaded: loaded (/etc/rc.d/init.d/network)
          Active: active (running) since Thu, 2013-06-27 02:01:23 CEST; 1 weeks and 2 days ago
          CGroup: name=systemd:/system/network.service
                  ├ 1229 /usr/sbin/wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf -D wext
                  ├ 1231 /sbin/ifplugd -I -b -i wlan0
                  └ 1840 dhclient -1 -q -lf /var/lib/dhclient/dhclient--wlan0.lease -pf /var/run/dhclient-wlan0.pid wlan0

Jul 01 07:07:03 Mageia3 ifplugd(wlan0)[1231]: Executing '/etc/ifplugd/ifplugd.action wlan0 up'.
Jul 01 07:07:04 Mageia3 dhclient[1734]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 01 07:07:04 Mageia3 dhclient[1734]: DHCPACK from 192.168.178.1
Jul 01 07:07:04 Mageia3 dhclient[1734]: bound to 192.168.178.20 -- renewal in 368634 seconds.
Jul 01 07:07:04 Mageia3 ifplugd(wlan0)[1231]: client: Determining IP information for wlan0... done.
Jul 01 07:07:04 Mageia3 ifplugd(wlan0)[1231]: client:  [  OK  ]
Jul 01 07:07:04 Mageia3 ifplugd(wlan0)[1231]: Program executed successfully.
Jul 05 13:30:58 Mageia3 dhclient[1840]: DHCPREQUEST on wlan0 to 192.168.178.1 port 67
Jul 05 13:30:58 Mageia3 dhclient[1840]: DHCPACK from 192.168.178.1
Jul 05 13:30:58 Mageia3 dhclient[1840]: bound to 192.168.178.20 -- renewal in 333414 seconds.

Code: Select all
[doktor5000@Mageia3 ~]$ sudo systemctl restart network.service

Code: Select all
[doktor5000@Mageia3 ~]$ sudo systemctl status network.service
network.service - LSB: Bring up/down networking
          Loaded: loaded (/etc/rc.d/init.d/network)
          Active: active (running) since Sat, 2013-07-06 17:33:37 CEST; 47s ago
         Process: 30816 ExecStop=/etc/rc.d/init.d/network stop (code=exited, status=0/SUCCESS)
         Process: 31209 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/network.service
                  ├ 31399 /usr/sbin/wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf -D wext
                  ├ 31401 /sbin/ifplugd -I -b -i wlan0
                  └ 31579 dhclient -1 -q -lf /var/lib/dhclient/dhclient--wlan0.lease -pf /var/run/dhclient-wlan0.pid wlan0

Jul 06 17:33:37 Mageia3 ifplugd(wlan0)[31401]: Initialization complete, link beat not detected.                                                                         
Jul 06 17:33:37 Mageia3 network[31209]: [  OK  ]                                                                                                                       
Jul 06 17:33:37 Mageia3 systemd[1]: Started LSB: Bring up/down networking.                                                                                             
Jul 06 17:33:38 Mageia3 ifplugd(wlan0)[31401]: Link beat detected.                                                                                                     
Jul 06 17:33:39 Mageia3 ifplugd(wlan0)[31401]: Executing '/etc/ifplugd/ifplugd.action wlan0 up'.
Jul 06 17:33:40 Mageia3 dhclient[31475]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jul 06 17:33:40 Mageia3 dhclient[31475]: DHCPACK from 192.168.178.1
Jul 06 17:33:40 Mageia3 ifplugd(wlan0)[31401]: client: Determining IP information for wlan0... done.
Jul 06 17:33:40 Mageia3 ifplugd(wlan0)[31401]: client:  [  OK  ]
Jul 06 17:33:40 Mageia3 ifplugd(wlan0)[31401]: Program executed successfully.

Re: How do you restart the network?

PostPosted: Jul 12th, '13, 19:34
by mark9117
I'm marking this one solved. I think the issue was related to the borked up network vpn connection.