Advertisements

UXMON: NTP Problems. Running on local time. Peer: 127.127.1.0 Cur. Offset: 0.000 Cur.

Having this problem alerted on a Linux system

Node : linux.setaoffice.com
Node Type : Intel/AMD x64(HTTPS)
Severity : minor
OM Server Time: 2015-03-24 19:54:33
Message : UXMON: NTP Problems. Running on local time. Peer: 127.127.1.0 Cur. Offset: 0.000 Cur. Symbol: * Ref. ID: .LOCL.
Msg Group : OS
Application : ntpmon
Object : ntpq
Event Type :
not_found

Instance Name :
not_found

Instruction : This message shows no valid peers

Please, contact with your UX expert

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

Verifying the log file I noticed the following

root@linux:~ # tail -50 /var/opt/OV/log/OpC/ntp_mon.log
NTP Problems. Running on local time. Peer: 127.127.1.0 Cur. Offset: 0.000 Cur. Symbol: * Ref. ID: .LOCL.”

Comment the line that is saying it is using the local clock on file /etc/ntp.conf

#server 127.127.1.0 # local clock

It is using the fake driver even if it is configured to use 4 NTP servers configured

root@linux:~ # ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*LOCAL(0) .LOCL. 10 l 38 64 377 0.000 0.000 0.001
NTP1server 172.16.73.51 4 u 5 16 1 31.138 -15.569 0.001
NTP2server 172.16.73.9 3 u 4 16 1 26.626 -15.001 0.001
NTP3server 172.16.73.50 5 u 3 16 1 23.416 -16.803 0.001
NTP4server 172.16.73.51 4 u 2 16 1 28.340 -10.889 0.001

Stopped NTP service and it was still listening

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

root@linux:~ # ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*LOCAL(0) .LOCL. 10 l 65 64 377 0.000 0.000 0.001
NTP1server 172.16.73.51 4 u – 16 377 30.697 -18.969 2.157
NTP2server 172.16.73.9 3 u 13 16 377 26.172 -1.256 1.121
NTP3server 172.16.73.50 5 u 11 16 377 23.315 -12.326 8.230
NTP4server 172.16.73.51 4 u 16 16 377 28.309 -11.716 2.544

Found that there was already another NTP process running

root@linux:~ # ps -ef | grep ntp
root 23339 1 0 2014 ? 00:38:38 ntpd -pq
root 30880 23657 0 10:07 pts/8 00:00:00 grep ntp

Killed the process

root@linux:~ # kill 23339
root@linux:~ # ps -ef | grep ntp
root 30918 23657 0 10:07 pts/8 00:00:00 grep ntp

NTP stopped listening

root@linux:~ # ntpq -p
ntpq: read: Connection refused

Started NTO service

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
==============================================================================
NTP1server 172.16.73.51 4 u 5 16 1 31.138 -15.569 0.001
NTP2server 172.16.73.9 3 u 4 16 1 26.626 -15.001 0.001
NTP3server 172.16.73.50 5 u 3 16 1 23.416 -16.803 0.001
NTP4server 172.16.73.51 4 u 2 16 1 28.340 -10.889 0.001

Advertisements
%d bloggers like this: