Your message dated Mon, 10 Oct 2011 11:51:01 +0300
with message-id <20111010115101.4b26699d@ileemo>
and subject line Re: Bug#644617: /sbin/ifup: "ifup -a" exits before dhcp setup
is finished
has caused the Debian Bug report #644617,
regarding /sbin/ifup: "ifup -a" exits before dhcp setup is finished
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.)
--
644617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644617
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ifupdown
Version: 0.6.10
File: /sbin/ifup
Severity: important
*** Please type your report below this line ***
"ifup -a" returns before the dhcp setup is completed.
So the network init script (/etc/init.d/networking) finishes before the
interfaces are actually set up and the LSB init script system doesn't
work as expected because scripts who's 'Required-Start'-tag contains
'$network' start before the network has been configured.
In particular the apache2 webserver doesn't start if the dhcp server is
slow.
-- System Information:
Debian Release: 6.0.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ifupdown depends on:
ii libc6 2.11.2-10 Embedded GNU C Library:
Shared lib
ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2
init scrip
ii net-tools 1.60-23 The NET-3 networking toolkit
ifupdown recommends no packages.
Versions of packages ifupdown suggests:
ii iproute 20100519-3 networking and traffic
control too
ii isc-dhcp-client [dh 4.1.1-P1-15+squeeze3 ISC DHCP client
pn ppp <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,
As the issue's resolved, I'm marking the bug as done.
--
WBR, Andrew
--- Begin Message ---
Hello Andrew,
I'm creating a live cd and because of that I don't have any influence on
the environment.
My problem is that whenever the dhcp server of the user who boots the cd
is slow the apache won't start.
The workaround for me is to change line 70 in /etc/init.d/networking:
"if ifup -a; then" -> "if ifup eth0 && ifup lo; then".
After that everything works perfect.
But I think that there are a lot of scenarios where the behaviour of
"ifup -a" and so /etc/init.d/networking is problematical.
The LSB system suggests that it's possible to ensure that a script is
running after the setup of the network interfaces is done by adding the
keyword "$network" to the attribute "Required-Start".
In fact it's not the case at least not under any circumstances.
I'm wondering why "ifup -a" exits before the work is done. Why does it
act differently than for example "ifup eth0"?
Best regards
Hendrik
Andrew O. Shadura wrote:
Hello,
On Fri, 07 Oct 2011 13:43:17 +0200
Hendrik Schwartke <[email protected]> wrote:
"ifup -a" returns before the dhcp setup is completed.
So the network init script (/etc/init.d/networking) finishes before
the interfaces are actually set up and the LSB init script system
doesn't work as expected because scripts who's 'Required-Start'-tag
contains '$network' start before the network has been configured.
In particular the apache2 webserver doesn't start if the dhcp server
is slow.
Hendrik, what dhcp client are you using? Does it have an option to
specify the DHCP reply timeout?
--- End Message ---
--- Begin Message ---
Hello,
On Mon, 10 Oct 2011 10:10:28 +0200
Hendrik Schwartke <[email protected]> wrote:
> I'm wondering why "ifup -a" exits before the work is done. Why does
> it act differently than for example "ifup eth0"?
I guess you have allow-hotplug eth0 or something in
your /etc/network/interfaces. That can change the behaviour.
--
WBR, Andrew
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi Andrew,
thank you for your very fast reply.
In fact I left the "allow-hotplug eth0" line and added "auto eth0", but
unfortunately with a typo ;(
So eth0 comes up but after "ifup -a" exits.
I don't know how to close this bug. Could you do this?
Thank you and best regards
Hendrik
Andrew O. Shadura wrote:
Hello,
On Mon, 10 Oct 2011 10:10:28 +0200
Hendrik Schwartke <[email protected]> wrote:
I'm wondering why "ifup -a" exits before the work is done. Why does
it act differently than for example "ifup eth0"?
I guess you have allow-hotplug eth0 or something in
your /etc/network/interfaces. That can change the behaviour.
--- End Message ---
signature.asc
Description: PGP signature
--- End Message ---
