[Mageia-dev] systemd network.service issues

Barry Jackson zen25000 at zen.co.uk
Fri Mar 16 13:12:32 CET 2012


On 16/03/12 03:45, Anssi Hannula wrote:
> Hi all!
>
> So, I've just upgraded my home server to mga2/cauldron.
>
> Something seems fishy in the network.service handling, systemd thinks it
> has failed:
>
> # 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, 16 Mar 2012
> 05:25:09 +0200; 11min ago
>            CGroup: name=systemd:/system/network.service
>                    ├ 4679 /sbin/ifplugd -I -b -i eth0
>                    ├ 4723 /sbin/ifplugd -I -b -i eth1
>                    └ 5372 /sbin/dhclient -q -lf
> /var/lib/dhcp/dhclient-eth0.leases -pf /var/run/dhclient-eth0.pid -cf
> /etc/dhclient-eth0.conf...
>
> Mar 16 05:25:09 delta.onse.fi ifplugd(eth1)[4723]: Using detection mode:
> SIOCETHTOOL
> Mar 16 05:25:09 delta.onse.fi ifplugd(eth1)[4723]: Initialization
> complete, link beat not detected.
> Mar 16 05:25:09 delta.onse.fi network[4397]: [161B blob data]
> Mar 16 05:25:09 delta.onse.fi network[4397]: [14B blob data]
> Mar 16 05:25:13 delta.onse.fi ifplugd(eth0)[4679]: Link beat detected.
> Mar 16 05:25:14 delta.onse.fi ifplugd(eth0)[4679]: Executing
> '/etc/ifplugd/ifplugd.action eth0 up'.
> Mar 16 05:25:15 delta.onse.fi dhclient[5312]: DHCPREQUEST on eth0 to
> 255.255.255.255 port 67
> Mar 16 05:25:15 delta.onse.fi dhclient[5312]: DHCPACK from 109.204.128.1
> Mar 16 05:25:15 delta.onse.fi ifplugd(eth0)[4679]: client: Determining
> IP information for eth0... done.
> Mar 16 05:25:15 delta.onse.fi ifplugd(eth0)[4679]: Program executed
> successfully.
>
>
> Trying to restart it I seem to hit other issues:
>
> # systemctl restart network.service
> Job failed. See system journal and 'systemctl status' 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 Fri, 16 Mar 2012
> 05:36:39 +0200; 3s ago
>           Process: 8027 ExecStart=/etc/rc.d/init.d/network start
> (code=exited, status=1/FAILURE)
>            CGroup: name=systemd:/system/network.service
>                    ├ 8195 /sbin/ifplugd -I -b -i eth0
>                    └ 8353 /sbin/dhclient -q -lf
> /var/lib/dhcp/dhclient-eth0.leases -pf /var/run/dhclient-eth0.pid -cf
> /etc/dhclient-eth0.conf...
>
> Mar 16 05:36:39 delta.onse.fi network[8027]: RTNETLINK answers: File exists
> Mar 16 05:36:39 delta.onse.fi network[8027]: RTNETLINK answers: File exists
> Mar 16 05:36:39 delta.onse.fi network[8027]: RTNETLINK answers: File exists
> Mar 16 05:36:39 delta.onse.fi network[8027]: RTNETLINK answers: File exists
> Mar 16 05:36:39 delta.onse.fi dhclient[8261]: DHCPREQUEST on eth0 to
> 255.255.255.255 port 67
> Mar 16 05:36:40 delta.onse.fi dhclient[8261]: DHCPACK from 109.204.128.1
> Mar 16 05:36:40 delta.onse.fi ifplugd(eth0)[8195]: client: Determining
> IP information for eth0...NETLINK: Error: File exists
> Mar 16 05:36:40 delta.onse.fi ifplugd(eth0)[8195]: client:  done.
> Mar 16 05:36:40 delta.onse.fi ifplugd(eth0)[8195]: client: NETLINK:
> Error: File exists
> Mar 16 05:36:40 delta.onse.fi ifplugd(eth0)[8195]: Program executed
> successfully.
>
> Any ideas? If not, I'll investigate this myself later.
>
>
> On a related note, I also got dropped to emergency console on first
> boot, not sure why was that (it didn't tell me the reason... maybe the
> reason was in another virtual console, but I didn't remember to check
> there at the time). I just exited the console and it continued to boot...
>
> I see the following in systemctl --failed:
>
> # systemctl --failed
> UNIT                         LOAD   ACTIVE SUB    JOB DESCRIPTION
> bootparamd.service           loaded ESC[1;31mfailed failedESC[0m
> SYSV: The bootparamd server allows older Sun workstations to net boot
> from Linux boxes. It (along with rarp) is rarely used anymore; bootp and
> dhcp have mostly replaced both of them.
> fedora-loadmodules.service   loaded ESC[1;31mfailed failedESC[0m
> Load legacy module configuration
> network.service              loaded ESC[1;31mfailed failedESC[0m
> LSB: Bring up/down networking
> systemd-modules-load.service loaded ESC[1;31mfailed failedESC[0m
> Load Kernel Modules
>

Not sure if its related, but I am seeing the same failures of 
fedora-loadmodules and systemd-modules-load, however the network comes 
up OK.

[root at zmhost baz]# systemctl status systemd-modules-load.service
systemd-modules-load.service - Load Kernel Modules
           Loaded: loaded 
(/lib/systemd/system/systemd-modules-load.service; static)
           Active: failed (Result: timeout) since Wed, 14 Mar 2012 
13:38:28 +0000; 1 day and 22h ago
         Main PID: 391
           CGroup: name=systemd:/system/systemd-modules-load.service

[root at zmhost baz]# systemctl status fedora-loadmodules.service
fedora-loadmodules.service - Load legacy module configuration
           Loaded: loaded 
(/lib/systemd/system/fedora-loadmodules.service; static)
           Active: failed (Result: exit-code) since Wed, 14 Mar 2012 
13:38:28 +0000; 1 day and 22h ago
         Main PID: 386 (code=exited, status=1/FAILURE)
           CGroup: name=systemd:/system/fedora-loadmodules.service

[root at zmhost baz]# systemctl status network.service
network.service - LSB: Bring up/down networking
           Loaded: loaded (/etc/rc.d/init.d/network)
           Active: active (running) since Wed, 14 Mar 2012 13:38:32 
+0000; 1 day and 22h ago
           CGroup: name=systemd:/system/network.service
                   └ 1336 /sbin/ifplugd -I -b -i eth0

These time out before boot can complete.
http://mtf.no-ip.co.uk/boot14032012.svg


More information about the Mageia-dev mailing list