Your message dated Mon, 16 Nov 2015 23:17:09 +0100 with message-id <[email protected]> and subject line ifupdown: All interfaces fail to come up after 2nd boot. ifup fails to bring up all interfaces. has caused the Debian Bug report #723184, regarding ifupdown: All interfaces fail to come up after 2nd boot. ifup fails to bring up all interfaces. to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 723184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723184 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ifupdown Version: 0.7.8 Severity: grave Justification: renders package unusable Dear Maintainer, I have now installed Debian Wheezy on three systems and have experienced this identical problem on all three. One was a hosted VM, the other two different boxes of my own. After the Debian installer is finished and the machine reboots the network comes up. But then when I alter /etc/network/interfaces to something like: auto lo iface lo inet loopback auto eth0 address 192.168.0.12 netmask 255.255.255.0 gateway 192.168.0.1 after rebooting NO interfaces come up, including lo. If I manually run: ifup lo it says "link: error fetching interface information: Device not found" for "ifup eth0" it says: addr: error feching interface information: Device not found during boot I can also see the message run by: link: error fetching interface information: device not found Also, running "/etc/init.d/networking restart" also fails similarly. If I run "ifconfig lo up" it brings up lo. If I run "ifconfig eth0 192.168.0.12 netmask 255.255.255.0 && route add default gw 192.168.0.1" eth0 also correctly comes up. Is it related to any other packages which I install after the first boot? The packages I usually install are: wireless-tools vim rsync cpufrequtils wpasupplicant pcmciautils screen dselect acpid powermgmt-base acpi powertop acpitool deborphan sudo anacron pm-utils cron-apt laptop-mode-tools ethtool dphys-swapfile intel-microcode iucode-tool kacpimon apt-file build-essential fail2ban on a minimal system which at the tasksel stage of the install I only select "standard system" and nothing else. I have checked the permissions for /etc, /etc/network, and /etc/network/interfaces and all look ok. /etc/hosts is ok. /etc/hostname is ok. /etc/resolv.conf is ok. -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ifupdown depends on: ii dpkg 1.16.10 ii initscripts 2.88dsf-41 ii iproute 20120521-3+b3 ii libc6 2.13-38 ii lsb-base 4.1+Debian8+deb7u1 ifupdown recommends no packages. Versions of packages ifupdown suggests: ii isc-dhcp-client [dhcp-client] 4.2.2.dfsg.1-5+deb70u6 ii net-tools 1.60-24.2 pn ppp <none> pn rdnssd <none> -- no debconf information
--- End Message ---
--- Begin Message ---Closing this bug, since the problem is/was with your /etc/network/interfaces file which is invalid: > auto lo iface lo inet loopback > > auto eth0 > address 192.168.0.12 > netmask 255.255.255.0 > gateway 192.168.0.1 This should have been: auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.0.12 netmask 255.255.255.0 gateway 192.168.0.1 Note the missing "iface eth0 inet static" line and the newline between "auto lo" and "iface lo inet loopback". -- Met vriendelijke groet / with kind regards, Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
