NAS4Free 11.1.0.4.5313 released (FreeBSD 11.1-RELEASE-P8)

[zoon01]

The NAS4Free Team is pleased to announce the release of version 11.1.0.4.5313 - Atomics

This is an security maintenance release to address:
CVE-2018-1050 and CVE-2018-1057
CVE-2017-5715, CVE-2017-5754 (FreeBSD-SA-18:03)

Download build 11.1.0.4.5313
Please Read always the readme_11.1 file

BUILD 11.1.0.4.5313

Changes after release 11.1.0.4.5279
===============================
- Upgrade to FreeBSD 11.1-RELEASE-P8.
- Webgui framework/code improvements.
- Update translations.
- Upgrade intel microcode.
- Upgrade nano to 2.9.4.
- Upgrade lighttpd to 1.4.49.
- Upgrade samba to 4.7.6.


Note:
- Make a new backup of your system configuration and store this on safe location, the system config.xml has been upgraded!
- Clear your browser's cache to avoid display issues after upgrade when coming from older release like past 11.0 series.

Enjoy!

Regards,
The NAS4Free Team

[adultery_nas]

Working great! Thanks a million zoon!!

[Barmynon]

Hi,

I noticed this error after upgrading to 11.1.0.4 - Atomics (revision 5313) when you select the Disks/zfs/volumes tab. It may have been there before but I don't often go there in the GUI.

Fatal error: Uncaught Error: Call to a member function insTHwC() on string in /usr/local/www/disks_zfs_volume.php:204 Stack trace: #0 {main} thrown in /usr/local/www/disks_zfs_volume.php on line 204

Thanks for your continually excellent work on this project.

Barmynon

[raulfg3]

Yes, confirmed, not detected until you post, sorry.

[ms49434]

Hi,

I noticed this error after upgrading to 11.1.0.4 - Atomics (revision 5313) when you select the Disks/zfs/volumes tab. It may have been there before but I don't often go there in the GUI.

Fatal error: Uncaught Error: Call to a member function insTHwC() on string in /usr/local/www/disks_zfs_volume.php:204 Stack trace: #0 {main} thrown in /usr/local/www/disks_zfs_volume.php on line 204

Thanks for your continually excellent work on this project.

Barmynon

Found & fixed with commit r5317

[Snapshot]

Updated successfully on my Gen8.
Is there a tutorial for applying commits or is it safer just to wait for the next release?

[ms49434]

Waiting for the next release is the safest option.

Applying a commit is not the preferred way to keep your system up to date because
- there is a possibility of dependency issues.
- An embedded installation will revert the modified file(s) to the released version on reboot.

The bug will not show when ZFS volumes have been already defined,
If you have an urgent need to create your first ZFS volume and you are on r5313 already you can download, replace and run the above file without issues. Don't forget to refresh / clear your browsers cache. It might take some time until the new version becomes available (PHP cache).

[Onichan]

Recently started having issues and happened to notice Samba was using 12GB+ of RAM. Found this post https://forums.freenas.org/index.php?th ... -ram.61039 and bug report https://redmine.ixsystems.com/issues/28585.

Adding

Code: Select all

unix extensions = no
wide links = yes

as additional parameters appears to have fixed it now as a workaround until they find more about the root cause.

[rocket]

Recently started having issues and happened to notice Samba was using 12GB+ of RAM. Found this post https://forums.freenas.org/index.php?th ... -ram.61039 and bug report https://redmine.ixsystems.com/issues/28585.

Adding

Code: Select all

unix extensions = no
wide links = yes

as additional parameters appears to have fixed it now as a workaround until they find more about the root cause.

Sounds like I ran into the same problem here on (rev 5127): https://www.nas4free.org/forums/viewtop ... 21&t=13505

I will be trying the two new smb4.conf addition tonight

[BodgeIT]

Upgraded on embedded, with no noticeable issues.
I'm still making sure to disable all extensions before upgrading. Seems to foster a much more reliable upgrade.

I checked memory useage. SMB only using 450Mb but applied the above workaround anyway.
Really don't want this system falling over while I'm not watching.

Thanks everybody!

[zoon01]

We released 5321 today, Disks/zfs/volumes tab now opens as it should.

[Viper780]

We released 5321 today, Disks/zfs/volumes tab now opens as it should.

I've tried the USB Live Image and it won't boot (Missing operation System!).
Used three different USB Sticks on two different PC's to flash (both Win10 withWin32DiskImager) and it won't boot.

Please check again

[raulfg3]

please use Etcher instead win32

[Viper780]

Etcher is really cool and good looking - didn't heard of it before.
unfortunately it is still the same - will try an older Nas4Free Img

[raulfg3]

well, perhaps your BIOS Order do not work well, do you test the boot disk on other PC's to see if somethings fails to your Motherboard BIOS order?

[Viper780]

No the boot devices in the Bios are ok.
The USB Sticks got messed uped while flashing. I've restored the Device ID and all of the partitions, flashed them again and now they work
Thx for your help and the recommendation for Etcher

[jwcasl]

I upgraded from 5019 to 5321 and have 2 issues:

1. when I modified my rysnc local entry and went to apply, I got a "Fatal error: Uncaught Error: Call to undefined method co_sphere_grid::notifier_processor() in /usr/local/www/services_rsyncd_local.php:92 Stack trace: #0 {main} thrown in /usr/local/www/services_rsyncd_local.php on line 92"

2. SMB: I can see my shares, but when I tried to connect to a share, I get a cannot connect, check server name or ip address error.

on 5019 both of these were working fine. Nothing was changed from 5019. I'm running embedded.

Thanks for looking into this and providing this great software.

[ms49434]

I upgraded from 5019 to 5321 and have 2 issues:

1. when I modified my rysnc local entry and went to apply, I got a "Fatal error: Uncaught Error: Call to undefined method co_sphere_grid::notifier_processor() in /usr/local/www/services_rsyncd_local.php:92 Stack trace: #0 {main} thrown in /usr/local/www/services_rsyncd_local.php on line 92"
Thanks for looking into this and providing this great software.

I cannot replicate your issue. There has been a change in method naming with commit 5186 (co_sphere.php) and the related commit 5215 (service_rsyncd_local.php).
My guess is that your upgrade to 5321 wasn't successful. You should backup your configuration and perform a new installation.

Please amend your signature so we don't need to ask if you are on embedded or full installation etc.

[apollo567]

Just discovered (first time) with Version 5321 the Smart reporting for the Disks connected to my Dell PERC H310 (no IT Mode Flash !) doesn't work anymore.
Where there some changes which could result in such behaivior?