Bug#866531: systemd: networking.service fails with virtual interfaces

Michael Biebl biebl at debian.org
Thu Jun 29 23:13:27 BST 2017


Control: severity -1 important
Control: reassign -1 ifupdown

Am 29.06.2017 um 23:46 schrieb BERTRAND Joël:
> Package: systemd
> Version: 233-9
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
> 
> I have seen for a long time several issues with systemd. All of these issues 
> seem to come from target networking.service.
> 
> Indeed, systemctl status networking.service returns:
> networking.service - Raise network interfaces
> Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor
> preset: enabled)
> Active: failed (Result: exit-code) since Thu 2017-06-29 23:33:40 CEST; 16s ago
> ...
> juin 29 23:33:39 rayleigh ifup[16031]: RTNETLINK answers: File exists
> juin 29 23:33:39 rayleigh ifup[16031]: ifup: failed to bring up eth1:4
> juin 29 23:33:39 rayleigh ifup[16031]: RTNETLINK answers: File exists
> juin 29 23:33:39 rayleigh ifup[16031]: ifup: failed to bring up eth1:5
> juin 29 23:33:39 rayleigh ifup[16031]: RTNETLINK answers: File exists
> juin 29 23:33:39 rayleigh ifup[16031]: ifup: failed to bring up eth1:6
> juin 29 23:33:40 rayleigh systemd[1]: networking.service: Main process exited,
> code=exited, status=1/FAILURE
> juin 29 23:33:40 rayleigh systemd[1]: Failed to start Raise network interfaces.
> juin 29 23:33:40 rayleigh systemd[1]: networking.service: Unit entered failed
> state.
> juin 29 23:33:40 rayleigh systemd[1]: networking.service: Failed with result
> 'exit-code'.
> 
> This target calls /sbin/ifup -a --read-environment that returns
> RTNETLINK answers: File exists
> ifup: failed to bring up eth1:1
> RTNETLINK answers: File exists
> ifup: failed to bring up eth1:2
> RTNETLINK answers: File exists
> ifup: failed to bring up eth1:3
> RTNETLINK answers: File exists
> ifup: failed to bring up eth1:4
> RTNETLINK answers: File exists
> ifup: failed to bring up eth1:5
> RTNETLINK answers: File exists
> ifup: failed to bring up eth1:6
> 
> Network interfaces I have configured are :
> - eth0 (LAN)
> - eth1 (WAN1) with six virtual interfaces eth1.[1-6]
> - eth2 (WAN2)
> - tap0
> - tap1
> 
> I cannot test as I cannot remove virtual interfaces but on all other servers
> without virtual interfaces, networking.service runs as expected.

networking.service is shipped by ifupdown, so reassign accordingly.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20170630/fa3e26f2/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list