XigmaNAS

typhon wrote: ↑

23 Sep 2019 10:33

I did an upgrade from Version 11.2.0.4.6862 to this new Version and now the console menu appears only after login. Is it a security feature or went something wrong?

Name: ttyv0_autologin
Command: /usr/bin/sed -i.bak -e "/^ttyv0/ s/Pc/autologin/" /etc/ttys
Comment: Autologin Console
Type: PreInit

ms49434 wrote: ↑

23 Sep 2019 10:46

It was changed for security reasons. Some users weren't aware that console access was possible without providing login details.
You can restore the old behaviour by adding a small command script in System > Advanced > Command Scripts:

Code: Select all

Name: ttyv0_autologin
Command: /usr/bin/sed -i.bak -e "/^ttyv0/ s/Pc/autologin/" /etc/ttys
Comment: Autologin Console
Type: PreInit

bewoco wrote: ↑

23 Sep 2019 20:54

Comparing the 6881 release notes of 11.2 and 12.0 branches, the 12.0 changes include the python update to 3.6, what is missing for 11.2.
Is this correct or does the python update is only missing in the corresponding list?

cookiemonster wrote: ↑

24 Sep 2019 01:14

Nice. May I suggest to add to the release notes the unison version? Unison requires both client and server to be on the same major version, and building with ui everytime on my sync clients is inconvenient. I always end up resolving new dependencies client side, and I haven't figured out how ubuntu uses the alternatives mechanism to link "latest" (their naming) to the newly built version and integrate it to the menus, so I end up having to call it with aliases and some voodoo that lacks system integration due to my lack of time.
With the version on the release notes I could prepare for it or delay XigmaNAS upgrade until I have the time to redo that.

jamaroney wrote: ↑

23 Sep 2019 13:00

ms49434 wrote: ↑

23 Sep 2019 10:46

It was changed for security reasons. Some users weren't aware that console access was possible without providing login details.
You can restore the old behaviour by adding a small command script in System > Advanced > Command Scripts:

Code: Select all

Name: ttyv0_autologin
Command: /usr/bin/sed -i.bak -e "/^ttyv0/ s/Pc/autologin/" /etc/ttys
Comment: Autologin Console
Type: PreInit

Thanks for that command. May I suggest putting a "no-login console access" option in the "Advanced Setup" in future releases?

ms49434 wrote: ↑

25 Sep 2019 02:20

The option to enable autologin has been added to the System > Advanced page.
Sourceforge commit 6899

zoon01 wrote: ↑

24 Sep 2019 01:44

cookiemonster wrote: ↑

24 Sep 2019 01:14

Nice. May I suggest to add to the release notes the unison version? Unison requires both client and server to be on the same major version, and building with ui everytime on my sync clients is inconvenient. I always end up resolving new dependencies client side, and I haven't figured out how ubuntu uses the alternatives mechanism to link "latest" (their naming) to the newly built version and integrate it to the menus, so I end up having to call it with aliases and some voodoo that lacks system integration due to my lack of time.
With the version on the release notes I could prepare for it or delay XigmaNAS upgrade until I have the time to redo that.

bcpierce00-unison-v2.51.2_GH0.tar.gz is used

jamaroney wrote: ↑

25 Sep 2019 04:36

ms49434 wrote: ↑

25 Sep 2019 02:20

The option to enable autologin has been added to the System > Advanced page.
Sourceforge commit 6899

Super - thanks!

ExTruckie wrote: ↑

03 Oct 2019 03:28

jamaroney wrote: ↑

25 Sep 2019 04:36

ms49434 wrote: ↑

25 Sep 2019 02:20

The option to enable autologin has been added to the System > Advanced page.
Sourceforge commit 6899

Super - thanks!

Could you add a small tutorial on how to enter the new code? Or at least hold my hand. Cmd line is not my strongest thing and I am just not 100% sure where and how.
Thank you in advance

raulfg3 wrote: ↑

03 Oct 2019 09:50

Best is to wait until new release offers this like on/off button.

Uzi wrote: ↑

03 Oct 2019 23:06

So far one successful update here. The second system will hopefully follow within a few days.

I noticed two things though:
1.) It seems that after login for the console menu there seems no way to log out of it.
2.) I never really took a deeper look at it but there is a difference between the "CPU Usage" in System Information and the "CPU Load" in Status - Monitoring. While CPU Usage is mostly in the single digit range, the CPU Load (both during file transfers) is around 80-90%. What's the difference between the two?

apollo567 wrote: ↑

05 Oct 2019 17:32

Hello,

under Status-Monitoring Screen I have since the latest version a CPU usage of around 90% where as under Status-System Screen the overall CPU-Load is quite low. Might there be an calculation errror in the Monitor screen ? In previous versions the CPU usage was always quite low.

ms49434 wrote: ↑

05 Oct 2019 17:45

[
Bug 403 has been already fixed and will be available in the next release.

nasrocks wrote: ↑

24 Sep 2019 03:00

I found the solution on the german Xigmanas forum. I had extended GUI turned off before I installed this version but was able to login via another page and I had to uninstall the extended GUI for it to work.

gimeumeu wrote: ↑

07 Oct 2019 18:19

nasrocks wrote: ↑

24 Sep 2019 03:00

I found the solution on the german Xigmanas forum. I had extended GUI turned off before I installed this version but was able to login via another page and I had to uninstall the extended GUI for it to work.

hi
I have the same problem (Fatal error: Cannot redeclare get_upsinfo() (previously declared in /usr/local/www/index.php:145) in /etc/inc/system.inc on line 898 ).
Could you give me the link to another page of the web server where the connection is possible.
Tanks.
gimeumeu

ms49434 wrote: ↑

07 Oct 2019 18:44

gimeumeu wrote: ↑

07 Oct 2019 18:19

nasrocks wrote: ↑

24 Sep 2019 03:00

I found the solution on the german Xigmanas forum. I had extended GUI turned off before I installed this version but was able to login via another page and I had to uninstall the extended GUI for it to work.

hi
I have the same problem (Fatal error: Cannot redeclare get_upsinfo() (previously declared in /usr/local/www/index.php:145) in /etc/inc/system.inc on line 898 ).
Could you give me the link to another page of the web server where the connection is possible.
Tanks.
gimeumeu

[protocol]://[ip-address or name of your NAS]/notavailable.php, i.e. https://192.168.0.222/notavailable.php

Do NOT upgrade servers on lower versions than XigmaNAS 11.2.0.4.6625

ginggs wrote: ↑

29 Oct 2019 15:41

I noticed in the release notes for 12.0.0.4:

Do NOT upgrade servers on lower versions than XigmaNAS 11.2.0.4.6625

My server has 11.2.0.4.6400 so I thought I had better upgrade to the latest 11.2.0.4 build.
Looking on:
https://sourceforge.net/projects/xigman ... .0.4.6881/
There is no XigmaNAS-x64-embedded-11.2.0.4.6881.img.xz file.

There is a XigmaNAS-x64-embedded-11.2.0.4.7014.img.xz, but this actually appears to be 11.3.04.

ms49434 wrote: ↑

29 Oct 2019 15:55

FreeBSD 11.2 is end of life, it is recommended to upgrade to 11.3.
Because you are running an older version, you should backup your configuration, create a new boot media with the help of the ISO/USB image and restore your configuration after a successful boot with the new release.
The new boot media is required because of a change in partition sizes.

XigmaNAS-x64-embedded-11.2.0.4.7014.img.xz 	2019-10-18
readme_11.2.txt 				2019-10-03
changes_after_6766_release_11.2.txt 		2019-09-22
XigmaNAS-x64-LiveCD-11.2.0.4.6881.iso 		2019-09-22
XigmaNAS-x64-LiveUSB-GPT-11.2.0.4.6881.img.gz 	2019-09-22
XigmaNAS-x64-LiveUSB-MBR-11.2.0.4.6881.img.gz 	2019-09-22
XigmaNAS-x64-full-11.2.0.4.6881.tgz 		2019-09-22
XigmaNAS-x64-11.2.0.4.6881.SHA512-CHECKSUM 	2019-09-22