Den 10-01-2014 19:40, Daniel McDonald skrev:
On 1/10/14 10:33 AM, "Henrik Størner" <user-ce4a2c883f75@xymon.invalid> wrote:
Den 10-01-2014 15:49, Daniel McDonald skrev:
Running xymon 4.3.13 on SuSe ES 11 SP 3, the ntp test isn¹t working:
Command: ntpdate -u -q -p 2 10.1.9.51 2>&1
!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!!!
The ntpdate program is deprecated and should not be used any more.
I have given up on ntpdate, sntp, "ntpd -q" etc ... each sub-version of
the ntp package appears to have a new set of commands and options.
In version 5, the NTP check is built into the network test tool, so it
doesn't rely on any external programs.
That doesn't seem to be implemented yet on beta.xymon.com:
Fri Jan 10 19:29:02 2014 ntp ok
Service ntp on blixen.hswn.dk is OK (up)
Command: ntpdate -u -q -p 2 192.168.1.1 2>&1
Don't let that fool you :-) The "blixen" server is on an internal
network, so it cannot be reached from beta.xymon.com - the data you see
here comes from a Xymon network probe running version 4.
I've added another ntp check for the "strauss" server, so have a look at
http://beta.xymon.com/xymon-cgi/svcstatus.sh?HOST=strauss.hswn.dk&SERVICE=ntp
:
Service ntp on strauss.hswn.dk is OK (up)
Target : 78.46.170.167 port 123
Seconds: 0.001
But .. you ask: Where is all of the NTP data? It's in the client data:
http://beta.xymon.com/xymon-cgi/svcstatus.sh?CLIENT=strauss.hswn.dk§ion=ntp
[ntp]
Handler: ntp
StartTime: 1389391314
EndTime: 1389391314
TargetHostname: strauss.hswn.dk
TargetIP: 78.46.170.167
TargetPort: 123
Location: hetzner
Protocol: UDP
SSL: NO
Status: OK
TestID: 20
ElapsedMS: 0.237
DNSMS: 0.42
TimeoutMS: 30000
IntervalMS: 300000
BytesRead: 0
BytesWritten: 0
NTPstratum: 3
NTPoffset: -0.000005
Regards,
Henrik