Comment 8 for bug 1189571

Revision history for this message
Scott Moser (smoser) wrote : Re: isc-dhcp client "Unable to set up timer: out of range" caused by bad 64_bit timer

I don't understand it, but this does not seem to affect 12.04. That indicates this is an upstream regression (or ubuntu regression) between 4.1.ESV-R4-0ubuntu5.8 and 4.2.4-1ubuntu10 .

I verified booting a instance on azure of 12.04, and then

/var/lib/dhcp/dhclient.eth0.leases has:
 lease {
  interface "eth0";
  fixed-address 10.74.50.125;
  server-name "RD008CFA0438D2";
  option subnet-mask 255.255.254.0;
  option routers 10.74.50.1;
  option dhcp-lease-time 4294967295;
  option dhcp-message-type 5;
  option domain-name-servers 10.74.50.220;
  option dhcp-server-identifier 10.74.0.114;
  option dhcp-renewal-time 4294967295;
  option dhcp-rebinding-time 4294967295;
  option unknown-245 a:4a:32:dc;
  option domain-name "2ddcb339b3df4fd58fd5c9c97bf03ec5.sm-20130610-211835-precise.4202432685.useast.internal.cloudapp.net";
  renew 5 2149/07/18 03:48:33;
  rebind 5 2149/07/18 03:48:33;
  expire 5 2149/07/18 03:48:33;
}

$ sudo ifup eth0
ifup: interface eth0 already configured

$ ps axw | grep dhc
  962 ? Ss 0:00 dhclient3 -e IF_METRIC=100 -pf /var/run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -1 eth0