Package: ifupdown Version: 0.8.12 Severity: important I can see that at boot time on my systemd-based laptop, the /etc/network/if-pre-up.d and /etc/network/if-up.d scripts are run twice. Here are the corresponding lines from the journalctl output:
Jun 01 10:14:22 zira ifup[570]: /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-pre-up.d/ethtool Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-pre-up.d/wireless-tools Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-pre-up.d/wpasupplicant Jun 01 10:14:22 zira ifup[570]: Configuring interface lo=lo (inet) Jun 01 10:14:22 zira ifup[570]: /bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-pre-up.d/ethtool Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-pre-up.d/wireless-tools Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-pre-up.d/wpasupplicant Jun 01 10:14:22 zira ifup[570]: /bin/ip link set dev lo up Jun 01 10:14:22 zira ifup[570]: /bin/run-parts --exit-on-error --verbose /etc/network/if-up.d Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/avahi-autoipd Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/avahi-daemon Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/ethtool Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/mountnfs Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/openntpd Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/openssh-server Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/postfix Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/upstart Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/wpasupplicant Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/z_home_net Jun 01 10:14:22 zira ifup[570]: /bin/run-parts --exit-on-error --verbose /etc/network/if-up.d Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/avahi-autoipd Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/avahi-daemon Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/ethtool Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/mountnfs Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/openntpd Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/openssh-server Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/postfix Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/upstart Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/wpasupplicant Jun 01 10:14:22 zira ifup[570]: run-parts: executing /etc/network/if-up.d/z_home_net Jun 01 10:14:51 zira logger[1470]: netplug in: /sbin/ifup -v eth0 One of them corresponds to "Configuring interface lo=lo (inet)". But what about the other one? Note that it seems to partly break the configuration because at least z_home_net starts with: [ "$IFACE" != "lo" ] || exit 0 and the script does not exit here, which is unexpected at the point of the boot. Other if-up.d scripts have similar code, so may also break. This has occurred at least since December 2015, but I've noticed this problem only now due to bug 825995 (a time out in systemd 230 due to the fact z_home_net does not exit here, though this time out is itself unrelated). I've attached my /etc/network/interfaces file. -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ifupdown depends on: ii adduser 3.114 ii init-system-helpers 1.34 ii iproute2 4.3.0-1+b1 ii libc6 2.22-9 ii lsb-base 9.20160110 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.3.4-1 Versions of packages ifupdown suggests: pn ppp <none> pn rdnssd <none> -- Configuration Files: /etc/default/networking changed: VERBOSE=yes -- no debconf information
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface # [VL] No longer use "allow-hotplug eth0" as it makes the boot hang for # several dozens of seconds when no Ethernet cable is plugged in: # a DHCP client is started and is waiting for a response. The eth0 # interface will automatically be brought up by netplugd (from the # netplug package) when an Ethernet connection is detected. #allow-hotplug eth0 iface eth0 inet dhcp # USB tethering with my Samsung Galaxy Note 3. # Configuration on 2015-12-22: allow-hotplug enx02060b0e3333 iface enx02060b0e3333 inet dhcp # Configuration on 2016-05-01: allow-hotplug enp0s20u2 iface enp0s20u2 inet dhcp # $Id: interfaces 88628 2016-05-01 13:57:53Z vinc17/zira $
