[SRU] "Unable to set up timer: out of range" caused by bad 64_bit timer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
DHCP |
Fix Released
|
High
|
|||
isc-dhcp (Fedora) |
Fix Released
|
High
|
|||
isc-dhcp (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Quantal |
Fix Released
|
Medium
|
Unassigned | ||
Raring |
Fix Released
|
Medium
|
Unassigned | ||
Saucy |
Fix Released
|
Medium
|
Unassigned |
Bug Description
SRU justification
[Symtpom]:The dchp client on 12.10 and 13.04 on 64-bit installations fails with "Unable to set up timer: out of range" and then exits when the max lease time is given (~135years).
[Impact]: Systems running on networks with max lease times will not configure and the dhcpclient will error out and exit.
[Test Case]:
- Set DHCP Server to serve out max lease times
- Configure Ubuntu to use DHCP
- Run "sudo restart networking"
- Check if dhclient is NOT running, i.e. "ps axw | grep dhclient"
- Install new isc-dhcp-client and isc-dhcp-common package
- Run "sudo restart networking"
- Check if dhclient IS running, i.e. "ps axw | grep dhclient"
[Regression]: No regressions are expected. This fix simply reduces the lease time to (MAX_TIME - 9) seconds in cases where the lease exceeds the max lease.
[Other Info]
This is an upstream regression between 4.1.ESV-R4 (precise's isc-dhcp) and 4.2.4 (quantal, raring, saucy). It was fixed in Fedora under redhat bug 789601 (http://
[Originial Report]:
On Windows Azure, the max lease time is used. In digging, it appears
that the problem is related to the large lease times:
From /var/log/
Listening on LPF/eth0/
Sending on LPF/eth0/
Sending on Socket/fallback
DHCPREQUEST of 100.86.20.3 on eth0 to 255.255.255.255 port 67 (xid=0x30df9c2d)
DHCPACK of 100.86.20.3 from 100.86.20.1
RTNETLINK answers: File exists
Unable to set up timer: out of range
Failed to bring up eth0.
This looks like a duplicate of the RH Bug 789601
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: isc-dhcp-client 4.2.4-5ubuntu2
ProcVersionSign
Uname: Linux 3.8.0-23-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Mon Jun 10 17:57:48 2013
MarkForUpload: True
SourcePackage: isc-dhcp
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in isc-dhcp (Ubuntu Saucy): | |
importance: | Undecided → Medium |
Changed in isc-dhcp (Ubuntu Raring): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
description: | updated |
summary: |
- isc-dhcp client "Unable to set up timer: out of range" caused by bad - 64_bit timer + [SRU] "Unable to set up timer: out of range" caused by bad 64_bit timer |
description: | updated |
description: | updated |
Changed in dhcp: | |
importance: | Unknown → High |
status: | Unknown → Fix Released |
Changed in isc-dhcp (Fedora): | |
importance: | Unknown → High |
status: | Unknown → Fix Released |
dhcpd fails after a while with:
Feb 11 17:19:18 pent dhcpd: Timeout requested too large reducing to 2^^32-1
Feb 11 17:19:18 pent dhcpd: Unable to set up timer: out of range
Feb 11 17:19:18 pent dhcpd[29451]: Timeout requested too large reducing to 2^^32-1
Feb 11 17:19:18 pent dhcpd:
Feb 11 17:19:18 pent dhcpd[29451]: Unable to set up timer: out of range
dhcp-4. 2.3-6.P2. fc16.x86_ 64
Removing or modifying lease options below seems to make no difference. I don't know of a work-around.
dhcpd.conf is:
ddns-update-style interim;
authoritative;
ignore client-updates;
subnet 192.168.0.0 netmask 255.255.255.0 {
}
subnet 192.168.1.0 netmask 255.255.255.0 {
# --- default gateway
option routers 192.168.1.1;
option subnet-mask 255.255.255.0;
option nis-domain "localdomain";
option domain-name "localdomain";
option domain-name-servers 8.8.8.8;
# option time-offset -18000; # Eastern Standard Time
# option ip-forwarding off;
default-lease-time infinite;
max-lease-time infinite;
host rent {
# hardware ethernet 0:c0:9f:66:fa:fd;
# hardware ethernet 0:0b:6b:4c:40:52;
hardware ethernet 0:1a:6b:6a:21:5b;
# hardware ethernet 00:1b:77:5a:50:7b;
fixed-address 192.168.1.3;
option host-name "rent";
}
host argument {
hardware ethernet 00:12:3f:eb:7f:8f;
fixed-address 192.168.1.4;
option host-name "argument";
}
host sent {
hardware ethernet 00:1c:bf:42:fb:8a;
fixed-address 192.168.1.8;
option host-name "sent";
}
host went {
hardware ethernet 00:0f:b5:9f:c3:78;
fixed-address 192.168.1.100;
option host-name "went";
}
host parent {
hardware ethernet b8:ff:61:11:cc:34;
fixed-address 192.168.1.5;
option host-name "parent";
}
range 192.168.1.9 192.168.1.90;
}