I experienced similar behavior when I first set up a Linux server for the pool.
It turns out that I was dropping NTP packets due to the nf_conntrack_max kernel parameter value being too low for the amount of traffic I was getting. I set it at 256000 and the server has been stable since then. I've configured the server for 1 Gig network speed and am getting about 3 Mbps sustained NTP traffic. Cheers Gerardo Perales ---- On Mon, 05 Dec 2016 17:02:03 -0600 Joseph B <[email protected]> wrote ---- Hi fellow aussie :-) > I've been testing a LeoNTP[1] GPS Stratum 1 NTP device for the designer, > it's been sitting in the @ au oceania zones[2]. > [2] http://www.pool.ntp.org/scores/203.135.184.46 Interesting that as soon as your device hits the score threshold (10) and is added to the pool, the monitoring server starts having connectivity issues to your device. The score is decremented due to unreachability (from the monitoring perspective) and after a while reachability returns, the score improves, your device goes back into the pool and the cycle repeats. http://www.pool.ntp.org/scores/203.135.184.46/log?limit=50 A couple of things could be happening here: 1) The device is having issues answering all the queries 2) A firewall or device locally or upstream is dropping packets 3) DDOS filtering upstream is causing reachability issues Based on the other graphs, clearly once your device is no longer in the pool it is still serving traffic, so the issues with your device being able to stay in the pool successfully are likely related to 2 or 3. Cheers, Joseph _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
