Page 1 of 1

Failed to start LSB: Bring up/down networking

PostPosted: Dec 7th, '13, 08:53
by niemand
I'm getting this FAILED message at log-out or shut down:
Code: Select all
[  OK  ] Started Network Manager.
         Starting LSB: Bring up/down networking...
         Starting Network Manager Wait Online...
[FAILED] Failed to start LSB: Bring up/down networking.
See 'systemctl status network.service' for details.
         Starting LSB: Wait for the hotplugged network to be up...

The message flashes by too quickly to read.

Re: Failed to start LSB: Bring up/down networking

PostPosted: Dec 7th, '13, 09:25
by doktor5000
And, what impact is there to this message?

Re: Failed to start LSB: Bring up/down networking

PostPosted: Dec 7th, '13, 09:33
by niemand
doktor5000 wrote:And, what impact is there to this message?

Nothing noticeable thus far.
Am curious whether it is something that needs to be fixed.

Re: Failed to start LSB: Bring up/down networking

PostPosted: Dec 7th, '13, 09:53
by doktor5000
Well, check the state of the LSB services:

Code: Select all
systemctl list-units | grep -i lsb
hddtemp.service           loaded active running       LSB: Information about hard drives' temperature
mandi.service             loaded active running       LSB: Network monitoring daemon
microcode_ctl.service     loaded active exited        LSB: Update the Intel / AMD CPU microcode
msec.service              loaded active exited        LSB: Enables MSEC security policy on boot
network-up.service        loaded active exited        LSB: Wait for the hotplugged network to be up
network.service           loaded failed failed        LSB: Bring up/down networking
partmon.service           loaded active exited        LSB: Checks if a partition is close to full up
resolvconf.service        loaded active exited        LSB: Nameserver information manager
virtualbox.service        loaded active exited        LSB: VirtualBox Linux kernel module
wine.service              loaded active exited        LSB: Allow users to run Windows(tm) applications


In particular, it's probably the network.service:

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 Tue, 2013-12-03 16:27:54 CET; 3 days ago
         Process: 1210 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
          CGroup: name=systemd:/system/network.service
                  ├ 1401 /usr/sbin/wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf -D wext
                  ├ 1403 /sbin/ifplugd -I -b -i wlan0
                  └ 4094 dhclient -1 -q -lf /var/lib/dhclient/dhclient--wlan0.lease -pf /var/run/dhclient...

Dec 04 19:26:51 Mageia3 ifplugd(wlan0)[1403]: Link beat lost.
Dec 04 19:26:57 Mageia3 ifplugd(wlan0)[1403]: Executing '/etc/ifplugd/ifplugd.action wlan0 down'.
Dec 04 19:26:57 Mageia3 ifplugd(wlan0)[1403]: Program executed successfully.
Dec 04 19:27:15 Mageia3 ifplugd(wlan0)[1403]: Link beat detected.
Dec 04 19:27:16 Mageia3 ifplugd(wlan0)[1403]: Executing '/etc/ifplugd/ifplugd.action wlan0 up'.
Dec 04 19:27:17 Mageia3 dhclient[3974]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Dec 04 19:27:17 Mageia3 dhclient[3974]: DHCPACK from 192.168.178.1
Dec 04 19:27:18 Mageia3 dhclient[3974]: bound to 192.168.178.20 -- renewal in 340019 seconds.
Dec 04 19:27:18 Mageia3 ifplugd(wlan0)[1403]: client: Determining IP information for wlan0... done.
Dec 04 19:27:18 Mageia3 ifplugd(wlan0)[1403]: Program executed successfully.

Re: Failed to start LSB: Bring up/down networking

PostPosted: Dec 7th, '13, 09:59
by doktor5000