Re: Will ntpd tell me if it encounters problems?



"gluino" <gluino@xxxxxxxxx> wrote in message
news:1176293456.182001.141420@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I am using the default ntpd setup in plain redhat box. Default
settings except for specifying a nearer time server.
Everything seems fine (ntpq pasted below), and it has been left alone
for months.
Said box hardly receives human attention, and is depended on for time
sync by a couple hundred local machines.

My question is: how would I know if ntpd has problems. I'm thinking of
some kind of alert when ntpd is unable to contact any good time
servers, for example.

# ntpq -np
remote refid st t when poll reach delay
offset jitter

============================================================================
==
203.117.180.36 .INIT. 16 u - 1024 0 0.000 0.000
4000.00
+64.109.43.141 130.149.17.21 2 u 534 1024 377 313.466
-19.302 2.021
+64.246.40.39 67.15.110.21 3 u 505 1024 377 253.106
-13.209 0.184
127.127.1.0 LOCAL(0) 10 l 60 64 377 0.000
0.000 0.001
*203.117.180.36 .ACTS. 1 u 582 1024 337 31.425
4.047 1.380

Assume the above is healthy?

Well... marginal. Healthy now, but it wouldn't take much.

You have four servers but one has never been reachable at all and
two others are indeed very far away. Although the jitter isn't
bad, I wouldn't trust them too much if the fourth server went away.
Stability _would_ suffer.

Generating alerts could be done by some simple checking of ntpq -p
output from a cron job. Check that you have an asterisk and a few
pluses. Check the stratum, reach, delay, offset, and jitter in the
relevant lines. If you don't like what you see, send an email and
have a human look closer.

No matter with Richard and his exclamation marks say, I consider
the local clock justified. Having several hundred clients following
a single wandering server in the event of problems is probably
preferable to all of them wandering aimlessly. Stratum ten is fine.

Groetjes,
Maarten Wiltink


.



Relevant Pages

  • Re: Local clock question with dialup connection
    ... This looks like ntpd is not running at the time you did this. ... It may be that the server is just dropping your queries. ... Internet, I run ntpq> pe, it shows local as a system peer, and ... they are being tried once while there is no initial Internet connection ...
    (comp.protocols.time.ntp)
  • syncing two machines, microsecond precision?
    ... Hi, I'm trying to sync two machines, one as the server the other as the ... client, both sitting on a private switched network. ... filegen clockstats file clockstats type day enable ... ntpq> rv ...
    (comp.protocols.time.ntp)
  • Re: NTP fails synchronization with server at startup
    ... synchronize with the server at booting. ... not make the connection. ... isn't up when NTP starts. ... Just for info I post a bit of output from ntpq> pe from FC2, ...
    (Fedora)
  • Re: notrust alternative?
    ... Any entries shown in ntpq other than those you configured are spurious and the result of tampering in the sources that leave here. ... My concern is that my server might be using systems other than the five I have listed in my ntp.conf as a synchronization source. ... restrict default kod nomodify notrap nopeer noquery ...
    (comp.protocols.time.ntp)
  • Linux/Windows: Different synchronization behaviour
    ... We are running ntpd ... clients on both Linux and Windows Server 2003 with identical ... Below I attach ntpq output and the ntp.conf configuration file. ... restrict default ignore ...
    (comp.protocols.time.ntp)