XigmaNAS 11.2.0.4.6536 released (FreeBSD 11.2-RELEASE-P9)

[zoon01]

We are pleased to announce the release of XigmaNAS version 11.2.0.4.6536 - Omnius.

First BACKUP your current Configuration!
READ readme_11.2.txt please before you do anything!

Download build 11.2.0.4.6536

Changes after release 11.2.0.4.6400
======================
- Upgrade FreeBSD 11.2-RELEASE to P9.
- Update translations.
- Removed novnc from webgui.
- Add detailed encryption and authentication algorithm.
- WebGUI code & framework improvements.
- Upgrade msmtp to 1.8.3.
- Upgrade bash to 5.0 p2.
- Upgrade phpmyadmin to 4.8.5.
- Upgrade lighttpd to 1.4.53.
- Upgrade virtualbox-ose to 5.2.26.
- Upgrade libvncserver to 0.9.12.
- Upgrade samba to 4.8.9.
- Upgrade php to 7.3.2.
- Upgrade APCu to 5.1.17.
- Upgrade dialog to 1.3-20190211.
- Upgrade arcconf to 3.00.23488.
- Upgrade smartmontools to 7.0.

fixes:
===
- Fix lockdown file access when hostallow is bypassed.
- Fix diag_log_settings.
- Fix delete orphaned pools.

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

Regards,
Team XigmaNAS

[rth]

Just tried upgrading to this from 11.2.0.4 - Omnius (revision 6400) using the embedded upgrade file. System says it is doing the upgrade but when I log in a few minutes later it has not rebooted and is still on old version. Do I need to reboot manually to enable the new version. Have tried doing the upgrade twice with the same result.

system is HP microserver x64-embedded on AMD Turion(tm) II Neo N40L with 2GB and 3 *2TB zfs array and 1 4TB disc

[zoon01]

Just tried upgrading to this from 11.2.0.4 - Omnius (revision 6400) using the embedded upgrade file. System says it is doing the upgrade but when I log in a few minutes later it has not rebooted and is still on old version. Do I need to reboot manually to enable the new version. Have tried doing the upgrade twice with the same result.

system is HP microserver x64-embedded on AMD Turion(tm) II Neo N40L with 2GB and 3 *2TB zfs array and 1 4TB disc

Please reboot your server and try flash embedded file again please.

[jamaroney]

Exact same circumstances for me as rth - 2 attempts at embedded upgrade from 6400 failed:

Right after the first attempt, I couldn't access the WebGUI page - my browser showed only this:

Warning: session_start(): open(/tmp/sess_08f33976dbd0de18f2c9449cf77fdf40, O_RDWR) failed: No space left on device (28) in /etc/inc/session.inc on line 52 Warning: session_start(): Failed to read session data: files (path: /tmp) in /etc/inc/session.inc on line 52 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/session.inc:52) in /usr/local/www/auth.inc on line 39

So, I rebooted via SSH.

After second upgrade attempt, I could access the WebGUI. But the log showed this:

Feb 22 06:07:06 nas4free kernel: (da2:umass-sim2:2:0:0): Error 5, Retries exhausted
Feb 22 06:07:06 nas4free kernel: (da2:umass-sim2:2:0:0): CAM status: CCB request completed with an error
Feb 22 06:07:06 nas4free kernel: (da2:umass-sim2:2:0:0): WRITE(10). CDB: 2a 00 00 01 ba 80 00 00 40 00
Feb 22 06:07:01 nas4free kernel: (da2:umass-sim2:2:0:0): Retrying command
Feb 22 06:07:01 nas4free kernel: (da2:umass-sim2:2:0:0): CAM status: CCB request completed with an error
Feb 22 06:07:01 nas4free kernel: (da2:umass-sim2:2:0:0): WRITE(10). CDB: 2a 00 00 01 ba 80 00 00 40 00
Feb 22 06:06:55 nas4free kernel: (da2:umass-sim2:2:0:0): Retrying command
Feb 22 06:06:55 nas4free kernel: (da2:umass-sim2:2:0:0): CAM status: CCB request completed with an error
Feb 22 06:06:55 nas4free kernel: (da2:umass-sim2:2:0:0): WRITE(10). CDB: 2a 00 00 01 ba 80 00 00 40 00
Feb 22 06:06:50 nas4free kernel: (da2:umass-sim2:2:0:0): Retrying command
Feb 22 06:06:50 nas4free kernel: (da2:umass-sim2:2:0:0): CAM status: CCB request completed with an error
Feb 22 06:06:50 nas4free kernel: (da2:umass-sim2:2:0:0): WRITE(10). CDB: 2a 00 00 01 ba 80 00 00 40 00
Feb 22 06:06:44 nas4free kernel: (da2:umass-sim2:2:0:0): Retrying command
Feb 22 06:06:44 nas4free kernel: (da2:umass-sim2:2:0:0): CAM status: CCB request completed with an error
Feb 22 06:06:44 nas4free kernel: (da2:umass-sim2:2:0:0): WRITE(10). CDB: 2a 00 00 01 ba 80 00 00 40 00

[raulfg3]

Exact same circumstances for me as rth - 2 attempts at embedded upgrade from 6400 failed:

Right after the first attempt, I couldn't access the WebGUI page - my browser showed only this:

Warning: session_start(): open(/tmp/sess_08f33976dbd0de18f2c9449cf77fdf40, O_RDWR) failed: No space left on device (28) in /etc/inc/session.inc on line 52 Warning: session_start(): Failed to read session data: files (path: /tmp) in /etc/inc/session.inc on line 52 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/session.inc:52) in /usr/local/www/auth.inc on line 39

So, I rebooted via SSH.

After second upgrade attempt, I could access the WebGUI. But the log showed this:

Feb 22 06:07:06 nas4free kernel: (da2:umass-sim2:2:0:0): Error 5, Retries exhausted
Feb 22 06:07:06 nas4free kernel: (da2:umass-sim2:2:0:0): CAM status: CCB request completed with an error
Feb 22 06:07:06 nas4free kernel: (da2:umass-sim2:2:0:0): WRITE(10). CDB: 2a 00 00 01 ba 80 00 00 40 00
Feb 22 06:07:01 nas4free kernel: (da2:umass-sim2:2:0:0): Retrying command
Feb 22 06:07:01 nas4free kernel: (da2:umass-sim2:2:0:0): CAM status: CCB request completed with an error
Feb 22 06:07:01 nas4free kernel: (da2:umass-sim2:2:0:0): WRITE(10). CDB: 2a 00 00 01 ba 80 00 00 40 00
Feb 22 06:06:55 nas4free kernel: (da2:umass-sim2:2:0:0): Retrying command
Feb 22 06:06:55 nas4free kernel: (da2:umass-sim2:2:0:0): CAM status: CCB request completed with an error
Feb 22 06:06:55 nas4free kernel: (da2:umass-sim2:2:0:0): WRITE(10). CDB: 2a 00 00 01 ba 80 00 00 40 00
Feb 22 06:06:50 nas4free kernel: (da2:umass-sim2:2:0:0): Retrying command
Feb 22 06:06:50 nas4free kernel: (da2:umass-sim2:2:0:0): CAM status: CCB request completed with an error
Feb 22 06:06:50 nas4free kernel: (da2:umass-sim2:2:0:0): WRITE(10). CDB: 2a 00 00 01 ba 80 00 00 40 00
Feb 22 06:06:44 nas4free kernel: (da2:umass-sim2:2:0:0): Retrying command
Feb 22 06:06:44 nas4free kernel: (da2:umass-sim2:2:0:0): CAM status: CCB request completed with an error
Feb 22 06:06:44 nas4free kernel: (da2:umass-sim2:2:0:0): WRITE(10). CDB: 2a 00 00 01 ba 80 00 00 40 00

Errros are related to HD, revise cables and unplug & plug to solve

PD: I dout that your errors are related to new release.

[provels]

Embedded upgrade went fine for me, but Log Settings boxes are grayed out and Log Entries field not editable.
Tried 2 browsers and cleared cache. Just FYI.

Capture.PNG

[ms49434]

Embedded upgrade went fine for me, but Log Settings boxes are grayed out and Log Entries field not editable.
Tried 2 browsers and cleared cache. Just FYI.
Capture.PNG

Just click on the edit button in the lower left corner:

diag_log_settings.png

If you feel that the edit button is too far away you can let it display right under the form, just enable checkbox Button Location:

system_advanced2.png

... and the button will be displayed at the end of the lighter area:

diag_log_settings2.png

If you think you don't need this additional protection against unwanted input at all you can enable Skip View Mode:

system_advanced.png

[provels]

OK, no problem then. Is that new? Seems a little inconsistent with other config pages, just asking, not complaining.

[ms49434]

OK, no problem then. Is that new? Seems a little inconsistent with other config pages, just asking, not complaining.

it's there since 2 years. To support the new layout, most pages require a full rewrite.

[KTL]

Thanks, used the RootOnZFS WebGUI firmware upgrade method to 6536 without problems.

[provels]

it's there since 2 years. To support the new layout, most pages require a full rewrite.

OK, LOL @ moi!

[Snufkin]

Embedded upgrade from 6400 to 6536 went smoothly.
Many thanks to XNAS development team for their excellent work!

Latest PHP 7.3 brought a couple of small bugs in Nextcloud extension.

1. smbclient PHP extension package should be upgraded.

   Code: Select all

   php72-pecl-smbclient-0.9.0_4
   php73-pecl-smbclient-1.0.0

   Just waiting for Crest to update the extension.
2. Nextcloud PHP code needs to be updated as well to fix following error.

   Code: Select all

   FastCGI-stderr: PHP Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"?
   in /persistent/path/webserver/nextcloud/3rdparty/sabre/dav/lib/CalDAV/ICSExportPlugin.php on line 321

   Hot fix could be found in Nextcloud forum thread

   It’s a warning caused by an semi-experimental deprecation in php 7.3. To eliminate the warning simply follow its suggestion - and the explicit “continue 2” is supported in previous php versions and clarifies the intent anyway which is always A Good Thing.

   Just waiting for Nextcloud developers to update their code.

[ExTruckie]

Upgraded to Ver.6536 Looked over and operates normally in my configuration.

I did notice that the home screen shows the running version as a beta

Did I get the wrong file?

[KTL]

The release version is 11.2.0.4.6536, looks like you grabbed 12.0.0.4.6536, which is the BETA version.

[rth]

Tried embedded install again and this time the server did reboot and correctly installed 11.2.0.4.6536 version. Seems to be working ok now and backup to server working properly.

[ExTruckie]

The release version is 11.2.0.4.6536, looks like you grabbed 12.0.0.4.6536, which is the BETA version.

Ha, the laugh is on me I followed the link at the top of the pace for the release. looks like they are switched.

Getting the proper one

[jerryone]

Upgrade complete without any problems! Keep up the great work. Many thanks!

[Eagle_42]

Upgraded from 6400, no issues so far.

[Chucko]

I have a problem with adding variables to sysctl.conf via the web GUI. Every time I hit the 'Add' button I get an error page with the following message:

Fatal error: Uncaught Error: Call to a member function execute() on bool in /etc/inc/updatenotify.inc:105 Stack trace: #0 /usr/local/www/system_sysctl_edit.php(199): updatenotify_set('sysctl', 0, '2e467101-61fd-4...') #1 {main} thrown in /etc/inc/updatenotify.inc on line 105

Not a show-stopper, but as I have a bunch of stuff customized in sysctl.conf, I would like to be able to continue adding variables.

A similar problem was encountered adding variables to loader.conf.

[ms49434]

I have a problem with adding variables to sysctl.conf via the web GUI. Every time I hit the 'Add' button I get an error page with the following message:

Fatal error: Uncaught Error: Call to a member function execute() on bool in /etc/inc/updatenotify.inc:105 Stack trace: #0 /usr/local/www/system_sysctl_edit.php(199): updatenotify_set('sysctl', 0, '2e467101-61fd-4...') #1 {main} thrown in /etc/inc/updatenotify.inc on line 105

Not a show-stopper, but as I have a bunch of stuff customized in sysctl.conf, I would like to be able to continue adding variables.

A similar problem was encountered adding variables to loader.conf.

The database which is storing the update notifications (sqlite) has an invalid format.
Please delete the database, the full path/filename is /var/db/updatenotify.db or from the WebGUI, go to Tools Command and paste the below command into the PHP command field and press execute:

Code: Select all

unlink(UPDATENOTIFY_DB);

[Chucko]

Thank you, that fixed it!

I have a problem with adding variables to sysctl.conf via the web GUI. Every time I hit the 'Add' button I get an error page with the following message:

Fatal error: Uncaught Error: Call to a member function execute() on bool in /etc/inc/updatenotify.inc:105 Stack trace: #0 /usr/local/www/system_sysctl_edit.php(199): updatenotify_set('sysctl', 0, '2e467101-61fd-4...') #1 {main} thrown in /etc/inc/updatenotify.inc on line 105

Not a show-stopper, but as I have a bunch of stuff customized in sysctl.conf, I would like to be able to continue adding variables.

A similar problem was encountered adding variables to loader.conf.

The database which is storing the update notifications (sqlite) has an invalid format.
Please delete the database, the full path/filename is /var/db/updatenotify.db or from the WebGUI, go to Tools Command and paste the below command into the PHP command field and press execute:

Code: Select all

unlink(UPDATENOTIFY_DB);

[nasrocks]

@jamaroney I know this is an old thread but I am getting a similar message to yours.

See below. Can you let me know what the fix was.

Warning: session_start(): open(/tmp/sess_4d4qh6u0jpspr3a4tp5nlcitvi0lavg9bbo380fok1dan4mn, O_RDWR) failed: No space left on device (28) in /etc/inc/session.inc on line 52 Warning: session_start(): Failed to read session data: files (path: /tmp) in /etc/inc/session.inc on line 52 Warning: Cannot modify header information - headers already sent by (output started at /etc/inc/session.inc:52) in /usr/local/www/auth.inc on line 39


Thanks