Jump to content

unRAID Server Release 6.1-rc4-x86_64 Available


limetech

Recommended Posts

If you are running 6.1-rc3 you should be able to click Check for Updates on the Plugins page to get this release.

 

Alternately, navigate to Plugins/Install Plugin and paste the following link into the box and click Install:

 

https://raw.githubusercontent.com/limetech/unRAIDServer-6.1-rc/master/unRAIDServer.plg

 

Changes here are to fix regressions introduced in -rc2/-rc3.  A note about these regressions: First of all a "regression" in this context means a change in software that breaks something that previously worked before.  The problems with notifications and certain other webGui functionality were introduced by my decision to plug "arbitrary command execution" holes in 6.1 release.  In hindsight this might have been handled better, and maybe even should have been a -beta series with this change.  I want to thank bonienl in particular, and other plugin authors for your patience and for not bringing out the pitchforks and torches.

 

Plugin authors: if you haven't already, please read release notes for 6.1-rc3 release:

http://lime-technology.com/forum/index.php?topic=42146.0

 

New users to 6.1-rc: please disable/enable notifications to get them working again.

 


 

unRAID Server Version 6.1-rc4 Release Notes
===============================================

Security Advisory updates (6.1-rc1)
-----------------------------------
- ntp: 4.2.8p3 (SSA:2015-188-03)
- openssl: 1.0.1p (SSA:2015-190-01)

Security Advisory updates (6.1-rc3)
-----------------------------------
- php: 5.4.43 (SSA:2015-198-02)

Other changes (6.1-rc1)
-----------------------
- btrfs-progs: version 4.1.0
- docker: version 1.7.1
- docker: less verbose logging by default
- emhttp: fix: let Pro start regardless of attached device count
- emhttp: bridge forward delay configurable
- emhttp: support disk share export Yes/No/Auto
- libvirt: version 1.2.17
- linux: version 4.1.1
- linux: support "Lite-On IT Corp. / Plextor M6e PCI Express SSD [Marvell 88SS9183] (rev 14)", see https://lkml.org/lkml/2015/2/2/226
- ntp: enable by default
- php: version 5.4.42
- php: enable pcntl
- smb: include linux "hidden" objects in directory listings
- unRAIDServer.plg: improvements in unRAID-5 update: ping google instead of local gateway to determine if network up
- vm.manager: support OpenELEC template
- webGui: include linux "hidden" objects in directory listings
- webGui: integrate latest dynamix changes; many changes, refer to github
- webGui: install key: accept pre-keyserver links to key files
- webGui: rearrange columns on Main page
    
Other changes (6.1-rc2)
-----------------------
- emhttp: properly handle non-rotational devices standby mode (ie, 'spindown')
- emhttp: require credentials on all accesses, not just webGui pages
- emhttp: get rid of passing arbitrary commands in URL
- webGui: added "Hide dot files" control on SMB Settings page
- webGui: fix issues with uploading thumbnails, banner
- webGui: fix notifications not initialized on reboot
- webGui: fix docker update regression introduced in 6.1-rc1

Other changes (6.1-rc3)
-----------------------
- avahi: supress "Invalid response packet from host" messages
- btrfs-progs: version 4.1.2
- emhttp: fix spindown regression introduced in -rc2.
- emhttp: fix problem not able to start multiple btrfs scrubs
- libvirt: version 1.2.18
- linux: version 4.1.5
- php: enable iconv per user request
- samba: version 4.1.19
- webGui: all '#command' and 'cmd' values must reference scripts within /usr/local/emhttp/ jail.
- webGui: fix image upload issues
- webGui: Disable Array Stop button when mover is running
- webGui: Fixed memory max display in dashboard
- webGui: VM Manger: Updated noVNC (using latest as of 8/5/15, commit 8f3c0f6)
- webGui: Replace alert-box for SweetAlert (enhanced messaging)
- webGui: additional options for text/graphical display of Used/Free.
- webGui: Add APCUPS summary to dashboard page
- webGui: other misc. bug fixes
- OpenELEC VM template: Fix: allow spaces and quotes in download folder
- OpenELEC: added 6.0-beta3 image (beta3 includes hdmi sound fixes for nvidia cards and corrected 'addon_url' to allow plugins in Kodi once again)
- OpenELEC: use readonly for openelec disk image

Other changes (6.1-rc4)
-----------------------
- webGui: fix monitor/notification regressions resulting from closing 'arbitrary command execution' holes

 

 

Link to comment

Right... and now I have introduced a regression error: it erroneously reports Deprecated absolute #command path when the command is correct instead of a not allowed absolute path.

 

(detail in update.php)

 

if (strpos($command, $docroot) !== 0)

 

should be

 

if (strpos($command, $docroot) === 0)

 

Sorry!

 

Ps. This has no impact on the execution (just the reporting)!

 

Link to comment

I'm trying to start a Docker.  It won't start and I get the following in the log.

 

Aug 15 17:39:56 Tower php: Deprecated absolute #command path: /plugins/dynamix.docker.manager/scripts/docker start Maria-WebSQL
Aug 15 17:39:56 Tower php: /plugins/dynamix.docker.manager/scripts/docker start Maria-WebSQL

 

EDIT: Update also fails.

 

Aug 15 17:45:39 Tower php: Deprecated absolute #command path: /plugins/dynamix.docker.manager/scripts/dockerupdate.php
Aug 15 17:45:39 Tower php: /plugins/dynamix.docker.manager/scripts/dockerupdate.php

 

All related to the new jail commands I suspect.

Link to comment

I'm trying to start a Docker.  It won't start and I get the following in the log.

 

Aug 15 17:39:56 Tower php: Deprecated absolute #command path: /plugins/dynamix.docker.manager/scripts/docker start Maria-WebSQL
Aug 15 17:39:56 Tower php: /plugins/dynamix.docker.manager/scripts/docker start Maria-WebSQL

 

EDIT: Update also fails.

 

Aug 15 17:45:39 Tower php: Deprecated absolute #command path: /plugins/dynamix.docker.manager/scripts/dockerupdate.php
Aug 15 17:45:39 Tower php: /plugins/dynamix.docker.manager/scripts/dockerupdate.php

 

All related to the new jail commands I suspect.

 

that looks suspiciously like one of my dockers, lol.

Link to comment

I'm trying to start a Docker.  It won't start and I get the following in the log.

 

Aug 15 17:39:56 Tower php: Deprecated absolute #command path: /plugins/dynamix.docker.manager/scripts/docker start Maria-WebSQL
Aug 15 17:39:56 Tower php: /plugins/dynamix.docker.manager/scripts/docker start Maria-WebSQL

 

EDIT: Update also fails.

 

Aug 15 17:45:39 Tower php: Deprecated absolute #command path: /plugins/dynamix.docker.manager/scripts/dockerupdate.php
Aug 15 17:45:39 Tower php: /plugins/dynamix.docker.manager/scripts/dockerupdate.php

 

All related to the new jail commands I suspect.

 

These are just reporting warnings,  the commands are working correctly

 

Right... and now I have introduced a regression error: it erroneously reports Deprecated absolute #command path when the command is correct instead of a not allowed absolute path.

 

(detail in update.php)

 

if (strpos($command, $docroot) !== 0)

 

should be

 

if (strpos($command, $docroot) === 0)

 

Sorry!

 

Ps. This has no impact on the execution (just the reporting)!

 

Link to comment

Maybe they are just warnings, but I can't start a Docker or check for updates to Dockers on my test server.

 

Interesting ,  auto start dockers start up fine,  but manually starting them fails.  I thought possibly this issue had cropped back up http://lime-technology.com/forum/index.php?topic=41741  but the fix for that does not work

 

root@Tower:~# chmod +x /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerUpdate.php
chmod: cannot access ‚ /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerUpdate.php‚ : No such file or directory

Link to comment

I have a question about the upcoming dual parity that influences my current hard drive purchases. Will the parity drives have to be the same size? For example, if my largest data drive is 4TB, can I have a 4TB and a 5TB parity drive?

 

I'm guessing they can be mismatched an the extra 1 TB will be unused, but I just wanted to get a confirmation on this before I purchase new drives.

Link to comment

upgraded from 6.0-rc2 to 6.1-rc4 so that I could try the openelec vm. Everything appeared to go smoothly with the boot and array coming back online. Dockers all started automatically.

 

Strange thing was that when I went into VM's to start my Win10 (with GPU passthrough GTX970) HTPC VM it did not do anything. Nothing appeared on the main system log in relation to the time that I attempted to start the VM. I needed that VM up and running so I reverted back to 6.0-rc2 and as soon as it was back online I was able to start the Win10 VM.

 

Before I go ahead and try to upgrade back to 6.1-rc4 is this a known issue or can someone suggest something that I can try to avoid this problem?

 

current working xml for 6.0-rc2

<domain type='kvm' id='2' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>windows81nvidiaMSIRAW</name>
  <uuid>cc411d70-4463-4db7-bf36-d364c0cdaa3c</uuid>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
    <locked/>
  </memoryBacking>
  <vcpu placement='static'>6</vcpu>
  <iothreads>6</iothreads>
  <cputune>
    <vcpupin vcpu='0' cpuset='2'/>
    <vcpupin vcpu='1' cpuset='3'/>
    <vcpupin vcpu='2' cpuset='4'/>
    <vcpupin vcpu='3' cpuset='5'/>
    <vcpupin vcpu='4' cpuset='6'/>
    <vcpupin vcpu='5' cpuset='7'/>
    <iothreadpin iothread='1' cpuset='2'/>
    <iothreadpin iothread='2' cpuset='3'/>
    <iothreadpin iothread='3' cpuset='4'/>
    <iothreadpin iothread='4' cpuset='5'/>
    <iothreadpin iothread='5' cpuset='6'/>
    <iothreadpin iothread='6' cpuset='7'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-q35-2.3'>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
    <pae/>
    <hap/>
    <kvm>
      <hidden state='on'/>
    </kvm>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='6' threads='1'/>
  </cpu>
  <clock offset='localtime'>
    <timer name='rtc' tickpolicy='catchup' track='guest'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>destroy</on_crash>
  <pm>
    <suspend-to-mem enabled='no'/>
    <suspend-to-disk enabled='no'/>
  </pm>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='directsync' io='native'/>
      <source file='/mnt/disk/vmdisk/Image Media/Win8.1ProN.raw'/>
      <backingStore/>
      <target dev='hda' bus='virtio'/>
      <alias name='virtio-disk0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/disk/vmdisk/Images/en_windows_8_1_n_x64_dvd_2707896.iso'/>
      <backingStore/>
      <target dev='hda' bus='sata'/>
      <readonly/>
      <alias name='sata0-0-0'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/disk/vmdisk/Images/virtio-win-0.1-100.iso'/>
      <backingStore/>
      <target dev='hdd' bus='sata'/>
      <readonly/>
      <alias name='sata0-0-3'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <controller type='pci' index='0' model='pcie-root'>
      <alias name='pcie.0'/>
    </controller>
    <controller type='pci' index='1' model='dmi-to-pci-bridge'>
      <alias name='pci.1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/>
    </controller>
    <controller type='pci' index='2' model='pci-bridge'>
      <alias name='pci.2'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <alias name='sata0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/>
    </controller>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <alias name='usb0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <alias name='usb0'/>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <alias name='usb0'/>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <alias name='usb0'/>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x2'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:46:29:be'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/>
    </interface>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/>
    </memballoon>
  </devices>
  <qemu:commandline>
    <qemu:arg value='-device'/>
    <qemu:arg value='ioh3420,bus=pcie.0,addr=1c.0,multifunction=on,port=1,chassis=1,id=root.1'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=01:00.1,bus=pcie.0'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=07:00.0,bus=pcie.0'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='vfio-pci,host=02:00.0,bus=pcie.0'/>
  </qemu:commandline>
</domain>

Link to comment

Right... and now I have introduced a regression error: it erroneously reports Deprecated absolute #command path when the command is correct instead of a not allowed absolute path.

 

(detail in update.php)

 

if (strpos($command, $docroot) !== 0)

 

should be

 

if (strpos($command, $docroot) === 0)

 

Sorry!

 

Ps. This has no impact on the execution (just the reporting)!

 

Actually this is preventing command execution - I will push out a fix asap.

Link to comment

Same problems with Docker… Any running Docker can’t be stopped, any Docker not running can’t be started however a force update will start a Docker but then can’t be stopped.

 

If the array is stopped and restarted the Dockers that I previously tried to stop is now stopped. Same result when rebooting the server.

 

Link to comment

Actually this is preventing command execution - I will push out a fix asap.

 

Bummer, you are right it affects execution and docker in particular.

 

No worries.  We have another little cool online feature being integrated & when that's finished I'll push out next -rc.

Link to comment

I have a question about the upcoming dual parity that influences my current hard drive purchases. Will the parity drives have to be the same size? For example, if my largest data drive is 4TB, can I have a 4TB and a 5TB parity drive?

 

I'm guessing they can be mismatched an the extra 1 TB will be unused, but I just wanted to get a confirmation on this before I purchase new drives.

You are guessing correctly!

Link to comment

Right... and now I have introduced a regression error: it erroneously reports Deprecated absolute #command path when the command is correct instead of a not allowed absolute path.

 

(detail in update.php)

 

if (strpos($command, $docroot) !== 0)

 

should be

 

if (strpos($command, $docroot) === 0)

 

Sorry!

 

Ps. This has no impact on the execution (just the reporting)!

 

Actually this is preventing command execution - I will push out a fix asap.

 

Would/could this have been the cause of apcupsd failing to stop my system cleanly last night?  I do run four dockers.

Link to comment

Would/could this have been the cause of apcupsd failing to stop my system cleanly last night?  I do run four dockers.

 

The error prevented dockers to be stopped, so yes it can be a reason that a proper shutdown wasn't possible.

 

You are advised to upgrade to rc5.

 

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...