Hello everyone,
I think I have an issue with NTP on my brand new TrueNAS scale build.
First, I saw the issue on the reporting tab, all date was 8hrs behind, I have to zoom out to see the graphs.
On my console I have the following:
In the Web UI, if I make any change, no matter how small to NTP servers, I can issue NTPQ -p with no problems.
BUT, right after this, I get "Connection refused".
Is the above behavior normal?
I have asked my ISP to unblock port 123 which they did.
Thank you!
I think I have an issue with NTP on my brand new TrueNAS scale build.
First, I saw the issue on the reporting tab, all date was 8hrs behind, I have to zoom out to see the graphs.
On my console I have the following:
Code:
admin@truenas[~]$ timedatectl status Local time: Fri 2023-03-17 00:24:48 EET Universal time: Thu 2023-03-16 22:24:48 UTC RTC time: Thu 2023-03-16 22:24:48 Time zone: Europe/Bucharest (EET, +0200) System clock synchronized: no NTP service: n/a RTC in local TZ: no admin@truenas[~]$
In the Web UI, if I make any change, no matter how small to NTP servers, I can issue NTPQ -p with no problems.
BUT, right after this, I get "Connection refused".
Code:
admin@truenas[~]$ ntpq -p remote refid st t when poll reach delay offset jitter ============================================================================== time1.google.co .GOOG. 1 u 1 64 1 41.165 +287937 0.000 ntp3.rdsnet.ro 10.199.226.96 2 u 1 64 1 7.202 +287937 1.807 185.86.67.2 207.197.87.124 4 u 2 64 1 6.135 +287937 0.000 time01.nevondo. 192.53.103.108 2 u 1 64 1 39.386 +287937 2.605 time.cloudflare 10.50.9.33 3 u 1 64 1 6.246 +287937 1.217 admin@truenas[~]$ ntpq -p ntpq: read: Connection refused admin@truenas[~]$
Is the above behavior normal?
I have asked my ISP to unblock port 123 which they did.
Thank you!