On 21 October 2013 22:54, Tony Caffe <anth...@woboinc.com> wrote: > > Now when I run puppet agent on these 2 specific vms, it "looks" fine and > completes, updates whatever. >
I assume by that, you mean that the puppet agent run completes without issues, and that the NTP configuration looks as you would expect it to following the successful run? > Well when you run command: *date* it doesnt fix the date as it should. > Do you mean the time is incorrect, or the timezone is incorrect? > I was wondering, is there a way to have puppet check that *date* command > displays the correct time for that timezone. My timezone is Los Angeles/ > PDT/ PST. > One issue with ntpd is that, if the time is too far off your time source, then if the '-x' option is given to ntpd, it will not 'jump' the time forward or back. A manual 'ntpdate your.ntp.server' is required then to jump it to the correct time. If you run the following on one of your failing hosts, what does it output? ntpdate -q your.ntp.server On a correctly syncing server here, I see: server my.ntp.server, stratum 2, offset 0.008437, delay 0.05721 22 Oct 12:34:27 ntpdate[25978]: adjust time server my.ntp.server offset 0.008437 sec ntpd(8) is enlightening as to how quickly/slowly, if at all, the clock will be adjusted in various situations. Regards, Matt. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
