Ah yes silly me, that server doesn’t have IPv6! That worked!
Alright first one is up and running, I’ll get a few more up here shortly now that is sorted out.
1 Like
How can I modify a test monitor? (Alternatively, delete it and readd with different parameters.)
I have the test monitor frlys1-355n9ds, but the airport name should be rather GVA, to get something like frgva1-355n9ds. (In fact, the distance of the GVA airport is about 2 km from my monitor.)
What will cause a test ntppool-agent to stay in status testing? It has been like that for a day, unlike the other one that changed to status active pretty quickly.
1 Like
@ask do you have an idea why or how i can debug it?
1 Like
Hi John!
Thanks for adding it. It stayed in testing because currently Andreas or I have to toggle the status manually!
The intention was to have a way to “review” a monitor before it gets important; but … I don’t if it makes sense anymore.
In the old system this was more necessary, and I got burned by adding monitors from someone unfamiliar who then went on to write a research paper about how the pool could be manipulated. 
So – the new system has a bunch of automated controls to make it harder for someone to meaningfully manipulate the system; and one of the mechanisms is to have lots of monitors and for the system to slowly phase new monitors in as it makes sense.
I’m happy to hear questions and suggestions around this; but I think I’ll change it so new monitors automatically are “active”.
Sometimes having a human in the loop is not a bad thing. 
I was just wondering if it was something I did or did not do. For this one I build a local FreeBSD port / package and installed that. (The port does not compile it from source. It uses your binary tar files and create a ntpmon user and install a rc.d startup script.)
2 Likes
I tend to agree in general, especially given the somewhat sensitive role that the monitors play. I just fear a bit that when there aren’t enough resources available to actually deal with that, and proactively accept (or reject) new monitors, this might become a similarly stagnant area of the project as the full processing of vendor zones as per vendor needs (i.e., get a zone established in the first place, and including IPv6-enabled subzones while IPv6 isn’t available in the default zones), or reported errors in detected server geolocation not being processed.
And automation, not only in the form of AI/ML, helps free human resources to do something more worthwhile, e.g., progress actual pool functionality, vs. burning resources on low-level administrative chores.
1 Like
My plan is to have monitors automatically migrate from testing to active after they’ve been running for a week or maybe two. (They’ll need some time to go into “testing state” on a number of servers anyway).