eschultz

Version 6.3.0-rc3 Release Notes

Recommended Posts

unRAID OS version 6.3 is primarily a bug fix and package "catch up" release.  There is one interesting new feature:

 

Please refer to change log below for list of updated components.

 

unRAID Server OS Change Log
===========================

Version 6.3.0-rc3 2016-10-22
----------------------------

Linux kernel:

- version 4.8.4 (CVE-2016-5195)

Management:

- shutdown: additional logging in event of cmdStop timeout

Version 6.3.0-rc2 2016-10-19
----------------------------

Base distro:

- docker: version 1.12.2
- containerd: version 0.2.4
- runc: version 1.0.0_rc2
- libseccomp: version 2.3.1
- libvirt-php: 0.5.2 (+ latest from git)
- php: version 7.0.12
- usbredir: version 0.7.1
- spice: version 0.12.8
- spice-protocol: version 0.12.12
- imlib2: version 1.4.9
- gd: version 2.2.3
- rsyslog: version 8.22.0
- libfastjson: version 0.99.4
- reverted OVMF firmware back to the version in 6.2 due to user reported issues

Linux kernel:

- version 4.8.2
- r750: version 1.2.10-16_10_13

Management:

- bug fix: Samba listening on the wrong interface in a VLAN-enable config
- emhttp: added starting/stopping docker/libvirt events
- emhttp: removed 'reboot', 'shutdown', 'changeNetwork' API calls; eliminated emhttp-managed network vars
- md/unraid: kernel 4.8 API changes; support FUA and SYNC write operation flags
- shutdown: save diagnostics in event of cmdStop timeout
- vm manager: add 'virtio-win-0.1.126-2' and 'virtio-win-0.1.126-1' to VirtIO-ISOs list
- webGui: Added "Join" notification agent
- webGui: Add support for "Notify My Android" notifications
- webGui: Fixed: Windows unable to extract diagnostics zip file
- webGui: Increased password length to 128 characters
- webGui: Interactive Reboot and Shutdown directly invokes '/sbin/reboot' and '/sbin/poweroff'

Version 6.3.0-rc1 2016-10-05
----------------------------

Base distro (primary packages):

- btrfs-progs: version v4.7.2
- netatalk: version 3.1.10
- openssl: version 1.0.2j
- php: version 5.6.26
- qemu: version 2.7.0
- samba: version 4.5.0

Base distro (secondary packages):

- apcupsd: version 3.14.14
- bash: version 4.4.0
- curl: version 7.50.3
- diffutils: version 3.5
- e2fsprogs: version 1.43.3
- etc: version 14.2
- file: version 5.28
- fuse: version 2.9.7
- gawk: version 4.1.4
- gdbm: version 1.12
- glib2: version 2.46.2
- glibc: version 2.24
- glibc: version zoneinfo
- glibc-solibs: version 2.24
- gnutls: version 3.4.15
- jemalloc: version 4.2.1
- kmod: version 23
- libtasn1: version 4.9
- libxml2: version 2.9.4
- lvm2: version 2.02.161
- nano: version 2.7.0
- network-scripts: version 14.2
- nfs-utils: version 1.3.4
- openssl-solibs version: 1.0.2j
- pkgtools-14.2-noarch: version 13
- reiserfsprogs: version 3.6.25
- util-linux: version 2.28.2

Base distro (desktop GUI packages):

- freetype: version 2.6.5
- harfbuzz: version 1.3.0
- libXfont: version 1.5.2
- mesa: version 12.0.2
- mozilla-firefox: version 49.0.1
- xkeyboard-config: version 2.18
- xorg-server: version 1.18.4

Linux kernel:

- version 4.7.6
- aacraid: version 1.2.1-52011
- intel 10Gbit ethernet: revert to in-tree drivers
- r750: version 1.2.9-16_09_27

Management:

- bug fix: For file system type "auto", only attempt btrfs,xfs,reiserfs mounts.
- bug fix: For docker.img and libvirt.img, if path on /mnt/ check for mountpoint on any subdir component
- bug fix: During shutdown force continue if array stop taking too long.
- bug fix: Handle case in 'mover' where rsync may move a file but also return error status.
- md/unraid: Fix bug where case of no data disks improperly detected.
- webGui: Add "Shutdown time-out" control on Disk Settings page.
- webGui: bug fix: Cannot manually specify virtIO iso in VM settings
- webGui: other changes: refer to github commit log

Share this post


Link to post
Share on other sites

As always, no apparent problems  ;D

Share this post


Link to post
Share on other sites
- shutdown: additional logging in event of cmdStop timeout

 

I looked over the things that are logged.  Nice work!  This will help a lot.

Share this post


Link to post
Share on other sites

I just want to check but the shutdown extra information is the only real change in rc3? Just thinking i may skip this one and wait for the next....

 

Jamie

Share this post


Link to post
Share on other sites

And the Linux kernel update which includes a security fix.

 

Update it is....

 

Edit

Updated with no issues. I'm still getting the dynamix bug where telling it to start the array gets to "Starting Services" and sits there. This happens when i load it via the unraid built in firefox if that helps (havent tried it from another machine)

The array does start as does everything else it just never reloads the page once done or finishes off stating it is starting everything else

 

I don't think its a browser cache issue since a fresh reboot should have no cache in unraid, i opened the console using f12 to check for no javascript issues but nothing. Everything else is working great other than this. Not a huge issue but certainly not one a log file can point to

 

Jamie

Share this post


Link to post
Share on other sites

And the Linux kernel update which includes a security fix.

 

Update it is....

 

Edit

Updated with no issues. I'm still getting the dynamix bug where telling it to start the array gets to "Starting Services" and sits there. This happens when i load it via the unraid built in firefox if that helps (havent tried it from another machine)

The array does start as does everything else it just never reloads the page once done or finishes off stating it is starting everything else

 

I don't think its a browser cache issue since a fresh reboot should have no cache in unraid, i opened the console using f12 to check for no javascript issues but nothing. Everything else is working great other than this. Not a huge issue but certainly not one a log file can point to

 

Jamie

 

Yes, we are aware of this issue.  Not sure if we'll have a fix in for 6.3 or if 6.4 will have it, but we know exactly what you're talking about.  The big issue on our end is the same as what you are seeing; nothing prints to the browser console to help us debug it.  That said, we can figure it out given enough time and attention, so we'll do just that in the future.

Share this post


Link to post
Share on other sites

And the Linux kernel update which includes a security fix.

 

Update it is....

 

Edit

Updated with no issues. I'm still getting the dynamix bug where telling it to start the array gets to "Starting Services" and sits there. This happens when i load it via the unraid built in firefox if that helps (havent tried it from another machine)

The array does start as does everything else it just never reloads the page once done or finishes off stating it is starting everything else

 

I don't think its a browser cache issue since a fresh reboot should have no cache in unraid, i opened the console using f12 to check for no javascript issues but nothing. Everything else is working great other than this. Not a huge issue but certainly not one a log file can point to

 

Jamie

 

Yes, we are aware of this issue.  Not sure if we'll have a fix in for 6.3 or if 6.4 will have it, but we know exactly what you're talking about.  The big issue on our end is the same as what you are seeing; nothing prints to the browser console to help us debug it.  That said, we can figure it out given enough time and attention, so we'll do just that in the future.

 

Good to hear i'm not the only one to see it, there are a few of us web developers hear if there is anything we can look at that may help

 

Jamie

Share this post


Link to post
Share on other sites

If I wanted to upgrade from RC1 to RC3, but keep the new OVMF firmware only present in RC1, is it just a case of backing up

/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd

, upgrading and replacing that file post upgrade?

Or can i back it up and reference that file somewhere else? eg on my cache drive, or  a dedicated VM SSD i have mounted via the unassigned devices plugin?

Share this post


Link to post
Share on other sites

There's a bug when doing a new config, it only works if something is selected on "retain current configuration:", it doesn't with "none".

Share this post


Link to post
Share on other sites

There's a bug when doing a new config, it only works if something is selected on "retain current configuration:", it doesn't with "none".

 

I am a little confused ???

 

When "none" is selected it means no disks are remembered, basically starting from scratch. What part doesn't work?

 

 

Share this post


Link to post
Share on other sites

There's a bug when doing a new config, it only works if something is selected on "retain current configuration:", it doesn't with "none".

 

I am a little confused ???

 

When "none" is selected it means no disks are remembered, basically starting from scratch. What part doesn't work?

 

Array is not reset, all assignments remain as they were.

Share this post


Link to post
Share on other sites

There's a bug when doing a new config, it only works if something is selected on "retain current configuration:", it doesn't with "none".

 

I am a little confused ???

 

When "none" is selected it means no disks are remembered, basically starting from scratch. What part doesn't work?

 

Array is not reset, all assignments remain as they were.

 

I did a test on my test server, which is on 6.2.2 and selecting "none" clears the array as expected.

 

AFAIK 6.3.0-rc3 has the same implementation, did you observe this behavior only in rc3 or in 6.2 as well?

 

Share this post


Link to post
Share on other sites

AFAIK 6.3.0-rc3 has the same implementation, did you observe this behavior only in rc3 or in 6.2 as well?

 

Did some testing to confirm, works fine on 6.2, 6.2.1, 6.2.2, doesn't work on any 6.3 release, so it started with 6.3-rc1.

Share this post


Link to post
Share on other sites

AFAIK 6.3.0-rc3 has the same implementation, did you observe this behavior only in rc3 or in 6.2 as well?

 

Did some testing to confirm, works fine on 6.2, 6.2.1, 6.2.2, doesn't work on any 6.3 release, so it started with 6.3-rc1.

 

Thanks for testing.

 

Seems my memory is failing :o

 

I did make an update for 6.3.0 to overcome a possible race condition.

 

Found the bad part and made a correction.

 

Ps. It is available through Bleeding Edge plugin.

 

 

Share this post


Link to post
Share on other sites

Guys, I'm receiving loads of emhttp: HWADDR not found on my syslog.

 

Resubmit the network configuration did not helped.

 

I suspect one of your installed plugins (maybe IPMI ?) is trying to read the deprecated HWADDR value (see http://lime-technology.com/forum/index.php?topic=50244.0)

 

Nope. Removed all my plugins, cleaned up the /usr/local/emhttp/plugins directory and the message still appears. It's difficult to be a plugin, since they use the injected variable "$var" to get those values from server.

 

A search using grep on /usr/local/ only showed emhttp using HWADDR word.

Share this post


Link to post
Share on other sites

Weird, checked my syslog but don't have these messages.

 

Share this post


Link to post
Share on other sites

Guys, I'm receiving loads of emhttp: HWADDR not found on my syslog.

 

Resubmit the network configuration did not helped.

Right, sorry about that.  It's a bug fixed in -rc4.  It will show up if you have AFP enabled.

Share this post


Link to post
Share on other sites

Guys, I'm receiving loads of emhttp: HWADDR not found on my syslog.

 

Resubmit the network configuration did not helped.

Right, sorry about that.  It's a bug fixed in -rc4.  It will show up if you have AFP enabled.

 

I don't have AFP enabled and I didn't see the same entries in my syslog as gfjardim was, just for the record and to help troubleshooting.

Share this post


Link to post
Share on other sites

Not sure how long this has been an issue but have just noticed this on my docker page

 

Docker Containers
Basic View
Warning: array_map(): Argument #2 should be an array in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 942 Warning: array_map(): Argument #2 should be an array in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 942 Warning: implode(): Invalid arguments passed in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(300) : eval()'d code on line 171 Warning: implode(): Invalid arguments passed in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(300) : eval()'d code on line 171

 

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.