data: lease_time: lease ends at 1248109552 when it is now 1248109556

[Glenn Satchell]

>Date: Tue, 21 Jul 2009 12:57:19 +0100
>Subject: data: lease_time: lease ends at 1248109552 when it is now 1248109556
>From: M S <sajext at googlemail.com>
>To: dhcp-users at lists.isc.org
>X-BeenThere: dhcp-users at lists.isc.org
>
>Hi,
>
>I was hoping someone on here can shed some light on the following DHCP 
exchange:
>
>Jul 20 17:05:55 DHCPSVR1 dhcpd: DHCPDISCOVER from 00:2a:d2:ae:1d:ef
>via 192.168.0.1
>Jul 20 17:05:55 DHCPSVR1 dhcpd: DHCPOFFER on 192.168.0.224 to
>00:2a:d2:ae:1d:ef via 192.168.0.1
>Jul 20 17:05:56 DHCPSVR1 dhcpd: DHCPREQUEST for 192.168.0.224
>(192.160.2.99) from 00:2a:d2:ae:1d:ef via 192.168.0.1
>Jul 20 17:05:56 DHCPSVR1 dhcpd: DHCPACK on 192.168.0.224 to
>00:2a:d2:ae:1d:ef via 192.168.0.1
>Jul 20 17:05:56 DHCPSVR1 dhcpd: DHCPRELEASE of 192.168.0.224 from
>00:2a:d2:ae:1d:ef via eth0 (found)
>Jul 20 17:05:56 DHCPSVR1 dhcpd: data: lease_time: lease ends at
>1248109552 when it is now 1248109556
>
>On the last line, I don't understand what it means by "lease_time:
>lease ends at 1248109552 when it is now 1248109556" is this fault?
>Done googling on this but can't find a clear answer.

What does your network look like? You have the initial requests coming
in via a relay 192.168.0.1. All looks good up to the release, which
comes in directly via eth0!!

Is the time on your server synchronised with NTP? Is it possible the
time jumped forwards by more than 4 sec around that point in time?

Suggest you look in the source code for the error message to get a bit
of context around it, although that may not be terribly enlightening.

                if (lease -> ends < cur_time) {
                        log_error ("%s %lu when it is now %lu",
                                   "data: lease_time: lease ends at",
                                   (long)(lease -> ends), (long)cur_time);
                        return 0;
                }

What type of device is the client? computer/os? or some appliance, etc?

I have never seen that message posted on this list :)

regards,
-glenn