Bug#637435: ifupdown: interfaces are not brought up anymore
Package: ifupdown Version: 0.7~alpha5+really0.6.11 Severity: critical Justification: breaks the whole system Hi. Since the recent upload to unstable, ifupdown seems to no longer bring up any interfaces, not even lo. $ ifconfig shows nothing,... after bringing down and then up lo,... it appears again and also eth0 starts to retrieve settings via DHCP. Reverting to 0.7~alpha5+really0.6.10 solves the issue. Cheers, Chris. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-heisenberg (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_DE.utf8, LC_CTYPE=en_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ifupdown depends on: ii libc6 2.13-16Embedded GNU C Library: Shared lib ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip ii net-tools 1.60-24.1 The NET-3 networking toolkit ifupdown recommends no packages. Versions of packages ifupdown suggests: ii iproute 20110629-1 networking and traffic control too ii isc-dhcp-client [dhcp3-clien 4.1.1-P1-17 ISC DHCP client ii ppp 2.4.5-5 Point-to-Point Protocol (PPP) - da -- debconf information: ifupdown/convert-interfaces: true -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637435: ifupdown: interfaces are not brought up anymore
Hello, On Thu, 11 Aug 2011 13:41:23 +0200 Christoph Anton Mitterer wrote: > Since the recent upload to unstable, ifupdown seems to no longer > bring up any interfaces, not even lo. > $ ifconfig > shows nothing,... > after bringing down and then up lo,... it appears again and also eth0 > starts to retrieve settings via DHCP. > Reverting to 0.7~alpha5+really0.6.10 solves the issue. Sorry, can't reproduce. I've just installed a clean unstable system, and it just doesn't happen. Please provide more details. -- WBR, Andrew signature.asc Description: PGP signature
Bug#637435: ifupdown: interfaces are not brought up anymore
There is something going on with recent update - my server failed to bring up dhcp interfaces too. It shows up that it's because "lo". /etc/init.d/interfaces reports that lo is already up (but it's not configured) - dhcp fails to start (since no 127.0.0.1). So shutdown/startup interface cleanup is somehow wrong (adding to /etc/init.d/network - ifdown lo; ifup lo - fixed entire process for me). Cheers - Adrian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637435: ifupdown: interfaces are not brought up anymore
Ehh, I wanted to write fast ... and I've made my last post a complete rubbish - sorry. >From beginning. After today restart, server did not boot up properly (hang - on configuring dhcp interfaces). I've started to look what's going on, I thought it's perhaps because of some changes in kernel 3.0.1 that I've just compiled - but old kernel gave me the same result. Then I find out that despite system claims "lo" is up (ifup lo showed it's "up") it's not configured and there is no 127.0.0.1 interface. I've started to test and it came out that /etc/init.d/networking script should bring all interfaces up (ifup -a) - but on this level "lo" is already reported as up (but not configured). I had not time to look for more (perhaps cleanup script is missing something...) and I've just added to /etc/init.d/networking in "start" section "ifdown lo; ifup lo" before "ifup -a" - it's ugly, but it's working. Ok I hope it's more clear now. My version: ii ifupdown 0.7~alpha5+really0.6.11 Cheers - Adrian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637435: ifupdown: interfaces are not brought up anymore
Hello, On Thu, 11 Aug 2011 21:08:37 +0200 Adrian Siemieniak wrote: > There is something going on with recent update - my server failed to > bring up dhcp interfaces too. It shows up that it's because > "lo". /etc/init.d/interfaces reports that lo is already up (but it's > not configured) - dhcp fails to start (since no 127.0.0.1). So > shutdown/startup interface cleanup is somehow wrong (adding > to /etc/init.d/network - ifdown lo; ifup lo - fixed entire process > for me). Please tell me where your /etc/network/run resides, is it on rootfs, or is it in /dev/shm or wherever else? -- WBR, Andrew signature.asc Description: PGP signature
Bug#637435: ifupdown: interfaces are not brought up anymore
It's plain root partition (no lvm) sauron:/etc/network# ls -ld run drwxr-xr-x 2 root root 4096 Aug 11 2011 run sauron:/etc/network# ls -l run total 4 -rw-r--r-- 1 root root 46 Aug 11 2011 ifstate This server has been upgraded for many years (more then 10 years on unstable now) - so quite often happens, it have really old and forgotten by "package managers" files :) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637435: ifupdown: interfaces are not brought up anymore
On Thu, 2011-08-11 at 20:41 +0300, Andrew O. Shadoura wrote: > Sorry, can't reproduce. I've just installed a clean unstable system, > and it just doesn't happen. > > Please provide more details. Well during ifupdown-clean on boot i get a cannot remove /etc/network/run/ifstate ... ro filesystem (shouldn't this go to /run now anyway?!) When I remove that file manually before restart, it brings the ifaces correctly up on the next boot. Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#637435: ifupdown: interfaces are not brought up anymore
Hello, Well, that's exactly what I suspected to happen. Tomorrow I will prepare a new release which should fix this issue. About /run --- not yet :-) -- WBR, Andrew -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637435: ifupdown: interfaces are not brought up anymore
On Fri, 2011-08-12 at 16:42 +0300, O. Andrew wrote: > Well, that's exactly what I suspected to happen. Tomorrow I will > prepare a new release which should fix this issue. Thx in advance, Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
