Advertisements

UXMON: The OFFSET in one peer is greater than the threshold: 400

Node : linux.setaoffice.com
Node Type : Intel/AMD x64(HTTPS)
Severity : minor
OM Server Time: 2015-10-28 13:01:33
Message : UXMON: The OFFSET in one peer is greater than the threshold: 400
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

Run ntpq -p and then check if the offset is higher than what’s configured on ntp_mon.cfg

root@linux:~ # cat /var/opt/OV/conf/OpC/ntp_mon.cfg
NTP_OFFSET 400
NUM_PEER_FAILS 5

Sync the two ntp servers that you are using and then restart the ntp service on the server

root@linux:~ # ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
ntp1 142.40.238.18 6 u 23 64 377 1.761 -23.727 9.886
ntp2 15.179.90.135 5 u 30 64 377 2.003 -48.137 4.418

Advertisements
%d bloggers like this: