SOLVED TrueNAS' web interface not reachable, TrueNAS not even visible, ntpd unusable?

[PépéDansLesOrties]

Hi,
I did shutdown (through GUI) my TrueNAS a few minutes, then restarted it... Usual web interface (freenas.local) was no more reachable.
I connected a screen to verify the web interface's direct address: 192.XXX.0.XX... Still not reachable.
But I got this on my screen:

Jan 5 16:45:04 freenas 1 2022-01-05T16:45:04.378486+01:00 freenas.local ntpd 1187 - - restrict: ignoring line 10, address/host '0.freebsd.pool.ntp.org' unusable.
Jan 5 16:45:04 freenas 1 2022-01-05T16:45:04.378944+01:00 freenas.local ntpd 1187 - - restrict: ignoring line 11, address/host '1.freebsd.pool.ntp.org' unusable.
Jan 5 16:45:04 freenas 1 2022-01-05T16:45:04.379385+01:00 freenas.local ntpd 1187 - - restrict: ignoring line 12, address/host '2.freebsd.pool.ntp.org' unusable.

I connected a keyboard and then tried a reboot to "see" any error messages:
everything seems fine, except

starting ntpd

taking too much time...
But yet, boot process seems to go all the way, display the (static set) web user interface address, and then the same three messages about ntpd unusable.
In addition, TrueNAS doesn't not appear in my network.
I'm totally lost, I got no idea of what's wrong and what to do... Everything was fine a few minutes earlier!
Thanks for your help!

 

[PépéDansLesOrties]

Update: in shell:

service ntpd stop
Stopping ntpd.
Waiting for PIDS: 1187.

ntpd actually stops.

ntpd
ntpd: daemon startup monitoring timed out.

and then:

Jan 6 05:55:25 freenas 1 2022-01-06T05:55:25.724431+01:00 freenas.local ntpd 13062 - - restrict: ignoring line 10, address/host '0.freebsd.pool.ntp.org' unusable.
Jan 6 05:55:25 freenas 1 2022-01-06T05:55:25.724909+01:00 freenas.local ntpd 13062 - - restrict: ignoring line 11, address/host '1.freebsd.pool.ntp.org' unusable.
Jan 6 05:55:25 freenas 1 2022-01-06T05:55:25.725333+01:00 freenas.local ntpd 13062 - - restrict: ignoring line 12, address/host '2.freebsd.pool.ntp.org' unusable.

 

[jgreco]

It's telling you that the pool addresses aren't usable. Is your ISP blocking your port 123?

 

[PépéDansLesOrties]

Hi jgreco,
no, it's not.
By the way, I shutted down my NAS just a few minutes, I haven't done any change during this time...

 

[jgreco]

Hi jgreco,
no, it's not.
By the way, I shutted down my NAS just a few minutes, I haven't done any change during this time...

Okay.

Try this:

Go to the command prompt and type "ping tick.sol.net"

You should get a ping response. If you don't, you have a networking problem.

Go to the command prompt and type "ntpdate -d tick.sol.net"

You should receive something that looks like

Code:

ntpdate[47718]: ntpdate 4.2.8p11-a (1)
transmit(206.55.65.228)
receive(206.55.65.228)
transmit(206.55.65.228)
receive(206.55.65.228)
transmit(206.55.65.228)
receive(206.55.65.228)
transmit(206.55.65.228)
receive(206.55.65.228)
server 206.55.65.228, port 123
stratum 3, precision -23, leap 00, trust 000
etc etc etc

which indicates ntpdate is able to communicate on an unprivileged port. This is good but not sufficient; ntpd needs to be able to talk on port 123, which has been blocked at a variety of service providers. But if those two things work, try changing one of your ntp servers to tick.sol.net, restart the ntpd service, wait a few minutes, and type "ntpq -p" which should show you synchronized.

All three of these things need to work or ntpd cannot sync time.

 

[PépéDansLesOrties]

Thanks a lot jgreco,
Since you mentionned my ISP, I remember I already had restarted my ISP, but not my routeur, so I did, and I get my NAS access and web interface back!!
What happened during these few minutes? Won't know! but problem's solved!
Nonetheless, I took time to see if ntpd issue was still on, thanks to your procedure, and everything's fine.
Thanks again,
have a great day/evening!
(And an happy new year, of course!)