Advertisements

NTP offset is over Critical threshold!

ATTENTION, RMC LEVEL 1 AGENT: This ticket will be automatically worked by the Automation Bus. Pls. ensure your Ticket List/View includes the

“Assignee” column, monitor this ticket until the user “ABOPERATOR” is no longer assigned, BEFORE you start work on this ticket.
Node : linux.setaoffice.com
Node Type : Intel/AMD x64(HTTPS)
Severity : critical
OM Server Time: 2016-07-25 18:54:18
Message : NTP offset is over Critical threshold!
Msg Group : OS
Application : ntpmon
Object : ntp
Event Type :
not_found

Instance Name :
not_found

Instruction : The ntpq -p command shows with one or more peers the
offset in time is greater than the threshold set in the
ntp_mon.cfg.

Please, review the ntp status of your system or increase
the threshold in the ntp_mon if you consider this offset
in time between the clocks of your system and the peer’s clock
is aceptable

Please check /var/opt/OV/log/OpC/ntp_mon.log for more details

Stopping ntp service

root@linux:~ # service ntp stop
Shutting down network time protocol daemon (NTPD) done

When I tried to run ntpdate in this Suse Linux Enterprise Server 11, I got an error message saying to use sntp

root@linux:~ # ntpdate ntpserver1
!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!!!

The ntpdate program is deprecated and should not be used any more. To
quote the upstream ntp developers:

“The functionality ntpdate offered is now provided by the ntpd daemon
itself. If you call ntpd with the command line option -q it will
retrieve the current time and set it accordingly.”

Please check the Network Time Protocol (NTP) daemon man page and
http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate
for further information.

You can replace the ntpdate call with “rcntp ntptimeset” to achieve an
inital poll of the servers specified in /etc/ntp.conf.

The program /usr/sbin/sntp offers comparable functionality to ntpdate.
Specifically
sntp -P no -r pool.ntp.org
is equivalent to
ntpdate pool.ntp.org

For further details please refer to the man page of sntp.

root@linux:~ # cat /etc/*release
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 3

I used my internal NTP server

root@linux:~ # sntp -P no -r ntpserver1

Started NTP server

root@linux:~ # service ntp start
Starting network time protocol daemon (NTPD) done

root@linux:~ # ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
ntpserver1 142.40.234.152 3 u 3 64 1 0.665 -27.640 0.001
ntpserver2 142.40.234.152 3 u 2 64 1 1.176 -17.426 0.001
142.40.5.45 .GPS. 1 u 1 64 1 11.257 -13.302 0.001

Check if the server lines in /etc/ntp.conf contain iburst

root@linux:~# grep server /etc/ntp.conf
server 142.40.234.152
server 142.40.234.153
server 10.32.5.29

root@linux:~ # vi /etc/ntp.conf

root@linux:~ # grep server /etc/ntp.conf
server 142.40.234.152 iburst
server 142.40.234.153 iburst
server 10.32.5.29 iburst

I was also having an reoccurence of this problem so I had to set the offset in ntp_mon.cfg

root@linux:~ # ls -l /var/opt/OV/conf/OpC/ntp_mon.cfg
ls: cannot access /var/opt/OV/conf/OpC/ntp_mon.cfg: No such file or directory

root@linux:~ # cp /var/opt/OV/bin/instrumentation/ntp_mon.cfg /var/opt/OV/conf/OpC

root@linux:~ # vi /var/opt/OV/conf/OpC/ntp_mon.cfg
###############################################################################
#@(#) $Id: ntp_mon.cfg 2149 2015-03-03 08:45:34Z zhaofeif $
#@(#) $Rev: 2149 $
#@(#) $Author: zhaofeif $
#@(#) $Date: 2015-03-03 16:45:34 +0800 (Tue, 03 Mar 2015) $
#@(#) $LastChangedBy: zhaofeif $
###############################################################################

############################################
# NTP_MON.CFG
# DESCRIPTION
#——————-
# Monitoring the NTP Daemon
# You can configure the monitoring to watch over
# the offset reported by the ntpq -p command
#
# PARAMS DESCRIPTION
#——————————
# [REARM = TRUE|FALSE]
# If set TRUE (or true), rearm function is enabled, default is disabled
#
# “DISABLE =[yes|no]” : This is the switch for ntpmon running
# NTP_OFFSET_CRITICAL,NTP_OFFSET_WARNING set offset critical and warning threshold for active peer, devaut values are 500 and 250 in ms
# NTP_STRATUM_CRITICAL, NTP_STRATUM_WARNING set offset of stratum of peers which status are one of “*”, “o”, “+” or “#”, the default value are 16 and 10
# NTP_ONLINE_TIME , ntpmon will not check anything if process ntpd is not running more than NTP_ONLINE_TIME(minutes), default value is 10(min)
# ALARM_DELAY, ntpmon allow to delay triggering alarm by setting minutes.
#——————————
# PARAMS REQUIRED
#———————————–
#
# CONFIG FILE
#————————–
############################################
#
# EXAMPLE:
#
#
#################################################################
#
# Set your configuration from here
#REARM = TRUE

DISABLE = NO
NTP_OFFSET_CRITICAL 1500
NTP_OFFSET_WARNING 500
NTP_STRATUM_CRITICAL 15
NTP_STRATUM_WARNING 12
NTP_ONLINE_TIME 3
#ALARM_DELAY 60

# Set your configuration from here

If the last column jitter has a high number, stop NTP service, delete the drift file and start NTP service

root@suselinux:~ # grep drift /etc/ntp.conf
driftfile /var/lib/ntp/drift/ntp.drift # path for drift file

root@redhatlinux:~ # grep drift /etc/ntp.conf
driftfile /var/lib/ntp/drift

root@linux:~ # ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
+cator2valedc002 142.40.234.152 3 u 31 128 377 0.465 -70499. 236.299
cator2valedc004 .INIT. 16 u – 256 0 0.000 0.000 0.000
*142.40.5.45 .GPS. 1 u 28 128 377 10.848 -70614. 175.292

Edit file /etc/sysconfig/ntp

root@linux:~ # cat /etc/sysconfig/ntpd
# Drop root to id ‘ntp:ntp’ by default.
OPTIONS=”-x -u ntp:ntp -p /var/run/ntpd.pid -g”

Advertisements
%d bloggers like this: