** Changed in: isc-dhcp (Fedora)
Status: Unknown => Fix Released
** Changed in: isc-dhcp (Fedora)
Importance: Unknown => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad
There is a bad memory leak when many (thousands in our case) interfaces
are up and dhcpd is started. In addition it is very slow.
For the former, a call to freeifaddrs(ifaddr) is needed before the next
interface is looked at, and we got around the latter by only calling
getifaddrs() once, but tha
This bug was fixed in the package isc-dhcp - 4.2.4-7ubuntu12.2
---
isc-dhcp (4.2.4-7ubuntu12.2) trusty-proposed; urgency=medium
* debian/patches/dhcp-getifaddrs.patch: use getifaddrs
for getting nic addresses rather than /proc/net (LP: #1446767)
-- Scott MoserTue, 21 Apr 20
Yes, sorry for delay. We have been running repeated deployments with
Trusty and this package and are no longer hitting the problems anymore.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.laun
So, has anyone verified that the update is properly fixing the bug on
Trusty?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1446767
Title:
dhclient can fail if other nic
This bug was fixed in the package isc-dhcp - 4.3.1-5ubuntu2.1
---
isc-dhcp (4.3.1-5ubuntu2.1) vivid-proposed; urgency=medium
* debian/patches/dhcp-getifaddrs.patch: use getifaddrs
for getting nic addresses rather than /proc/net (LP: #1446767)
-- Scott MoserTue, 21 Apr 2015
With some other work that I was doing, I found bug 1272414
it seems that getifaddrs() is somewhat slow when lots of interfaces are used.
so this could have a bit of a performance impact in some places. that said,
dhclient is not likely a heavy use path.
--
You received this bug notification b
This bug was fixed in the package isc-dhcp - 4.3.1-5ubuntu2.1
---
isc-dhcp (4.3.1-5ubuntu2.1) vivid-proposed; urgency=medium
* debian/patches/dhcp-getifaddrs.patch: use getifaddrs
for getting nic addresses rather than /proc/net (LP: #1446767)
-- Scott MoserTue, 21 Apr 2015
## host system is vivid, trusty would also do
host $ rel=trusty ; serial=20150417
host $
url=http://cloud-images.ubuntu.com/releases/$rel/release-$serial/ubuntu-14.04-server-cloudimg-amd64-disk1.img
host $ img_dist="$rel-$serial-amd64.img.dist"
host $ img=${img_dist%.dist}
host $ pkgs="qemu-util
host $ rel=vivid serial=20150422
host $
url=http://cloud-images.ubuntu.com/releases/$rel/release-$serial/ubuntu-14.04-server-cloudimg-amd64-disk1.img
host $ img_dist="$rel-$serial-amd64.img.dist"
host $ img=${img_dist%.dist}
## host
host $ pkgs="qemu-utils qemu-system-x86 cloud-image-utils"
host
This has already ended up in vivid-proposed.
** Also affects: isc-dhcp (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=449946
Importance: Unknown
Status: Unknown
** Changed in: isc-dhcp (Ubuntu W-series)
Status: Confirmed => Fix Committed
** Changed in: isc-dhcp (Ubu
** Description changed:
+ === Begin SRU Information ===
+ [Impact]
+ Systems that use dhcp for network config combined with network device
re-naming can hit a race condition in dhclient which causes dhcp to fail. Any
network device renaming could cause this, but the most likely scenario is boo
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1446767
Title:
dhclient can fail if other nics are renamed
Status in isc-dhcp package in Ubuntu:
Co
The solution here was pulled from
https://bugzilla.redhat.com/show_bug.cgi?id=449946
The patch really just makes linux use getifaddrs rather than reading
/proc/net/dev for information.
The change has been in place in fedora for ~ 3 years, so that should
stand as some testimony.
** Bug watch ad
I've also put these attached recreate programs and the original kvm boot
recreate at lp:~smoser/+junk/lp128/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1446767
Titl
** Attachment added: "nic-go-crazy: randomly rename nics for dhclient noise"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1446767/+attachment/4380760/+files/nic-go-crazy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri
** Patch added: "fix applied to vivid"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1446767/+attachment/4380759/+files/lp-1446767-vivid.diff
** Attachment removed: "nic-go-crazy: randomly rename nics for dhclient noise"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/144
** Attachment added: "ifup-loop: loop over ifdown / ifup for a nic to cause
dhclient failure"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1446767/+attachment/4380761/+files/ifup-loop
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
** Patch added: "patch for trusty"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1446767/+attachment/4380752/+files/lp-1446767-trusty.diff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https
** Description changed:
given 3 nics eth0, eth1, eth2
dhclient -1 -v -pf /run/dhclient.eth0.pid -lf
/var/lib/dhcp/dhclient.eth0.leases eth0
while that in its early phases, if eth1 is renamed a race condition can
cause dhclient to exit failure.
+
+ This can happen in real life when
** Attachment added: "nic-go-crazy: randomly rename nics for dhclient noise"
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1446767/+attachment/4380696/+files/nic-go-crazy
** Changed in: isc-dhcp (Ubuntu)
Status: New => Confirmed
** Changed in: isc-dhcp (Ubuntu)
Importance:
21 matches
Mail list logo
