Nagios Support Forum

Dear experts,

recently I am trying to figure it out the problem with nagios critical warnings:

Current Status: CRITICAL (for 1d 16h 22m 57s)
Status Information: NTP CRITICAL: Offset 29295.67938 secs Splunk It
Performance Data: offset=29295.679383s;60.000000;120.000000;
Current Attempt: 3/3 (HARD state)
Last Check Time: 12-01-2014 04:46:02
Check Type: ACTIVE

I have 2 NTP servers and both has the same problem, both NTP uses:

server 0.north-america.pool.ntp.org iburst
server 1.north-america.pool.ntp.org iburst
server 2.north-america.pool.ntp.org iburst
server 3.north-america.pool.ntp.org iburst

On NTP server:

[root@centos19 ~]# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
-108.61.194.85.v 193.190.230.65 2 u 62 128 377 60.290 -13.203 0.190
*cheezum.mattnor 24.56.178.140 2 u 75 128 377 25.580 3.538 0.325
+linode2.file-it 193.190.230.66 2 u 68 128 377 54.589 -3.314 0.445
+sola-dal-09.ser 10.0.77.54 4 u 63 128 377 27.338 -2.518 0.168
LOCAL(0) .LOCL. 10 l 61 64 377 0.000 0.000 0.000

so there is communication between NTP and external 0.north-america.pool.ntp.org.

Locally: [root@centos19 plugins]# ./check_ntp_time -H localhost
NTP OK: Offset -1.14440918e-05 secs|offset=-0.000011s;60.000000;120.000000;

[root@centos19 plugins]# ./check_ntp_time -H 0.north-america.pool.ntp.org
NTP OK: Offset 0.006208539009 secs|offset=0.006209s;60.000000;120.000000;

What else I can check in order to get rid of these critical warnings? Thanks

It looks like the plugins are returning properly now, have you tried scheduling a forced immediate check on one of those services to see if it updates back to OK? If it does not, your service check_command must be different than what you are manually running and we need to see what you have on that service, for that check_command.

it has been fixed, silly me I did not check the time on the nagois server by itself ,,,,it was off exactly 29000 ms

problem solved, Thank You!

Great! We'll go ahead and close this issue. Thanks.