limetech Posted August 16, 2015 Share Posted August 16, 2015 If you are running 6.1-rc3/-rc4 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 -rc4 and to introduce a Feedback button on the webGui Menu. This has been in the works for a while and we created it in order to provide a quick way to provide feedback, especially for those who don't want to deal with a forum 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. Also you should hit F5 in browser window or clear browser cache after updating. Known issues: The powerdown script does not get invoked correctly. You can type this at the command shell to fix it or add to 'go' file until we generate another release: ln -s /usr/local/sbin/powerdown /root unRAID Server Version 6.1-rc5 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 Other changes (6.1-rc5) ----------------------- - webGui: fix another regression resulting from closing 'arbitrary command execution' holes - webGui: integrated eric's feedback for kool kids Link to comment
bonienl Posted August 16, 2015 Share Posted August 16, 2015 Cool feature ... not only for kids Link to comment
garycase Posted August 16, 2015 Share Posted August 16, 2015 Nice update -- the direct feedback feature is very nice. Link to comment
dlandon Posted August 16, 2015 Share Posted August 16, 2015 Loss of UPS power is not initiating a shutdown. I've submitted a bug report in the new "Feedback". We'll see how it works. Link to comment
NAS Posted August 16, 2015 Share Posted August 16, 2015 My concern is that we now have no way of users knowing about directly submitted bugs etc Link to comment
jumperalex Posted August 16, 2015 Share Posted August 16, 2015 good point. Is automated reposting to the defect forum possible. Link to comment
dlandon Posted August 16, 2015 Share Posted August 16, 2015 Tom, The /etc/apcupsd 'doshutdown' script refers to a script in /root that no longer exists: #!/bin/bash # LimeTech - modified for unRAID /root/powerdown exit 99 I believe it should be: #!/bin/bash # LimeTech - modified for unRAID /usr/local/sbin/powerdown exit 99 This is preventing a shutdown when UPS power is lost. EDIT: Because of this issue, the problem with Docker commands, and other functional issues, this series would probably have best been a beta. I know LT mentioned the reasons for an rc and not a beta, but the changes affected a lot of functionality and were not just bug fixes. I see where there are those that are so trusting of the rc releases, they are installing them on their main servers and not test servers. I am running beta and rc releases on my test server so I can do some testing and catch and report these issues and not affect my main server. Link to comment
limetech Posted August 16, 2015 Author Share Posted August 16, 2015 My concern is that we now have no way of users knowing about directly submitted bugs etc The feedback system is primarily targeting Trial users who may not want to create a forum account in order to provide feedback. If a Trial user encounters something that puts them off, they are likely to just abandon the s/w and we'd never know why. Of course they can still do that, but if we make it super-easy to send us info, then we're more likely to get info. Link to comment
limetech Posted August 16, 2015 Author Share Posted August 16, 2015 The /etc/apcupsd 'doshutdown' script refers to a script in /root that no longer exists: This is preventing a shutdown when UPS power is lost. Nice catch. You can type this at the command shell or add to 'go' file until we generate another release: ln -s /usr/local/sbin/powerdown /root Link to comment
NAS Posted August 16, 2015 Share Posted August 16, 2015 My concern is that we now have no way of users knowing about directly submitted bugs etc The feedback system is primarily targeting Trial users who may not want to create a forum account in order to provide feedback. If a Trial user encounters something that puts them off, they are likely to just abandon the s/w and we'd never know why. Of course they can still do that, but if we make it super-easy to send us info, then we're more likely to get info. I think it makes a lot of sense but playing devils advocate thats not what it is worded as and we can see one forum uber already used it. Link to comment
limetech Posted August 16, 2015 Author Share Posted August 16, 2015 My concern is that we now have no way of users knowing about directly submitted bugs etc The feedback system is primarily targeting Trial users who may not want to create a forum account in order to provide feedback. If a Trial user encounters something that puts them off, they are likely to just abandon the s/w and we'd never know why. Of course they can still do that, but if we make it super-easy to send us info, then we're more likely to get info. I think it makes a lot of sense but playing devils advocate thats not what it is worded as and we can see one forum uber already used it. It will probably undergo some refinements over time, such as adding some wording that says, "Please check our forum to see if the bug you are going to report has already been reported". Link to comment
BRiT Posted August 16, 2015 Share Posted August 16, 2015 It would be really slick if it feed into an actual bug tracking system instead. Link to comment
jumperalex Posted August 16, 2015 Share Posted August 16, 2015 The /etc/apcupsd 'doshutdown' script refers to a script in /root that no longer exists: This is preventing a shutdown when UPS power is lost. Nice catch. You can type this at the command shell or add to 'go' file until we generate another release: ln -s /usr/local/sbin/powerdown /root I know this is just a few posts down, but probably worth adding directly to the OP since no one will notice unless they explicitly test or have a power cut. Link to comment
limetech Posted August 16, 2015 Author Share Posted August 16, 2015 The /etc/apcupsd 'doshutdown' script refers to a script in /root that no longer exists: This is preventing a shutdown when UPS power is lost. Nice catch. You can type this at the command shell or add to 'go' file until we generate another release: ln -s /usr/local/sbin/powerdown /root I know this is just a few posts down, but probably worth adding directly to the OP since no one will notice unless they explicitly test or have a power cut. Good idea. done. Link to comment
CHBMB Posted August 16, 2015 Share Posted August 16, 2015 The /etc/apcupsd 'doshutdown' script refers to a script in /root that no longer exists: This is preventing a shutdown when UPS power is lost. Nice catch. You can type this at the command shell or add to 'go' file until we generate another release: ln -s /usr/local/sbin/powerdown /root Other than this all working great here as far as I can tell. I know this is just a few posts down, but probably worth adding directly to the OP since no one will notice unless they explicitly test or have a power cut. Good idea. done. Link to comment
kaiguy Posted August 17, 2015 Share Posted August 17, 2015 Sorry if this is a stupid question, but this is my first time moving up to an rc for 6.1... I thought in rc2 there was a change to non-rotational drives in the webgui. Well, my cache SSD has a "click to spindown" arrow on the Main tab in the webgui. Am I misunderstanding the change to think that this shouldn't be an option? Thanks! Link to comment
limetech Posted August 17, 2015 Author Share Posted August 17, 2015 Sorry if this is a stupid question, but this is my first time moving up to an rc for 6.1... I thought in rc2 there was a change to non-rotational drives in the webgui. Well, my cache SSD has a "click to spindown" arrow on the Main tab in the webgui. Am I misunderstanding the change to think that this shouldn't be an option? Thanks! Your SSD is able to go into 'standby' mode, presumably lower power, that's what spindown means for such devices. Link to comment
balloob Posted August 17, 2015 Share Posted August 17, 2015 Ever since I upgraded to RC3, Chrome has been unable to retrieve any of the webfonts. It keeps getting 401 Not authorized responses. Navigating directly to the URL works. I experience no problems in Safari or Firefox. Link to comment
bonienl Posted August 17, 2015 Share Posted August 17, 2015 Ever since I upgraded to RC3, Chrome has been unable to retrieve any of the webfonts. It keeps getting 401 Not authorized responses. Navigating directly to the URL works. I experience no problems in Safari or Firefox. First I recommend you upgrade to v6.1rc5, but this has nothing to do with your issue. It seems the style-sheet files (.css) are not loaded. Are they deleted? You can check manually by telnetting into your system: # ls -l /usr/local/emhttp/webGui/styles/*.css -rw-r--r-- 1 root root 4977 Jun 30 01:48 /usr/local/emhttp/webGui/styles/context.standalone.css -rw-r--r-- 1 root root 78 Jul 25 00:32 /usr/local/emhttp/webGui/styles/custom-banner.css -rw-r--r-- 1 root root 64 Jul 25 00:38 /usr/local/emhttp/webGui/styles/default-banner.css -rw-r--r-- 1 root root 16463 Aug 9 18:02 /usr/local/emhttp/webGui/styles/default-black.css [color=red]-rw-r--r-- 1 root root 1449 Sep 20 2014 /usr/local/emhttp/webGui/styles/default-fonts.css[/color] -rw-r--r-- 1 root root 16263 Jul 25 00:32 /usr/local/emhttp/webGui/styles/default-white.css -rw-r--r-- 1 root root 16236 Jul 13 23:32 /usr/local/emhttp/webGui/styles/dynamix-black.css -rw-r--r-- 1 root root 16125 Jul 13 23:32 /usr/local/emhttp/webGui/styles/dynamix-white.css [color=red]-rw-r--r-- 1 root root 23643 Jun 30 01:48 /usr/local/emhttp/webGui/styles/font-awesome.css[/color] -rw-r--r-- 1 root root 6021 Jul 8 20:42 /usr/local/emhttp/webGui/styles/jquery.filetree.css -rw-r--r-- 1 root root 17724 Aug 16 09:57 /usr/local/emhttp/webGui/styles/jquery.sweetalert.css -rw-r--r-- 1 root root 408 Jul 1 05:13 /usr/local/emhttp/webGui/styles/jquery.switchbutton.css -rw-r--r-- 1 root root 21453 Jun 30 01:48 /usr/local/emhttp/webGui/styles/jquery.ui.css Link to comment
balloob Posted August 17, 2015 Share Posted August 17, 2015 Sorry, I meant to say I did upgrade to RC5 but had this issue since RC3. The stylesheets are there and it works fine in Firefox and Safari. Only happens in Chrome when the urls are loading from the webGui. Navigating directly to the urls works. From inspecting with the Chrome dev tools it looks like Chrome is not adding the authorization header. Link to comment
bonienl Posted August 17, 2015 Share Posted August 17, 2015 Sorry, I meant to say I did upgrade to RC5 but had this issue since RC3. The stylesheets are there and it works fine in Firefox and Safari. Only happens in Chrome when the urls are loading from the webGui. Navigating directly to the urls works. From inspecting with the Chrome dev tools it looks like Chrome is not adding the authorization header. Weird, I am using Chrome (44.0.2403.155) too and don't have issues. Link to comment
CHBMB Posted August 17, 2015 Share Posted August 17, 2015 I'm having no issues with Chrome on my Windows 10 laptop, Windows 8.1 desktop, my Android tablet and Android phone. Be interesting to see what the issue is. Link to comment
jonp Posted August 17, 2015 Share Posted August 17, 2015 Ever since I upgraded to RC3, Chrome has been unable to retrieve any of the webfonts. It keeps getting 401 Not authorized responses. Navigating directly to the URL works. I experience no problems in Safari or Firefox. Does this cause the fonts on the webgui to be rendered in times new roman or something? Have you tried clearing browser cache? Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.