XigmaNAS 11.2.0.4.6743 released (FreeBSD 11.2-RELEASE-P10)

[zoon01]

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

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

Download build 11.2.0.4.6743

- Upgrade FreeBSD 11.2-RELEASE to P10.
- Update translations.
- WebGUI code & framework improvements.
- Add script for root authorized_keys installation.
- Add RootOnZFS RAID10 install option.
- Add RootOnZFS MBR install option.
- Add RootOnZFS old kernel retrieval on upgrades.
- Add RootOnZFS device shifting immunity.
- Upgrade syncthing to 1.1.3.
- Upgrade bash to 5.0 p7.
- Upgrade msmtp to 1.8.4.
- Upgrade nano to 4.2.
- Upgrade tmux to 2.9a.
- Upgrade jQuery to 3.4.1.
- Upgrade samba to 4.8.12.
- Upgrade php to 7.3.6.
- Upgrade lighttpd to 1.4.54.
- Upgrade virtualbox-ose to 5.2.30.
- Upgrade e2fsprogs to 1.45.2.
- Upgrade beadm to 1.3.0.
- Upgrade phpmyadmin to 4.9.0.
- Upgrade syncthing to 1.1.4.
- Upgrade devcpu-data to 1.22.

fixes:
===
- Fix missing single quote character.
- Fix password bug after changing permissions.

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

[karlandtanya]

Easy upgrade, thanks very much!
However dnsmasq service won't start now.

[zoon01]

Easy upgrade, thanks very much!
However dnsmasq service won't start now.

Sorry to read your issue, be aware that this is extension related issue, on that we do not have any control.

[karlandtanya]

Easy upgrade, thanks very much!
However dnsmasq service won't start now.

Sorry to read your issue, be aware that this is extension related issue, on that we do not have any control.

Thanks for the quick reply! Sorry for "who touched it last".
FWIW, dnsmasq wanted libidn.so.11, but seems to work ok if I just tell it to use .12.

[lindsay]

Solved

[KTL]

Thanks for the release, updated from 6625 w/o issues.

[netware5]

Successfully upgraded via WebGui from 6625 to 6743. The only matter of concern are the following lines in the log:

Code: Select all

Jun 9 18:41:14	kernel:	Firmware Warning (ACPI): Invalid length for FADT/Pm2ControlBlock: 32, using default 8 (20171214/tbfadt-850)
Jun 9 18:41:14	kernel:	Firmware Warning (ACPI): Invalid length for FADT/Pm1aControlBlock: 32, using default 16 (20171214/tbfadt-850)
Jun 9 18:41:14	kernel:	Firmware Warning (ACPI): 32/64X length mismatch in FADT/Pm2ControlBlock: 8/32 (20171214/tbfadt-748)
Jun 9 18:41:14	kernel:	Firmware Warning (ACPI): 32/64X length mismatch in FADT/Pm1aControlBlock: 16/32 (20171214/tbfadt-748)

and also this one:

Code: Select all

Jun 9 18:41:21	root:	/etc/rc: WARNING: failed to start nut_upsmon

[netware5]

Unfortunately my previous post was wrong. The nut_upsmon problem persists even after fresh installation from LiveCD. So I reverted back to 6625. Will wait until the issue is fixed.

[ms49434]

Unfortunately my previous post was wrong. The nut_upsmon problem persists even after fresh installation from LiveCD. So I reverted back to 6625. Will wait until the issue is fixed.

would it be possible for you to post the output of

Code: Select all

# service nut_upsmon start

Does your master username or master password contain spaces?

[netware5]

Unfortunately my previous post was wrong. The nut_upsmon problem persists even after fresh installation from LiveCD. So I reverted back to 6625. Will wait until the issue is fixed.

would it be possible for you to post the output of

Code: Select all

# service nut_upsmon start

Does your master username or master password contain spaces?

My master username and password (under UPS service menu) do not contain spaces. In fact they are default - root and no password.

The output you asked for is:

Code: Select all

service nut_upsmon start
Starting nut_upsmon.
Network UPS Tools upsmon 2.7.4
fopen /var/run/upsmon.pid: No such file or directory
/var/etc/upsmon.conf line 1: invalid directive MONITOR BackUPSES550@localhost 1 master
Using power down flag file /var/etc/killpower

Fatal error: insufficient power configured!

Sum of power values........: 0
Minimum value (MINSUPPLIES): 1

Edit your upsmon.conf and change the values.
/etc/rc.d/nut_upsmon: WARNING: failed to start nut_upsmon

When reverting back to 6625 and restoring the same backup config everything is fine.

[ms49434]

Unfortunately my previous post was wrong. The nut_upsmon problem persists even after fresh installation from LiveCD. So I reverted back to 6625. Will wait until the issue is fixed.

would it be possible for you to post the output of

Code: Select all

# service nut_upsmon start

Does your master username or master password contain spaces?

My master username and password (under UPS service menu) do not contain spaces. In fact they are default - root and no password.

The output you asked for is:

Code: Select all

service nut_upsmon start
Starting nut_upsmon.
Network UPS Tools upsmon 2.7.4
fopen /var/run/upsmon.pid: No such file or directory
/var/etc/upsmon.conf line 1: invalid directive MONITOR BackUPSES550@localhost 1 master
Using power down flag file /var/etc/killpower

Fatal error: insufficient power configured!

Sum of power values........: 0
Minimum value (MINSUPPLIES): 1

Edit your upsmon.conf and change the values.
/etc/rc.d/nut_upsmon: WARNING: failed to start nut_upsmon

When reverting back to 6625 and restoring the same backup config everything is fine.

please reenter master user and master password in 6743, they seem to be emtpy, therefore the MONITOR directive is failing.

[netware5]

please reenter master user and master password in 6743, they seem to be emtpy, therefore the MONITOR directive is failing.

Thank you, ms49434!

Everything is fine now! I'm just wondering why it happened - till now I had no problem with my empty ups master password.

I am also concerned about these lines in boot log and system log:

Capture.PNG

Code: Select all

Jun 12 00:07:58	kernel:	Firmware Warning (ACPI): Invalid length for FADT/Pm2ControlBlock: 32, using default 8 (20171214/tbfadt-850)
Jun 12 00:07:58	kernel:	Firmware Warning (ACPI): Invalid length for FADT/Pm1aControlBlock: 32, using default 16 (20171214/tbfadt-850)
Jun 12 00:07:58	kernel:	Firmware Warning (ACPI): 32/64X length mismatch in FADT/Pm2ControlBlock: 8/32 (20171214/tbfadt-748)
Jun 12 00:07:58	kernel:	Firmware Warning (ACPI): 32/64X length mismatch in FADT/Pm1aControlBlock: 16/32 (20171214/tbfadt-748)

[gustar]

I've got the same issue
"Failed to start service nut_upsmon" master user and master password reentered and it did not help

[typhon]

The upgrade for embedded on HP Proliant Microserver Gen8 from 6625 to 6743 went fine. But it had problems with updating time with ntp at boot and nut did not start on every boot. To solve the problem I had to enable "netwait" in rc.conf.

[igr4free]

updated from 6625 with out issues. very fast upgrade with RootOnZFS firmware upgrade menu.

[biggsy]

Upgrades from 6625 to 4743 went very smoothly on two ESXi VMs (Gen8 and Gen10) and one bare metal install on Gen8.

Only small gotcha was with the new public key stuff as resolved in this thread, thanks to expert assistance from ms49434.