The quick fix is to run "dpkg-reconfigure ntp" on any affected hosts. I had set that up as a bcfg2 action for a while, but disabled it when I thought we can hit everything. Guess I was wrong. Ken Raffenetti Systems Administration Associate MCS Division - Argonne National Laboratory On 06/14/2012 09:44 AM, Ti Leggett wrote:
Can you add <Permissions /> for that directory in bcfg to make sure it's set right or is there something else?
On Jun 14, 2012, at 9:19 AM, Ken Raffenetti wrote:
That's been a battle we've fought between our image and bcfg2 since we rolled Lucid out. It's a big part of why I monitor NTP everywhere.
Ken Raffenetti Systems Administration Associate MCS Division - Argonne National Laboratory
On 06/14/2012 08:23 AM, Craig Stacey wrote:
Now that's weird. /var/log/ntpstats was not owned by ntp, and thus couldn't write there.
root@vserver7:~# ls -ld /var/log/ntpstats/ drwxr-xr-x 2 avahi-autoipd haldaemon 4096 2010-04-08 22:14 /var/log/ntpstats/
I chowned it to ntp:ntp. -- Craig
On Jun 14, 2012, at 8:14 AM, [email protected] wrote:
***** Nagios *****
Notification Type: PROBLEM
Service: NTP Host: vserver7 Address: vserver7.mcs.anl.gov State: CRITICAL
Date/Time: Thu Jun 14 08:14:44 CDT 2012
Additional Info:
NTP CRITICAL: Server not synchronized, Offset unknown
URL: https://peer.mcs.anl.gov/nagios3/cgi-bin/extinfo.cgi?type=2&host=vserver7.mc...