*** From dhcp-server -- To unsubscribe, see the end of this message. ***
We recently had about 7 server failures in a two-week period in which the
server appeared to continue receiving packets normally, but didn't update
the leases file (and because of the way errors are handled in write_lease()
and supersede_lease()) also stopped answering client requests.
Our first thought was that we had a crucial i/o failure writing the leases
file, so we promptly created a new version of the server that more quickly
notified the system operators when an i/o error occurred. We never even got
that version into production when the failures magically stopped.
While we have several additional theories as to what might have occurred,
the situation hasn't arisen since the first spate of failures, so now we
suspect some sort of "killer" packet might be the culprit. During the
period in question we suspect that a user group might have been testing thin
clients, but have not been able to corroborate that suspicion.
So, my question is: has anyone else experienced an apparent server failure
for no reason at all, especially one that might correlate with the use of
thin clients?
--Barr
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
Archives for this mailing list are available at
http://www.webnology.com/list-archives/dhcp/dhcp-server
------------------------------------------------------------------------------
