limetech Posted August 31, 2015 Share Posted August 31, 2015 Download Clicking 'Check for Updates' on the Plugins page is the preferred way to upgrade. Note: If you are using plugins, please see this thread regarding plugin support. > unRAID Server Version 6.1 Release Notes Changes since 6.0.1. Functional Changes Feedback Button There is a new Feedback button on the webGui menu bar. This may be used to participate in polls and/or view poll results, as well as provide bug reports, feature requests, and general comments related to unRAID. This is aimed at those who do not want to create a forum account, or just want to provide quick feedback to Lime Technology. Custom Images You can now upload (or drag and drop) custom thumbnail images for user icons under Users, as well as a custom banner image. The file must have .png extension and not exceed 95KB in size. The size restriction will be lifted in a future release. If you want to use a larger custom image you may copy it directly to the appropariate directory on your USB Flash device: </pre> <ul>for a banner: config/plugins/dynamix/banner.png for a user thumbnail: config/plugins/dynamix/users/<username>.png </ul> <h3>Enable Disk Shares setting</h3> <p>There is a new setting on the Global Share Settings page called Enable disk shares which can take the value Yes/No/Auto:</p> <p>Yes All disk shares are exported upon array start, provided they are enabled for export in each disk share setting page (this is how it worked before).</p> <p>No All disk shares are unconditionally not exported.</p> <p>Auto Conditionally exports disk shares depending on whether they participiate in user shares or not:</p> <ul> if Enable user shares is set to Yes, then disks which are marked as participating in user shares (according Included/Excluded disks global share setting) are unconditionally not exported. Stated another way: if user shares are enabled, then a particular disk share can only possibly be exported if it is not participating or eligible to participate in user shares. if Enable user shares is set to No, all disk shares are exported upon array start, provided they are enabled for export in each disk share setting. </ul> <p>The purpose of this change is to make it safer to move files off a particular disk to a user share in order to empty the disk or re-arrange files to other disk(s). The proper procedure for this is to first exclude the source disk in the Global Share Settings page (and ensure this setting is set to Auto). Now when browsing the server under Network, only that disk share will show up and you can navigate and move files as necessary.</p> <p>This also makes it safer to do such an operation locally, eg, via command line or using mc. However, since other disk share mount points are still visible, you must be careful to copy files off only the disk which has been excluded as above.</p> <p>This setting is set to Yes when upgrading via this script. For new installations the default for this setting is Auto. We highly recommend setting this to Auto.</p> <h3>OpenELEC Template</h3> <p>The VM Manager now includes the OpenELEC VM template type. Please refer to the wiki page on the subject.</p> <h3>Dot Files Now Displayed</h3> <p>All files/directories beginning with a '.' character are shown when viewing shares and are also now visible via SMB. This makes it easier to see why a particular share is not empty.</p> <h3>Other Changes</h3> <ul>For new installations, NTP is now enabled by default. For new installations, User Shares are now enabled by default. </ul> <h2>Security Advisory updates</h2> <ul>gnutls: 3.3.17.1 (SSA:2015-233-01) ntp: 4.2.8p3 (SSA:2015-188-03) openssl: 1.0.1p (SSA:2015-190-01) </ul> <h2>Change Log</h2> <ul>avahi: supress "Invalid response packet from host" messages btrfs-progs: version 4.1.2 docker: less verbose logging by default docker: version 1.7.1 emhttp: bridge forward delay configurable emhttp: disk share export Yes/No/Auto support emhttp: fix problem not able to start multiple btrfs scrubs emhttp: get rid of passing arbitrary commands in URL emhttp: let Pro start regardless of attached device count emhttp: let Trial support disks in any slots emhttp: properly handle non-rotational devices standby mode (ie, 'spindown') emhttp: properly handle requests from localhost (IP address 127.0.0.1) emhttp: require credentials on all accesses, not just webGui pages libvirt: version 1.2.18 linux: version 4.1.5 linux: support "Lite-On IT Corp. / Plextor M6e PCI Express SSD [Marvell 88SS9183] (rev 14)", see https://lkml.org/lkml/2015/2/2/226 mover: only move objects where "Use Cache" is set to "Yes" for a share ntp: enable by default 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 php: enable pcntl php: version 5.4.44 samba: include linux "dot" objects in directory listings samba: version 4.1.19 slack: ca-certificates version 20150426 slack: check USB Flash device upon startup (set 6th field of fstab to 1) unRAIDServer.plg: improvements in unRAID-5 update: ping google instead of local gateway to determine if network up VM Manager: allow usb devices to be used that do not have a name/desciption VM Manager: Fix: OVMF+Q35 needs the bus set to 'usb' instead of 'ide' for CD-ROMs VM Manager: support OpenELEC template VM Manager: Updated noVNC (using latest as of 8/5/15, commit 8f3c0f6) webGui: Add APCUPS summary to dashboard page webGui: Add refresh button to Docker Scrub operation webGui: added "Hide dot files" control on SMB Settings page webGUI: added banner and user thumbnail image upload support webGui: additional options for text/graphical display of Used/Free. webGui: all '#command' and 'cmd' values must reference scripts within /usr/local/emhttp/ jail. webGui: Corrected: default settings were not applied for apcupsd webGui: disable Array Stop button when mover is running webGui: enhanced report generation webGui: feedback for kool kids webGui: fix issues with uploading thumbnails, banner webGui: fix docker update regression introduced in 6.1-rc1 webGui: fixed memory max display in dashboard webGui: fix notifications not initialized on reboot webGui: force browser reload of selected scripts and css files webGui: include linux "hidden" objects in directory listings webGui: install key: accept pre-keyserver links to key files webGui: integrate latest dynamix changes; many changes, refer to github webGui: Only show docker utilization when docker is enabled webGui: rearrange columns on Main page webGui: Replace alert-box for SweetAlert (enhanced messaging) webGui: use 'ftpusers' script to define ftp users webGui: use 'agent' script to control notification agents webGui: other misc. bug fixes and improvements </ul> <h1>Installation on a New USB Flash Device</h1> <p>To make a bootable USB Flash device follow these steps:</p> <h2>If using Windows (XP/Vista/Win7)</h2> <ol> Plug your USB Flash device into your Windows PC. Open 'My Computer' (XP) or 'Computer' (Vista/Win7) and right-click your Flash device. Click 'Format...', set the volume label to UNRAID and then click 'Start'. Important: the volume label must be set exactly to UNRAID (all caps). Click on your Flash device (to open it), click on the zip file (to open it) and drag then entire contents of the unRAID Server zip file to the Flash. For Windows XP, click on the file 'make_bootable'. A DOS window will open and run the 'syslinux' utility on the Flash. For Windows Vista or Windows 7, right-click on the file 'make_bootable' and select 'Run as administrator'. The 'syslinux' utility will write the Master Boot Record and create a small hidden file named 'ldlinux.sys' on the Flash device, making it bootable. Once again, right-click your Flash device in 'My Computer' or 'Computer' and then click 'Eject'. Your USB Flash device is now ready to boot into unRAID Server OS. </ol> <h2>If using OS X</h2> <ol> Plug your USB Flash device into your Mac. Open Disk Utility, select the device and click the Erase tab. Select Format: MS-DOS (FAT) format, Name: UNRAID and then click Erase. Important: the Name (volume label) must be set exactly to UNRAID (all caps). Click on your UNRAID device (to open it), click on the downloaded unRAID Server OS release zip file (to open it), click on the un-archived unRAID Server folder that results (to open it), and drag then entire contents of the unRAID Server folder to the Flash. Click on the file 'make_bootable_mac' on the device. A terminal window will open and prompt for your admin password. If the selected device is correct, enter the password and hit return. The script will proceed to run the 'syslinux' utility which will write the Master Boot Record and create a small file named 'ldlinux.sys' on the Flash device, making it bootable. Note: you may see your device disappear and reappear on your desktop a few times as the script is running - this is normal. When the script completes, close the terminal window and Eject the device. Your USB Flash device is now ready to boot into unRAID Server OS. </ol Quote Link to comment
smdion Posted September 1, 2015 Share Posted September 1, 2015 Congrats on the official release LT! Quote Link to comment
CHBMB Posted September 1, 2015 Share Posted September 1, 2015 Good work guys. Was expecting this to come along this week sometime.... Quote Link to comment
galways Posted September 1, 2015 Share Posted September 1, 2015 Hi, selected plugin update and got this: plugin: updating: unRAIDServer.plg plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.1.0-x86_64.zip ... done plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.1.0-x86_64.md5 ... done Archive: /tmp/unRAIDServer.zip inflating: /tmp/unRAIDServer/bzimage inflating: /tmp/unRAIDServer/bzroot creating: /tmp/unRAIDServer/config/ extracting: /tmp/unRAIDServer/config/go inflating: /tmp/unRAIDServer/config/network.cfg extracting: /tmp/unRAIDServer/config/disk.cfg inflating: /tmp/unRAIDServer/config/share.cfg inflating: /tmp/unRAIDServer/config/ident.cfg creating: /tmp/unRAIDServer/config/plugins/ inflating: /tmp/unRAIDServer/license.txt inflating: /tmp/unRAIDServer/make_bootable.bat inflating: /tmp/unRAIDServer/make_bootable_mac inflating: /tmp/unRAIDServer/memtest inflating: /tmp/unRAIDServer/readme.txt creating: /tmp/unRAIDServer/syslinux/ inflating: /tmp/unRAIDServer/syslinux/menu.c32 inflating: /tmp/unRAIDServer/syslinux/ldlinux.c32 inflating: /tmp/unRAIDServer/syslinux/syslinux.cfg- inflating: /tmp/unRAIDServer/syslinux/mbr.bin inflating: /tmp/unRAIDServer/syslinux/mboot.c32 inflating: /tmp/unRAIDServer/syslinux/syslinux.cfg inflating: /tmp/unRAIDServer/syslinux/syslinux.exe inflating: /tmp/unRAIDServer/syslinux/syslinux inflating: /tmp/unRAIDServer/syslinux/libutil.c32 inflating: /tmp/unRAIDServer/syslinux/libcom32.c32 inflating: /tmp/unRAIDServer/syslinux/make_bootable_mac.sh Warning: copy(/boot/config/plugins/unRAIDServer.plg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 523 plugin: updated Done Is it safe to reboot? Quote Link to comment
limetech Posted September 1, 2015 Author Share Posted September 1, 2015 Good work guys. Was expecting this to come along this week sometime.... Wanted to get bonienl's changes to SMART report downloads in. As usual: a big thank you to bonienl for his continued contributions to dynamix! Quote Link to comment
jonp Posted September 1, 2015 Share Posted September 1, 2015 Video added to the announcement post! Quote Link to comment
limetech Posted September 1, 2015 Author Share Posted September 1, 2015 Hi, selected plugin update and got this: plugin: updating: unRAIDServer.plg plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.1.0-x86_64.zip ... done plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.1.0-x86_64.md5 ... done Archive: /tmp/unRAIDServer.zip inflating: /tmp/unRAIDServer/bzimage inflating: /tmp/unRAIDServer/bzroot creating: /tmp/unRAIDServer/config/ extracting: /tmp/unRAIDServer/config/go inflating: /tmp/unRAIDServer/config/network.cfg extracting: /tmp/unRAIDServer/config/disk.cfg inflating: /tmp/unRAIDServer/config/share.cfg inflating: /tmp/unRAIDServer/config/ident.cfg creating: /tmp/unRAIDServer/config/plugins/ inflating: /tmp/unRAIDServer/license.txt inflating: /tmp/unRAIDServer/make_bootable.bat inflating: /tmp/unRAIDServer/make_bootable_mac inflating: /tmp/unRAIDServer/memtest inflating: /tmp/unRAIDServer/readme.txt creating: /tmp/unRAIDServer/syslinux/ inflating: /tmp/unRAIDServer/syslinux/menu.c32 inflating: /tmp/unRAIDServer/syslinux/ldlinux.c32 inflating: /tmp/unRAIDServer/syslinux/syslinux.cfg- inflating: /tmp/unRAIDServer/syslinux/mbr.bin inflating: /tmp/unRAIDServer/syslinux/mboot.c32 inflating: /tmp/unRAIDServer/syslinux/syslinux.cfg inflating: /tmp/unRAIDServer/syslinux/syslinux.exe inflating: /tmp/unRAIDServer/syslinux/syslinux inflating: /tmp/unRAIDServer/syslinux/libutil.c32 inflating: /tmp/unRAIDServer/syslinux/libcom32.c32 inflating: /tmp/unRAIDServer/syslinux/make_bootable_mac.sh Warning: copy(/boot/config/plugins/unRAIDServer.plg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 523 plugin: updated Done Is it safe to reboot? What version are you running now? Quote Link to comment
galways Posted September 1, 2015 Share Posted September 1, 2015 Updated from 6.1 R6 Quote Link to comment
limetech Posted September 1, 2015 Author Share Posted September 1, 2015 Updated from 6.1 R6 Well to answer your question: sure, reboot. I haven't seen that pop up in any of our testing. Quote Link to comment
NotYetRated Posted September 1, 2015 Share Posted September 1, 2015 Updated successfully on my end. Thanks for the hard work and generous updates! Quote Link to comment
interwebtech Posted September 1, 2015 Share Posted September 1, 2015 Slightly odd... update via webGUI from my W10 pc. I always turn on the monitor connected to UR server when there will be a reboot so I can watch that process. Normally all the responses from updating appear in the webgui popup that downloads installs, etc. This time, starting with the "syncing..." message (before it tells you to REBOOT), ALL the responses from that point on appeared on the console (not the webgui popup). I was watching webgui and was wondering what was taking so long (no messages), turned around and all the messages were on the console screen. Is this normal? I'd prefer it all be in one place, either or but all on the same screen ps. update was successful Quote Link to comment
galways Posted September 1, 2015 Share Posted September 1, 2015 Hi, tried twice to reboot it starts the reboot process fine then I get this on the screen when it freezes up 0800 3918848 sda driver: sd 0801 3918816 sda1 0e5ab 65r-01 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block (0,0) CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.1.5-unRaid #3 Disk problem or something else? Quote Link to comment
bondoo0 Posted September 1, 2015 Share Posted September 1, 2015 Slightly odd... update via webGUI from my W10 pc. I always turn on the monitor connected to UR server when there will be a reboot so I can watch that process. Normally all the responses from updating appear in the webgui popup that downloads installs, etc. This time, starting with the "syncing..." message (before it tells you to REBOOT), ALL the responses from that point on appeared on the console (not the webgui popup). I was watching webgui and was wondering what was taking so long (no messages), turned around and all the messages were on the console screen. Is this normal? I'd prefer it all be in one place, either or but all on the same screen ps. update was successful Seeing something similar (pop up stps at syncing) however I don't see any additional update on console. I'm not sure if update was successful out not is there anything I should check to see if update was successful, short of rebooting? Quote Link to comment
galways Posted September 1, 2015 Share Posted September 1, 2015 Got it working. I checked the flash drive, only some of the files had been replaced i.e., bzimage was while bzroot wasn't. Downloaded the zip, put missing files on the flash and it rebooted just fine. Quote Link to comment
toby9999 Posted September 1, 2015 Share Posted September 1, 2015 Well done on the new release I'm getting one strange message *every minute* ... Sep 1 11:07:47 StorageArray kernel: mdcmd (94): set spinup_group 19 0 Sep 1 11:07:47 StorageArray kernel: mdcmd (95): set spinup_group 20 0 Sep 1 11:07:47 StorageArray kernel: mdcmd (96): set spinup_group 21 0 Sep 1 11:08:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:09:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:10:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:11:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:11:53 StorageArray emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Sep 1 11:12:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:13:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:14:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:15:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:16:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:17:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:17:50 StorageArray kernel: mdcmd (97): spindown 0 Sep 1 11:18:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:19:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:20:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:21:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Any ideas? Quote Link to comment
jonp Posted September 1, 2015 Share Posted September 1, 2015 Well done on the new release I'm getting one strange message *every minute* ... Sep 1 11:07:47 StorageArray kernel: mdcmd (94): set spinup_group 19 0 Sep 1 11:07:47 StorageArray kernel: mdcmd (95): set spinup_group 20 0 Sep 1 11:07:47 StorageArray kernel: mdcmd (96): set spinup_group 21 0 Sep 1 11:08:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:09:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:10:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:11:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:11:53 StorageArray emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Sep 1 11:12:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:13:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:14:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:15:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:16:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:17:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:17:50 StorageArray kernel: mdcmd (97): spindown 0 Sep 1 11:18:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:19:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:20:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:21:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Any ideas? Did you reboot? Quote Link to comment
dlandon Posted September 1, 2015 Share Posted September 1, 2015 The syncing and please reboot messages go to the attached console and not the updating dialog. Might be confusing some. Quote Link to comment
trurl Posted September 1, 2015 Share Posted September 1, 2015 Update from plugin page worked normally for me. Quote Link to comment
smdion Posted September 1, 2015 Share Posted September 1, 2015 Well done on the new release I'm getting one strange message *every minute* ... Sep 1 11:07:47 StorageArray kernel: mdcmd (94): set spinup_group 19 0 Sep 1 11:07:47 StorageArray kernel: mdcmd (95): set spinup_group 20 0 Sep 1 11:07:47 StorageArray kernel: mdcmd (96): set spinup_group 21 0 Sep 1 11:08:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:09:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:10:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:11:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:11:53 StorageArray emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Sep 1 11:12:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:13:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:14:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:15:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:16:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:17:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:17:50 StorageArray kernel: mdcmd (97): spindown 0 Sep 1 11:18:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:19:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:20:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:21:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Any ideas? Did you reboot? Hey Jon Seeing the same thing here... multiple reboots... I am running as a Guest on esxi... so I never like to post errors first. Quote Link to comment
toby9999 Posted September 1, 2015 Share Posted September 1, 2015 Yep - rebooted and so far everything is solid under 6.1 ... just those messages in the log file every minute. Quote Link to comment
dlandon Posted September 1, 2015 Share Posted September 1, 2015 Yep - rebooted and so far everything is solid under 6.1 ... just those messages in the log file every minute. There was a change made in the notification system that I think is causing those messages. Disable notifications and then re-enable notifications and they should go away. Quote Link to comment
jonp Posted September 1, 2015 Share Posted September 1, 2015 Well done on the new release I'm getting one strange message *every minute* ... Sep 1 11:07:47 StorageArray kernel: mdcmd (94): set spinup_group 19 0 Sep 1 11:07:47 StorageArray kernel: mdcmd (95): set spinup_group 20 0 Sep 1 11:07:47 StorageArray kernel: mdcmd (96): set spinup_group 21 0 Sep 1 11:08:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:09:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:10:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:11:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:11:53 StorageArray emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Sep 1 11:12:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:13:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:14:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:15:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:16:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:17:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:17:50 StorageArray kernel: mdcmd (97): spindown 0 Sep 1 11:18:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:19:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:20:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:21:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Any ideas? Did you reboot? Hey Jon Seeing the same thing here... multiple reboots... I am running as a Guest on esxi... so I never like to post errors first. No ideas. Works solid on physical systems from all our testing. Ran through it earlier today as a sanity check upgrading 6.0.1 to 6.1.0 Quote Link to comment
sureguy Posted September 1, 2015 Share Posted September 1, 2015 Yep - rebooted and so far everything is solid under 6.1 ... just those messages in the log file every minute. There was a change made in the notification system that I think is causing those messages. Disable notifications and then re-enable notifications and they should go away. I'm running ESXi and was getting the notifications. Disabling and re-enabling the notifications seemed to work. Aug 31 21:29:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:30:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:31:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:32:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:33:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:34:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:35:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:35:10 Phatstore php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'DUC' Aug 31 21:35:10 Phatstore kernel: device vethd4861c3 entered promiscuous mode Aug 31 21:35:10 Phatstore kernel: docker0: port 2(vethd4861c3) entered forwarding state Aug 31 21:35:10 Phatstore kernel: docker0: port 2(vethd4861c3) entered forwarding state Aug 31 21:35:10 Phatstore avahi-daemon[8877]: Withdrawing workstation service for veth03cfb8e. Aug 31 21:35:10 Phatstore kernel: eth0: renamed from veth03cfb8e Aug 31 21:35:25 Phatstore kernel: docker0: port 2(vethd4861c3) entered forwarding state Aug 31 21:36:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:37:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:38:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:39:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:40:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:41:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:42:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:43:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:44:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:45:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:46:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:47:16 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:48:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:49:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:50:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:50:40 Phatstore emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Aug 31 21:51:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:52:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:53:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:54:01 Phatstore crond[2004]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Aug 31 21:54:47 Phatstore php: /usr/local/emhttp/plugins/dynamix/scripts/notify 'cron-init' Aug 31 21:55:00 Phatstore php: /usr/local/emhttp/plugins/dynamix/scripts/notify 'cron-init' Aug 31 21:55:07 Phatstore emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Aug 31 21:55:15 Phatstore emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Aug 31 21:55:30 Phatstore emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Aug 31 21:56:05 Phatstore emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Aug 31 21:57:37 Phatstore emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Aug 31 21:59:38 Phatstore emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog I'm going to reboot to see if the fix is "sticky" - I've rebooted several times after upgrading as it seems the unassigned devices plugin is broken. Quote Link to comment
smdion Posted September 1, 2015 Share Posted September 1, 2015 Well done on the new release I'm getting one strange message *every minute* ... Sep 1 11:07:47 StorageArray kernel: mdcmd (94): set spinup_group 19 0 Sep 1 11:07:47 StorageArray kernel: mdcmd (95): set spinup_group 20 0 Sep 1 11:07:47 StorageArray kernel: mdcmd (96): set spinup_group 21 0 Sep 1 11:08:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:09:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:10:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:11:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:11:53 StorageArray emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Sep 1 11:12:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:13:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:14:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:15:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:16:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:17:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:17:50 StorageArray kernel: mdcmd (97): spindown 0 Sep 1 11:18:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:19:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:20:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Sep 1 11:21:01 StorageArray crond[1674]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Any ideas? Did you reboot? Hey Jon Seeing the same thing here... multiple reboots... I am running as a Guest on esxi... so I never like to post errors first. No ideas. Works solid on physical systems from all our testing. Ran through it earlier today as a sanity check upgrading 6.0.1 to 6.1.0 Removed all plugins and got this in the logs Aug 31 21:02:16 Redemption crond[2130]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null I also see this in the console cat: /var/log/scripts/*: No such file or directory I would restart again, but the wife is watching plex Quote Link to comment
Recommended Posts
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.