I note that a version 4.1.0 of the ntppool-agent package is available in the test repositories for deb and rpm packages.
Does anybody know what the updates/changes are?
The GitHub repository has a branch with activity that seems related to the migration from MySQL to PostgreSQL that Ask put on his agenda after the various recent outages related to the database.
Will this new package be compatible with the production system? As the package name, and the name of the binary, are the same for both the production and test packages, only one can be installed at any one time in my understanding. I.e., if the test package binary were not compatible with the production system, one would need to avoid updating any monitors registered in both the production and test/beta site for the time being.
At least there seems to be a packaging change: ntppool-agent obsoletes ntppool-monitor, ie. if you have an old (probably disabled and unused by now) ntppool-monitor installation, it will get removed.
I have now updated my test-only monitors to 4.1.0 and everything seems to be running fine.
ntppool-agent talks to the pool management servers via API calls. I’d expect the API to remain the same even if the backend database gets changed at some point. I’d also expect any new versions to be compatible with both testing and production environments. I’ll likely update my production monitor servers to the new version in the next few days, unless some new information comes up.
Was too slow to disable auto-update from the test repository on two of my monitors, and they already got upgraded. Working fine as well as far as I can see.
“W: GPG error: https://pkgs.ntppool.org/apt InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY B5810683F983E1EC”
when trying to update from the repo? The above url was provided as part of the monitor/agent process, iirc. However, when accessing it manually, I only get a 404 response. Any pointers?
@floppy Is it a new setup or old? I enabled signing in the apt repository and naively expected that existing configurations would just carry on. Maybe that’s not the case!
Sorry I didn’t post release notes for v4.1.0 or v4.1.1. No real changes in the client, just packaging to disable the old ntppool-monitor (the v3) instances that might still be running as none of them are active in the system anymore.
The API and scorer had some minor tweaks.
I’ve been working on migrating the whole system to Postgres (from MySQL), so most of the work the last months have been on branches related to that.
@ask Thank you for answering! It was an “older” setup (a few months maybe). So the new instructions completely were missed out by me. Following them fixed the situation for me.
Monitors/APT are fixed again…even added an IPv6 monitor, just saw one of my servers had little to do, so time to make it work hard for the money I spend on it
