NTP health check failed - No Active NTP peers for non configured NTP Servers

TrueNAS General
1

NTP health check failed - No Active NTP peers: [{‘SERVER: NOT_SELECTABLE [162.159.200.1]’}, {‘SERVER: NOT_SELECTABLE [178.251.64.52]’}, {‘SERVER: NOT_SELECTABLE [152.53.15.127]’}, {‘SERVER: NOT_SELECTABLE [86.59.80.170]’}]

This issue has been discussed several times BUT i have not found any solution so far to get rid of this bug as it ignores what i have configured in my system ?

This issue comes every day at 15:00 local time without any reason as the network is up and running AND those IPs are reachable.

So following questions:
1.) where are those NTP servers configured AS mine (configured in the GUI) might get ignored ?

  1. why are those configured when mine in the GUI should overwrite them.

  2. How can i get rid of this mess as nobody asked to query not reachable NPT servers within some config in the system - it’s annoying - this system should use the stuff i configured.

Address / Burst/iBurst/Prefered/Min Poll / MaxMoll
0.at.pool.ntp.org / No / Yes / Yes / 6 / 10

I am using TrueNAS 25.04.2.4 - Community Edition

Thnx for fixing this so i dont get Error Mails for no real errors !
Alex

2

Are those IPs behind the NTP pool?

3

I dont know ! i never configured this. this must be some system internal stuff

4

More to your point. It appears that the time servers from your configured NTP pool become unavailable at 1500 local time every day. That’s external to TrueNAS (maybe something with your ISP).

5

Thnx i will check this but i dont think that ALL “AT NTP server” get unavailable at 15:00 at once for everybody ?
But i will check and maybe add some more also from germany and other trustfull providers.

https://www.ntppool.org/de/zone/at
0.at.pool.ntp.org
1.at.pool.ntp.org
2.at.pool.ntp.org
3.at.pool.ntp.org

6

I added now 2 other countries. so this cannot happen again unless there is some other issue with my provider. but i was on the whole day so no ISP issue recognized from my side.

0.at.pool.ntp.org No Yes Yes 6 10
0.cz.pool.ntp.org No Yes Yes 6 10
0.de.pool.ntp.org No Yes Yes 6 10
1.at.pool.ntp.org No Yes Yes 6 10
1.cz.pool.ntp.org No Yes Yes 6 10
1.de.pool.ntp.org No Yes Yes 6 10
7

@Alexander_Wiltschek

You might want to set your min poll rate a bit higher to avoid getting blocked.

I run a Stratum 0 GPS+PPS NTP server on my pfSense firewall. Configurable clients are pointed directly to the firewall, or a firewall rule redirects all outbound NTP requests to the local firewall.

PROS:

  1. All clients are using the same time source
  2. Eliminates any Internet delay and minimizes offset/jitter
  3. All clients continue to receive time even if WAN is down
  4. Miscreants cannot profile what services or IoT devices I may have based on outbound NTP requests to hardcoded NTP servers.
  5. Makes me a good citizen by not allowing clients to overload external NTP servers with 1000’s of NTP requests per hour and possibly get blocked.

CONS:

  1. It takes a bit of trial and error to dial in the fudge[0,1] time values, but once they are, it works reliably.
1 Like