** Package changed: ifupdown (Ubuntu) = isc-dhcp (Ubuntu)
** Changed in: isc-dhcp (Ubuntu)
Importance: Undecided = Medium
** Changed in: isc-dhcp (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This was previously marked incomplete, then expired. However, all the
information that is available is in the bug. Here is a summary again:
dhclient stops trying to renew a lease if a previous renewal failed (due
to server being unavailable).
See #6 for all the logs available. See how the client
[Expired for ifupdown (Ubuntu) because there has been no activity for 60
days.]
** Changed in: ifupdown (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I will see if I can dig up the logs, but this happened a while ago and I only
got around to filing this bug now. Anyway, what happened on dozens of machines
(might have been hundreds):
Machine has a working ethernet connection (to the switch)
The network itself works reliably for the whole time.
Ubuntu's dhclient's -1 is different from upstream in that it never times
out on the first try, that was done specifically to avoid this bug.
** Changed in: ifupdown (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Well, that would cover the first failure mode I described, but we experience
the second one.
I don't see any workaround, apart from removing the -1 from the dhclient
options.
I'm sorry, but this means that a _part_ of my report might be invalid
(though we think we saw that issue), but the other
Can you provide a syslog showing that happening?
** Changed in: ifupdown (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1196975
Title:
ifupdown calling
Excerpts from Sven Mueller's message of 2013-07-02 15:43:57 UTC:
Well, that would cover the first failure mode I described, but we experience
the second one.
I don't see any workaround, apart from removing the -1 from the dhclient
options.
I'm sorry, but this means that a _part_ of my
Well, what we want is try forever in the foreground and daemonize on
success so not to block ifupdown (which is single threaded) from
executing the post-up scripts. And it's what our patch to dhclient is
supposed to be doing, if it's not, I want to see a log of this so we can
figure out exactly
