When is a Commit... Not Really a Commit

[Norman Elton]

We're using event scripting in our config file to log a message each
time a lease is committed (using the "on commit" functionality). This
seems to be working well for 99% of the leases. But, occasionally, a
client gets a new IP address without anything getting logged. So we're
curious... what exactly qualifies as a "commit"?

In our case, we're doing failover between two servers. Here's are the
logs from the two servers of a transaction that I would have expected
to produce a commit message:

SERVER-1: DHCPREQUEST for 192.168.1.4 from 00:13:02:70:03:08 via
128.239.168.5: wrong network.
SERVER-1: DHCPNAK on 192.168.1.4 to 00:13:02:70:03:08 via 128.239.168.5
SERVER-1: DHCPDISCOVER from 00:13:02:70:03:08 via 128.239.168.5: load
balance to peer wm-dhcp-03-04
SERVER-1: DHCPREQUEST for 128.239.169.17 (128.239.10.124) from
00:13:02:70:03:08 via 128.239.168.5: lease owned by peer

SERVER-2: DHCPREQUEST for 192.168.1.4 from 00:13:02:70:03:08 via
128.239.168.5: wrong network.
SERVER-2: DHCPNAK on 192.168.1.4 to 00:13:02:70:03:08 via 128.239.168.5
SERVER-2: DHCPDISCOVER from 00:13:02:70:03:08 via 128.239.168.5
SERVER-2: DHCPOFFER on 128.239.169.17 to 00:13:02:70:03:08
(2006WM-3234409E) via 128.239.168.5
SERVER-2: DHCPREQUEST for 128.239.169.17 (128.239.10.124) from
00:13:02:70:03:08 via 128.239.168.5: lease owned by peer
SERVER-2: DHCPREQUEST for 128.239.169.17 (128.239.10.124) from
00:13:02:70:03:08 (2006WM-3234409E) via 128.239.168.5
SERVER-2: DHCPACK on 128.239.169.17 to 00:13:02:70:03:08
(2006WM-3234409E) via 128.239.168.5

Client comes line, tries to ask for an invalid IP, gets NAK'd. Turns
around, broadcasts a DISCOVER, which our router forwards to the
server. The second server responds. The client broadcasts a REQUEST,
two which the second server ACK's.

I'm a little curious why both servers show "lease owned by peer".
Could this be part of the problem?

Any other reason why the "on commit" script isn't firing under these
circumstances?

Thanks

Norman