> -----Original Message-----
> From: Todd Denniston [mailto:Todd.Denniston@xxxxxxxxxxxxxxxxxxxxx]
> Sent: Monday, October 18, 2010 10:43 AM
> To: CentOS mailing list
> Subject: Re: dhcpd rpm
>
> Ausmus, Matt wrote, On 10/18/2010 01:11 PM:
> > Howdy,
> >
> >
> <SNIP>
> >
> > WeÃââve found the problem is generally caused by the time being out
> of
> > sync between the servers or the dhcpd daemon on one of the boxes
> dies.
>
>
> NTP does not keep them closely enough synchronized?
> OH, and in case you were not aware of it, you could run NTP on one of
> them using local clock if you
> don't have a good trust able time server available for some reason.
> Also making your DHCP machines
> NTP peers would be good too.
>
> Or are you talking about some other type of time?
>
> --
> Todd Denniston
> Crane Division, Naval Surface Warfare Center (NSWC Crane)
> Harnessing the Power of Technology for the Warfighter
I think the problem we have/had was related to a Layer 8 issue. I have student workers build our DHCP servers from specifications that I give them. What more than likely happened was that dhcpdate wasn't run on the boxes when they were first built causing the date & time to be off and ntpd having issues getting the time back in line. My understanding of how ntpd works is that if the time is off too much it sees the time difference as irrational and is not able to pull it back in line. Once I run ntpdate on those boxes the issues go away and ntpd is able to maintain the time sync fine.
____________________________
Matt Ausmus
Network Administrator
Chapman University
"Nothing is ever accomplished by a reasonable man."
-Bucyâs Law
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
