Tag Info

New answers tagged

1

Coming in a couple years late, but hopefully it will help. This will fix the unexpected interaction between ntpdate & ntp: rm -f /etc/network/if-up.d/ntpdate Then when you do a "update-rc.d ntp disable", ntp won't start on reboot.


0

Maybe this helps someone. We had the same problem recently and got the drifting into a reasonable range after having installed adtimex. aptitude install adjtimex


0

You have a simple syntax error in your manifest; something is setting $package_ensure to an array, when ensure wants it to be a string. Fix the definition of $package_ensure, and you're golden.


0

Depending on version of RHEL (which for whatever reason you decided not to include), you have to make sure ntpd (RHE6) or chronyd.service (RHEL7) IS running and set to start after reboot, also make sure it's configured properly. for more information: RHEL6: ntp.conf(5), ntpq(8), ntpdc(8) RHEL7: chrony(1), chronyc(1), chrony.conf(5), hwclock(8), ntpd(8) ...


0

Have you verified your NTP settings are pointing to your NTP server and communicating to the server? Or if you do not have an internal NTP server, verify that they are all pointing to the same external NTP server and that they are properly communicating to that server? You mention that the servers "lose sync". What does this mean exactly? Are they straying ...



Top 50 recent answers are included