FreeNAS 11.3-U5 is now available

[Samuel Tai]

The release notes are here. New version guide is here. Note, you may need to clear your browser cache after upgrade, or portions of the web UI may seem unresponsive. Also note the caveat about replication targets needing to be at 11.3 or higher.

 

[revengineer]

Has anyone updated? Any side effects?

 

[blanchet]

I have updated my systems two days ago: I have seen no side effects, it just works.

 

[alex992]

Working fine

 

[tiberiusQ]

same here - all good !

 

[adrianwi]

All good here too. Thanks

 

[revengineer]

Thanks for the feedback. I got bit by a bug with the 11.3-U4 update but I updated now and with U5 so far all is well.

 

[Newfoundland.Republic]

Just updated to 11.3-U5 - no issues. Seems to have fixed my BMC USB error, too (fingers crossed )!

 

[profwalken]

Hi Have pushed update on 3 FN 11.3-U4.1
on the third i got problem during update, like GUI stay stuck at 62.5%
finally update finished and FN rebooted to latest 11.3-U5

in console I get this :
Oct 5 22:29:48 SRV-XXXX ntpd[1388]: restrict: ignoring line 10, address/host '0.freebsd.pool.ntp.org' unusable.
Oct 5 22:29:48 SRV-XXXX ntpd[1388]: restrict: ignoring line 11, address/host '1.freebsd.pool.ntp.org' unusable.
Oct 5 22:29:48 SRV-XXXX ntpd[1388]: restrict: ignoring line 12, address/host '2.freebsd.pool.ntp.org' unusable.

Where can I do something ?, I have just seen in general system ntp and there are same lines as others FN servers on which these messages doesn't appear.

 

[Newfoundland.Republic]

Do you have any firewall rules restricting that particular FN server from accessing that NTP source?

 

[nas4free]

Hello
Upgraded to FreeNAS 11.3-U5. Found following issues:
1. Cannot create new Jail, getting following error:
HTTPSConnectionPool(host='www.freebsd.org', port=443): Max retries exceeded with url: /security/unsupported.html (Caused by NewConnectionError(': Failed to establish a new connection: [Errno 65] No route to host'))
NOTE: www.freebsd.org resolves to 96.47.72.84 on the host, so, this is not name resolution issue.

2. Previously working Ubuntu VM comes up with read-only filesystem due filesystem errors. I had to run fsck to fix the issue
This may be a coincidence, but wanted to report it.

Thanks

 

[Newfoundland.Republic]

As far as I know nothing set to block NTP

From FN console, if I Ping line from NTP, it works
View attachment 41867

You could potentially have a firewall rule that allows ICMP (e.g. ping) but block NTP requests.

Try forcing the NTP update with:
ntpdate -v -b freebsd.pool.ntp.org

 

[Newfoundland.Republic]

I neglected to note that you need to stop the ntp daemon (ntpd). I *think* the command is:
service ntpd stop (as root).

That said, the clue is for some reason you cannot resolve freebsd.pool.ntp.org (I can resolve it).

 

[no_connection]

So far update broke network access to VM. I only have VLAN IP attached to a pfSense VM so I don't know if it's only that being dropped at host level or if all traffic is broken.

 

[Newfoundland.Republic]

From a windwos pc same LAN, only second command line resolve.

I'd do the simple thing: Add individual NTP servers; e.g.:
0.freebsd.pool.ntp.org
1.freebsd.pool.ntp.org
etc.

Interestingly, I cannot resolve freebsd.pool.ntp.org at home (it works at my office). However, my country's pool address (I'm in Canada) does work:

Code:

nslookup ca.pool.ntp.org
Server:        127.0.0.53
Address:    127.0.0.53#53

Non-authoritative answer:
Name:    ca.pool.ntp.org
Address: 209.115.181.113
Name:    ca.pool.ntp.org
Address: 162.159.200.123
Name:    ca.pool.ntp.org
Address: 206.108.0.131
Name:    ca.pool.ntp.org
Address: 209.115.181.108

How about using your country's ntp pool?

 

[Newfoundland.Republic]

Hmmm... try replacing them with France's ntp servers:

Code:

server 0.fr.pool.ntp.org
server 1.fr.pool.ntp.org
server 2.fr.pool.ntp.org
server 3.fr.pool.ntp.org

 

[profwalken]

Hi, thanks for help,
I've changed NTP servers in GUI and stopped and restarted NTP service, no message displayed in console.
I will try a complete server reboot to see if it's fixed

 

[Newfoundland.Republic]

@profwalken - See:

231193 – ntpd peers stuck in INIT status when using local named

bugs.freebsd.org

NTP is not working

I have configured ntp.conf to have four servers to synchronize with. When I run # ntpq -pn remote refid st t when poll reach delay offset jitter ============================================================================== 36.105.58.17 .INIT. 16 u -...

forums.freebsd.org

I wonder if they are related?

 

[Newfoundland.Republic]

@profwalken - At this point, I would recommend starting a new thread specifically on your ntp issue. Start the thread by detailing the symptoms, the outcomes and the results of what you have tried. Being buried in the "FreeNAS 11.3-U5 is now available" thread means that it is highly likely that someone with other potential solutions will not see it here.

Suggested thread topic: "NTP not working with FreeNAS 11.3-U5".

Good luck!

 

[profwalken]

I will ,thanks a lot for your help
I have deleted my posts here and pasted in new dedicated thread as you suggested
Well i did wrong myself deleting previous posts i lose all my screen captures in new thread , there's no way to retrieve them? no recycle bin to restore with?