kricker

Any update on this? I just added this and I am seeing the same issue.

Can you get to the Web UI for the mcMyAdmin? I did what you outlined in the OP, but I have no clue if it is working. In the Docker log for McMyAdmin I see: Notice : McMyAdmin has started and is ready for use. Notice : This is the first time McMyAdmin has been started. Notice : You must complete the first-start wizard via the web interface.

I just upgraded to Unraid v6 and I am starting to work with Docker. I installed the Sickrage Docker and it looks to be running fine, but I can not login to the webui. Originally the Sickrage config was set to use web_host = 192.168.0.100 but that would give me errors, so I switched it to: web_host = localhost That no longer gave errors, but I can not connect to the webUI at all. I thought it would pass-through to my servers local ip of 192.168.0.100. I changed from bridged mode to host, and that works. What could be the issue in bridge mode?

Bump. I am seeing the same thing in my first running of v6 b15 after upgrading from v5.

Sweet. I renamed the file and I am up and running. Thanks.

I downloaded SABnzbd-0.7.20-src.tar.gz from sourceforge. I then placed it where I thought it went. Based on your last post I now moved it to /boot/config/plugins/Sabnzbd, but Sabnzbd still will not start. I keep getting that same issue. It looks like it tries to dl the file but something goes wrong.

I am having issues getting v2 of the SABnzbd plugin working. It appears there may be an issues downloading Sabnzbd-Phaze-0.7.20-src.tar.gz. I downloaded the file manually in Chrome and copied it to /boot/packages. But Sabnzbd still will not install. When I try it still tries to download the file and fails.

So...what are you going to do with the Atom system?

The system wierdness has worked itself out somehow and it sleeps happily.

Nope. Only the addons listed earlier.

After a couple system reboots it started working as it should. Then the system was moved to its new home and the issue came back. Hopefully after another few reboots it will behave again.

DOH! I manage unRaid remotely so often I forgot I could just login locally. I feel so dumb. Thanks for the tip. I'll do that.

I can't find a way to block it access to the internet with my router. I can add it to the firewall rules, but I can only block access based on ports. How can I know which port it could be communicatin on? If I pull the cable I won't be able to see if the disk is spinning or not. Hmmmm.

Everything that has access to the server is shutdown. I spun down the disk and reset the statistics. There have been no more reads on the disk but it still spun up.

As in pull the network cable from it? What is your though on this? I just saw the statistics show 9 reads on that drive. How can I tell what is doing these reads?

I'm bumping this old thread due to an issue I am having. I built a new unRaid setup for my Dad using a HP Microserver N54L and some spare drives I had laying around. For the most part everything is working great. The only issue I have is with one drive in particular will not stay spun down. I can manually tell it to spin down, but something is causing it to spin back up. I installed inotify from here and setup a watch on the disk. It never reported any activity, yet the drive did spin up. I don't' see anything in the logs. I have the following Dynamix plugins intalled: WebGUI Active Streams S3 Sleep System Info System Stats Plugin Control No other plugins are installed.

Thanks. The links in the OP go to: http://bergware.github.io/dynamix/

I have a friend setting up a new UnRaid system and I pointed him to Dynamix as a must have. Unfortunately, the Github is giving a 404 error.

Any chance you've tinkered with the "UnRecyler" addon yet? Having a trash for SMB is quite handy.

No worries. I've gotten good at restarting unRaid Just glad you could figure out what is happening.

Here you go: service="1" checkHDD="-a -c" timeout="30" interval="3" port="eth0" checkTCP="" idle="0" login="" pingIP="" stopDay="" stopHour="" dhcpRenew="" forceGb="" setWol="" preRun="" postRun="" debug="3" exclude="" excludeList="" options="-C 1 -a -c -m 30 -e eth0 -D 3"

This one. Warning: implode(): Invalid arguments passed in /usr/local/emhttp/update.sleep.php on line 13 Also see above. I tired killing the script but my GUI is still hung. I still have access to the tower using my iKVM or telnet and everything else is working, but the weGUI will not respond.

Thanks. I'll try that. Any ideas about the odd error message I see at the bottom of the Sleep plugin page when I hit Apply? Uhoh, looks like a good time to test it. I just hit Apply again in order to see the error at the bottom of the screen and the webGUI just hung. I killed the s3 script using "s3_sleep -q", but the gui is still hung. Nothing new is in the syslog.

Here is a new syslog where I uninstalled all the Dynamix plugins except; plugin control and WebGUI. After doing so, I then enabled the sleep plugin and pressed Apply. I still got the error message at the bottom of the screen. This time the WebGUI did not lock up though. The s3_sleep.log only contains lines tell me if drives are idle or not. No real debugging info. Mon Aug 25 10:42:35 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle Mon Aug 25 10:43:35 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle Mon Aug 25 10:44:35 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle Mon Aug 25 10:45:35 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle Mon Aug 25 10:46:35 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle Mon Aug 25 10:47:35 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle Mon Aug 25 10:48:36 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle Mon Aug 25 10:49:36 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle Mon Aug 25 10:50:36 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle Mon Aug 25 10:51:36 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle Mon Aug 25 10:52:10 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle Mon Aug 25 10:52:17 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle Mon Aug 25 10:53:17 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle Mon Aug 25 10:54:17 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle Mon Aug 25 10:55:17 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle Mon Aug 25 13:10:59 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle Mon Aug 25 13:11:59 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle Mon Aug 25 13:12:59 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle Mon Aug 25 13:13:59 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle Mon Aug 25 13:14:59 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle Mon Aug 25 13:16:00 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle Mon Aug 25 13:17:00 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle Mon Aug 25 13:18:00 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle Mon Aug 25 13:19:00 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle Mon Aug 25 13:20:27 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle Mon Aug 25 13:20:39 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle Mon Aug 25 13:21:39 EDT 2014: Disk activity detected. Reset all counters. /dev/sdb drive state is: active/idle /dev/sdc drive state is: active/idle /dev/sdd drive state is: active/idle /dev/sde drive state is: active/idle /dev/sdf drive state is: active/idle syslog.zip

I've finally got work projects under control. I now have time to dig and and get the necessary logs. Okay, syslog zipped and attached. I had just chosen to disable the S3 plugin and hit apply, when the webGUI became unusable. Then I grabbed the syslog and my sleep config file.log.zip