< snipped>
> 
> The server was still in the peerstats at 18:25 the following day
> when I did a reboot. So, after approximately 27 hours, ntpd
> hadn't dropped it. Obviously, my system isn't performing as you
> say it should. Can you, or anyone else, provide a clue as to how
> I might determine if my system is a fault or if there is a bug
> in the ntpd code?
> 
>> I.e. as long as you use the pool properly there is no need to worry 
>> about servers coming and going, or even individual servers that become 
>> falsetickers.

Hmmm. Sometime back I had noticed on my servers using the pool, that a couple 
of the selected servers had stopped responding. I did not know at the time that 
that situation was supposed to be dynamically corrected so I dropped the pool 
as  being unreliable. Maybe there is some issue. I just re-configured 4 servers 
back to using the pool and will monitor for black sheep.

> 
> When I first tried 4.2.8 I noticed the "soliciting" lines and
> that occasionally a server didn't get used.

 I have that too.

Feb 20 13:49:42 raspB2 ntpd[27451]: Soliciting pool server 195.154.41.195
Feb 20 13:50:48 raspB2 ntpd[27451]: Soliciting pool server 195.154.216.35
Feb 20 13:51:55 raspB2 ntpd[27451]: Soliciting pool server 5.39.78.25
Feb 20 13:51:56 raspB2 ntpd[27451]: Soliciting pool server 91.121.157.10
Feb 20 13:53:05 raspB2 ntpd[27451]: Soliciting pool server 195.154.78.115
Feb 20 13:54:12 raspB2 ntpd[27451]: Soliciting pool server 212.83.131.33
^Cmike@raspB2 ~ ntpq -pn
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*127.127.28.1    .GPS2.           0 l    4   16  377    0.000    0.008   0.006
+192.168.1.4     .PPS1.           1 u    3   16  377    0.926    0.039   0.032
+192.168.1.23    .GPS.            1 u    2   16  377    0.583    0.049   0.218
 0.pool.ntp.org  .POOL.          16 p    -   64    0    0.000    0.000   0.004
+5.39.78.25      140.7.62.122     2 u   14   64   17    5.883    2.928   0.047
+188.165.255.179 193.110.137.171  2 u    2   64    1    6.079    0.342   0.057

It also seems to be soliciting every minute and 7 secs. rather than hourly.

Feb 20 13:49:42 raspB2 ntpd[27451]: Soliciting pool server 195.154.41.195
Feb 20 13:50:48 raspB2 ntpd[27451]: Soliciting pool server 195.154.216.35
Feb 20 13:51:55 raspB2 ntpd[27451]: Soliciting pool server 5.39.78.25
Feb 20 13:51:56 raspB2 ntpd[27451]: Soliciting pool server 91.121.157.10
Feb 20 13:53:05 raspB2 ntpd[27451]: Soliciting pool server 195.154.78.115
Feb 20 13:54:12 raspB2 ntpd[27451]: Soliciting pool server 212.83.131.33
Feb 20 13:55:18 raspB2 ntpd[27451]: Soliciting pool server 188.165.255.179
Feb 20 13:55:19 raspB2 ntpd[27451]: Soliciting pool server 91.121.167.51
Feb 20 13:56:28 raspB2 ntpd[27451]: Soliciting pool server 178.32.54.53
Feb 20 13:57:35 raspB2 ntpd[27451]: Soliciting pool server 91.121.165.146
Feb 20 13:58:42 raspB2 ntpd[27451]: Soliciting pool server 91.121.169.20
Feb 20 13:59:50 raspB2 ntpd[27451]: Soliciting pool server 37.187.107.140
Feb 20 14:00:58 raspB2 ntpd[27451]: Soliciting pool server 195.154.108.164
Feb 20 14:02:05 raspB2 ntpd[27451]: Soliciting pool server 178.32.54.53
Feb 20 14:03:13 raspB2 ntpd[27451]: Soliciting pool server 129.250.35.250
Feb 20 14:04:22 raspB2 ntpd[27451]: Soliciting pool server 5.39.71.117
Feb 20 14:05:31 raspB2 ntpd[27451]: Soliciting pool server 129.250.35.251
Feb 20 14:06:38 raspB2 ntpd[27451]: Soliciting pool server 37.187.2.84
Feb 20 14:07:45 raspB2 ntpd[27451]: Soliciting pool server 87.98.188.218


> 
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions

Reply via email to