unRAID Server Release 6.1-rc3 Available


limetech

Recommended Posts

To install this release, 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

 

Mainly a bug-fix release.  In looking at the change log one might ask, "hey why are you updating the kernel for an unRaid release candidate?"  Answer is that we will update kernel "patch" releases (which are bug fixes), which is the third digit in the release, for example here we updated to 4.1.5.  We would not update to 4.2 in an unRaid -rc release however.  Same goes for other components, for example we also updated Samba to 4.1.19 - another patch release.

 

Having said that, there are a set of changes here which one could argue might not properly belong in a release candidate.  That is, we are plugging a potential unRaid security issue having to do with the ability to execute arbitrary commands via http GET/POST requests (plugin authors: see below).  We decided it was best to deal with this now rather than wait for 6.2 series.

 

A side-effect of these changes is that any Notifications you have enabled won't work until you disable the Notification, hit Apply, and then enable it again, and hit Apply.  If you see this message in your log, then this applies to you:

 

Aug 12 18:10:01 unRAID crond[1881]: exit status 127 from user root /usr/local/sbin/plugincheck &> /dev/null

 

Another side-effect is that some plugins may not work correctly until the author makes appropriate changes.

 


 

Plugin Authors:

 

We made some changes having to do with commands passed in the 'cmd' (for update.htm) and '#command' (for update.php) query variables.  There are basically 4 ways a command string can be passed:

 

1) An absolute path in a “/usr/local/emhttp” jail (docroot):

 

cmd=/webGui/scripts/mycmd
cmd=/plugins/<plugin-name>/scripts/mycmd

 

This is now the “best practice” for all command strings in the webGui.  When the command is actually executed we will prepend “/usr/local/emhttp” to form the real path.

 

2) An absolute path where docroot is explicitly included:

 

cmd=/usr/local/emhttp/webGui/scripts/mycmd
cmd=/usr/local/emhttp/plugins/<plugin-name>/scripts/mycmd

 

This will work but we will generate syslog message similar to:

 

“Deprecated absolute path:”

 

In 6.1 ‘stable’ this will be an error.  There are no uses of this form in current webGui.

 

3) A relative path:

 

cmd=webGui/scripts/mycmd
cmd=plugins/<plugin-name>/scripts/mycmd
cmd=rm file

 

This will work but we will generate syslog message similar to:

 

“Deprecated relative path:”

 

In 6.1 ‘stable’ this will be an error.  There are a couple places this is still used in webGui which need to be cleaned up before 6.1 stable released:

- NotificationAgents.page

- FTP.page

 

4) An absolute path outside our docroot:

 

cmd=/usr/sbin/rm file

 

This will not work at all and will generate an error message in the syslog.

 

Once 6.1 stable is released, we’ll use realpath() function to verify commands do not get outside /usr/local/emhttp but this is not enforced in –rc3 because I want to give some ‘heads up’ time to plugin authors to fix their code.

 

Finally, when passing a shell command to exec() and kin, the “best practice” is to specify an absolute path:

 

exec(“/usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin $args”);

 

though this will work (but watch out: no leading ‘/’):

 

exec(“plugins/dynamix.plugin.manager/scripts/plugin $args”);

 

and one could also use:

 

exec(“$docroot/plugins/dynamix.plugin.manager/scripts/plugin $args”);

 


 

unRAID Server Version &version; 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

Link to comment
  • Replies 86
  • Created
  • Last Reply

Top Posters In This Topic

With 61. rc3, I am unable to stop Docker containers.  This is all I see in the log:

 

Aug 12 07:04:28 unRAID php: /usr/local/emhttp/usr/bin/docker stop TFTP-Server
Aug 12 07:04:42 unRAID php: /usr/local/emhttp/usr/bin/docker stop TFTP-Server
Aug 12 07:04:56 unRAID php: /usr/local/emhttp/usr/bin/docker stop EmbyServer

 

I am also seeing these message in the syslog:

 

Aug 12 06:44:01 unRAID crond[1890]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Aug 12 06:45:01 unRAID crond[1890]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Aug 12 06:46:01 unRAID crond[1890]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Aug 12 06:47:01 unRAID crond[1890]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null

 

I removed all plugins (some Dynamix and the Community Apps) to see if one of them is the culprit.  Of course, the much larger issue however is the inability to stop containers.

 

John

Link to comment

With 61. rc3, I am unable to stop Docker containers.  This is all I see in the log:

 

Aug 12 07:04:28 unRAID php: /usr/local/emhttp/usr/bin/docker stop TFTP-Server
Aug 12 07:04:42 unRAID php: /usr/local/emhttp/usr/bin/docker stop TFTP-Server
Aug 12 07:04:56 unRAID php: /usr/local/emhttp/usr/bin/docker stop EmbyServer

 

I am also seeing these message in the syslog:

 

Aug 12 06:44:01 unRAID crond[1890]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Aug 12 06:45:01 unRAID crond[1890]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Aug 12 06:46:01 unRAID crond[1890]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Aug 12 06:47:01 unRAID crond[1890]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null

 

I removed all plugins (some Dynamix and the Community Apps) to see if one of them is the culprit.  Of course, the much larger issue however is the inability to stop containers.

 

John

 

Removed all plugins and the messages above seemed to have ceased.

 

Still not able to stop (or restart also I assume) Docker containers.

 

John

Link to comment

Another possible issue...

 

Is the ntpd service not starting?

 

I see the message below in my syslog:

 

Aug 12 07:21:44 unRAID ntpd[1869]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

 

So, I went into the Date & Time settings in unRAID and made a change and Apply/Done and saw these messages:

 

Aug 12 07:24:41 unRAID emhttp: shcmd (93): ln -sf /usr/share/zoneinfo/America/New_York /etc/localtime-copied-from
Aug 12 07:24:41 unRAID emhttp: shcmd (94): cp /etc/localtime-copied-from /etc/localtime
Aug 12 07:24:41 unRAID emhttp: shcmd (95): /etc/rc.d/rc.ntpd restart |& logger
Aug 12 07:24:41 unRAID ntpd[1869]: ntpd exiting on signal 1 (Hangup)
Aug 12 07:24:41 unRAID ntpd[1869]: 127.127.1.0 local addr 127.0.0.1 -> 
Aug 12 07:24:41 unRAID ntpd[1869]: 192.168.1.1 local addr 192.168.1.10 -> 
Aug 12 07:24:41 unRAID logger: Stopping NTP daemon...
Aug 12 07:24:42 unRAID ntpd[15505]: ntpd 4.2.8p3@1.3265-o Mon Jul 6 18:09:09 UTC 2015 (1): Starting
Aug 12 07:24:42 unRAID ntpd[15505]: Command line: /usr/sbin/ntpd -g -p /var/run/ntpd.pid
Aug 12 07:24:42 unRAID logger: Starting NTP daemon: /usr/sbin/ntpd -g
Aug 12 07:24:42 unRAID ntpd[15508]: proto: precision = 0.065 usec (-24)
Aug 12 07:24:42 unRAID ntpd[15508]: restrict default: KOD does nothing without LIMITED.
Aug 12 07:24:42 unRAID ntpd[15508]: Listen and drop on 0 v4wildcard 0.0.0.0:123
Aug 12 07:24:42 unRAID ntpd[15508]: Listen normally on 1 lo 127.0.0.1:123
Aug 12 07:24:42 unRAID ntpd[15508]: Listen normally on 2 br0 192.168.1.10:123
Aug 12 07:24:42 unRAID ntpd[15508]: Listen normally on 3 docker0 172.17.42.1:123
Aug 12 07:24:42 unRAID ntpd[15508]: Listening on routing socket on fd #20 for interface updates

 

Is this working as expected?  maybe a situation like Notification where you have to make a setting change and then apply again to get the service going?

 

John

Link to comment

With 61. rc3, I am unable to stop Docker containers.  This is all I see in the log:

 

Aug 12 07:04:28 unRAID php: /usr/local/emhttp/usr/bin/docker stop TFTP-Server
Aug 12 07:04:42 unRAID php: /usr/local/emhttp/usr/bin/docker stop TFTP-Server
Aug 12 07:04:56 unRAID php: /usr/local/emhttp/usr/bin/docker stop EmbyServer

 

I am also seeing these message in the syslog:

 

Aug 12 06:44:01 unRAID crond[1890]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Aug 12 06:45:01 unRAID crond[1890]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Aug 12 06:46:01 unRAID crond[1890]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null
Aug 12 06:47:01 unRAID crond[1890]: exit status 127 from user root /usr/lib/sa/sa1 1 1 &> /dev/null

 

I removed all plugins (some Dynamix and the Community Apps) to see if one of them is the culprit.  Of course, the much larger issue however is the inability to stop containers.

 

John

 

John, I'm able to stop, start & restart docker containers, I am also seeing similar crond messages in the log.  I have had no errors with my time settings..

Link to comment

The powerdown plugin can't shutdown the array cleanly because /root/mdcmd is not available in this rc.  Until I can resolve the issue, you should uninstall the powerdown plugin.

 

Ah, that explains why I suddenly seeing a parity check...  Was just looking into that.  Thanks dlandon.

Link to comment

Another possible issue...

 

Is the ntpd service not starting?

 

I see the message below in my syslog:

 

Aug 12 07:21:44 unRAID ntpd[1869]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

 

So, I went into the Date & Time settings in unRAID and made a change and Apply/Done and saw these messages:

 

Aug 12 07:24:41 unRAID emhttp: shcmd (93): ln -sf /usr/share/zoneinfo/America/New_York /etc/localtime-copied-from
Aug 12 07:24:41 unRAID emhttp: shcmd (94): cp /etc/localtime-copied-from /etc/localtime
Aug 12 07:24:41 unRAID emhttp: shcmd (95): /etc/rc.d/rc.ntpd restart |& logger
Aug 12 07:24:41 unRAID ntpd[1869]: ntpd exiting on signal 1 (Hangup)
Aug 12 07:24:41 unRAID ntpd[1869]: 127.127.1.0 local addr 127.0.0.1 -> 
Aug 12 07:24:41 unRAID ntpd[1869]: 192.168.1.1 local addr 192.168.1.10 -> 
Aug 12 07:24:41 unRAID logger: Stopping NTP daemon...
Aug 12 07:24:42 unRAID ntpd[15505]: ntpd 4.2.8p3@1.3265-o Mon Jul 6 18:09:09 UTC 2015 (1): Starting
Aug 12 07:24:42 unRAID ntpd[15505]: Command line: /usr/sbin/ntpd -g -p /var/run/ntpd.pid
Aug 12 07:24:42 unRAID logger: Starting NTP daemon: /usr/sbin/ntpd -g
Aug 12 07:24:42 unRAID ntpd[15508]: proto: precision = 0.065 usec (-24)
Aug 12 07:24:42 unRAID ntpd[15508]: restrict default: KOD does nothing without LIMITED.
Aug 12 07:24:42 unRAID ntpd[15508]: Listen and drop on 0 v4wildcard 0.0.0.0:123
Aug 12 07:24:42 unRAID ntpd[15508]: Listen normally on 1 lo 127.0.0.1:123
Aug 12 07:24:42 unRAID ntpd[15508]: Listen normally on 2 br0 192.168.1.10:123
Aug 12 07:24:42 unRAID ntpd[15508]: Listen normally on 3 docker0 172.17.42.1:123
Aug 12 07:24:42 unRAID ntpd[15508]: Listening on routing socket on fd #20 for interface updates

 

Is this working as expected?  maybe a situation like Notification where you have to make a setting change and then apply again to get the service going?

 

John

 

Actually John, just seen this in my log, but this was after I disabled then enabled NTP.

 

Aug 12 12:57:07 Server ntpd[4372]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized

Link to comment

The powerdown plugin can't shutdown the array cleanly because /root/mdcmd is not available in this rc.  Until I can resolve the issue, you should uninstall the powerdown plugin.

 

I don't have the powerdown plugin installed so it must have been another for me (Community Apps, Dynamix System Buttons or Dynamix System Info).

 

John

Link to comment

The powerdown plugin can't shutdown the array cleanly because /root/mdcmd is not available in this rc.  Until I can resolve the issue, you should uninstall the powerdown plugin.

 

This is what /root/mdcmd looks like.

#!/bin/bash
#
if [ $# -eq 0 ]; then
  echo "usage: mdcmd <command> [arg ... ]"
  exit 1;
fi;

if [ $1 == "status" ]; then
  cat /proc/mdcmd
else
  echo $* >/proc/mdcmd
fi

 

The powerdown plugin can be adjusted to echo the proper command directly to /proc/mdcmd instead.

Link to comment

The powerdown plugin can't shutdown the array cleanly because /root/mdcmd is not available in this rc.  Until I can resolve the issue, you should uninstall the powerdown plugin.

 

I don't have the powerdown plugin installed so it must have been another for me (Community Apps, Dynamix System Buttons or Dynamix System Info).

 

John

Doubt it was CA.  Until I get home from work, CA will probably be broken on displaying the popup descriptions / changelogs.  Sight unseen, everything else should still be operational.
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.