I am running TrueNAS SCALE Fangtooth 25.04 with 0.pool.ntp.org 1.pool.ntp.org and 2.pool.ntp.org as the NTP Servers. I also use rtcwake to put TrueNAS to sleep and wake at 8am.
This alert had accurred mulitple times already and it always time stamped at 8:02am
NTP health check failed - No Active NTP peers: [{‘SERVER: NOT_SELECTABLE [157.230.199.132]’}, {‘SERVER: NOT_SELECTABLE [70.116.101.97]’}, {‘SERVER: NOT_SELECTABLE [141.11.228.173]’}]
2025-07-19 08:02:23 (America/Chicago) => this is two minutes after TureNAS wake up from sleep.
Sometime I will see a clear but not always.
Any recommendation I should do next?
Would it make this less an issue if I use just one (ie. pool.ntp.org) NTP server?
Should I go back to the default NTP server? (need help on this, I forgot what I default NTP server was)
Thank you for the help in advance.
Howard
Thank you very much.
Changed back to default NTP Servers. Crossing my fingers.
Unfortunately, I received the same NTP health check failed alert again at 8:05am even using the default NTP server list.
I did timedatectl status to check. The output indicates System clock synchronized: yes, NTP service: active and RTC in local TZ: no
At this point, I believe the alert is just a transient condiction after the system woke up from sleep.
I am going to ignore it from now on. If anyone think I should dig into it further, I would appreciate your advises.
Adding my #meToo. On version TrueNAS Scale 24.10.2. Alert contents:
NTP health check failed - No Active NTP peers: [{'SERVER: SELECTABLE [162.159.200.1]'}, {'SERVER: SELECTABLE [167.248.62.201]'}, {'SERVER: SELECTABLE [2600:3c02:e000:74::123:0]'}, {'SERVER: NOT_SELECTABLE [192.168.1.218]'}]
I am trying to get it to prefer my domain controller in preference to the debian pool but maybe it’s not working right?
I am not getting any alerts that that machine is going down through host monitoring on my FingBox (I think the resolution for detection is like 5 minutes), but the alert notice and clear is usually exactly 12 hours (despite the apparent default frequency being “immediately”).
The alerts are also completely consistently, being sent at 5:26AM/PM
I’ll try adding another DC and having them talk to each other and maybe that will help availability? 
Try increasing the Min Pol and Max Pol values. Also look at Burst and IBurst tool tips. You probably have to change all lisitings
Are you also putting the server to sleep, like the OP does?
No, everything is running 24/7.
Sadly I haven’t been home during the times of “outage” and nobody complained that things weren’t working (as expected, the most egregious clock skews here are a few seconds a day and they’ll not likely care that the nas is being a bit funky)
