Also seeing this to DO's NYC3 DC. -100 on one server (despite traffic still hitting it) and a very unstable score on the other.
I really believe we need distributed scoring as we can't see the data and the polling service could be the issue. Lucas On July 5, 2016 1:32:09 PM CDT, "George R. Kasica" <[email protected]> wrote: >Starting on about 6/14/16 at around 0400 local time (Central Daylight >Time US UTC-6) all 5 of our time servers here can't be reached by the >Status polling servers apparently. Yes if I put up tcpdump on the Linux >hosts and do a packet capture on port 123 I can see traffic from many >other hosts coming into all 5 of the systems here and no one is >reporting any outages (including where I'm employed that used them and >monitors them - they were unreachable we'd have pages going off within >5-10 minutes). > >There is no firewalling that would block by IP or port for port 123 and >nothing has changed here for set up at that time to cause them to >suddenly drop out. > >Is there some way I can see what the Pool Status polling is looking >like from the NTP Pool end to get more of a clue as to why this has >suddenly started to fail? I've sent email to Ask but haven't yet >received a reply. > >George >_______________________________________________ >pool mailing list >[email protected] >http://lists.ntp.org/listinfo/pool -- Sent from my Android device with K-9 Mail. Please excuse my brevity. _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
