Ntpdate not updating clock
But not properly and you'd be better off with only ntpdate).
If you don't have such a connection, restrain yourself to ntpdate.
The smoking gun was that I temporarily have two independent, internet feeds.
In linux if I run does go around this, well, temporarily (no pun intended), it does not fix the time issue long term.
If you're using ntp, then YES, you must request permission to use the server about 4 times out of 5.
But it also implies that on an upgrade from a former release ntp/ntpdate might still be installed and therefore renders the new systemd based services disabled.ntp and ntpdate and installed both (i have an always on connection to the ntpdate is used to do a "one time only" update to your clock.ntp is used to discipline your clock and will in fact keep the RTC in a short leash updating it every 11 minutes. Ntp will refuse to run if your clock is off by more than a certain amount of time (which isn't very big BTW, so this is a real risk).In my case my ISP (Internet Service Provider) was blocking ports.A port scan of 123 didn't detect the blockage either.
If you use modems for dialup, forget ntp and use ntpdate.