[EMAIL PROTECTED] wrote: >> You never proposed changes, fixes or even some process to detect a cause. >> Meanwhile the monitoring system was observed by others to be 'fragile'. >> So you automagically remove time sources. > > If you don't know how to investigate such a problem, you should not be > running a pool server.
Criticism first. > It's probably just that you're serving atrocious time: > > $ ntpdate -q 80.101.128.228 > server 80.101.128.228, stratum 2, offset -0.216051, delay 0.47339 > 23 Aug 05:20:20 ntpdate[3409]: adjust time server 80.101.128.228 offset > -0.216051 sec Sometimes we don't have reception, so no pps. So we get time from outside sources. > $ ping -q -i 0.2 -c 20 80.101.128.228 > PING 80.101.128.228 (80.101.128.228) 56(84) bytes of data. Something within my scope to fix? The link has been up for the past night. > --- 80.101.128.228 ping statistics --- > 20 packets transmitted, 8 received, 60% packet loss, time 3843ms > rtt min/avg/max/mdev = 15.641/27.215/63.808/14.789 ms > > Probably primarily a network problem. You appear to be running it off an ADSL > connection... Indeed. I have been doing that for the past several years. First without gps, later with gps, doing small things for LinuxPPS, etc. We limit up/download speed in apps and using wondershaper, yet still our time is deemed unworthy. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
