Yeah, dhcpd must've gotten killed at that perfect moment twice for me. The last few restarts haven't caused a problem so that must be it. That's my luck. :(
On Wed, 13 Feb 2002, Martin Wuertele wrote: > > > default-lease-time 600; > > > max-lease-time 7200; > > > > I am also using those default values. The problem does not arise when the > > dhcp server goes down, but when it comes back up. Some machines end up > > with a new IP and existing connections die. Like ssh connections. :( > > did you try using fixed ip addresses based on mac address? > > looks like i don't have that problem as most of the boxes in the office > have a fixed address and the dhcp server has an uptime of 150 days... > > propably you have a problem with dhcpd.leases > > from man dhcpd.leases > > "There is a window of vulnerability where if the dhcpd pro? > cess is killed or the system crashes after the old lease > database has been renamed but before the new one has been > moved into place, there will be no /var/dhcp/dhcpd.leases. > In this case, dhcpd will refuse to start, and will require > manual intervention. DO NOT simply create a new lease > file when this happens - if you do, you will lose all your > old bindings, and chaos will ensue. Instead, rename > /var/dhcp/dhcpd.leases~ to /var/dhcp/dhcpd.leases, restor? > ing the old, valid lease file, and then start dhcpd. > This guarantees that a valid lease file will be restored."
