Results 1 to 1 of 1
I'm running ntpd on my servers to keep their times synced with my 2 ntp servers (both windows 2003 server domain controllers). The problem is that the ntpd is not ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 05-22-2007 #1
ntpd not keeping time accurate
I'm running ntpd on my servers to keep their times synced with my 2 ntp servers (both windows 2003 server domain controllers).
The problem is that the ntpd is not keeping the time accurate and the clocks are drifting. I'm sure that when ntp is working properly the time is supposed to be second accurate, but it's not happening here.
The clocks are drifting 15-180 seconds away from the time of the master ntp servers within a few days. I then have to ntpdate to adjust the clocks back to the right time manually which is silly (in fact I have to stop ntpd, then ntpdate, then start ntpd as they use the same socket)
Below is my ntpd.conf without the comments:
server x.x.x.1 server x.x.x.2 driftfile /var/lib/ntp/ntp.drift restrict default ignore restrict 127.0.0.1
Both ntp servers are second accurate and their time is identical down to the split second. So why aren't the unix boxes keeping time using ntpd?