Airw0lf

RAINMAN - does it shut your machine down cleanly on unRAID 6.2.2?

Will do so and report back...

Problem is, there have been a lot of changes in unRAID, and I don't believe this plugin is being updated. You'll have to tell us if it still works, but I suspect it needs a little tweaking. I can confirm the service starts correctly, recognises my UPS, reports stats like load, battery, etc. It also detects and alerts when the UPS switches to battery mode and back again. What I haven't tested yet is the shutdown of the unRAID server - was hoping to understand a bit more about this first. I suppose I'll just have to test it and see - what do you others think?

Hi guys, I've just installed NUT and I think it recognises my UPS well enough. My question is around the Powerdown plugin - the front page of the thread "highly recommends" installing it but then I see that Powerdown is deprecated for unRAID 6.2. Does this mean that NUT will be able to cleanly shut down my unRAID 6.2.2 without any issues if I don't have Powerdown? I.e., will NUT ensure that my plugins like Mylar, SABNZBd and so on are cleanly shut down before taking down the server?

Likely that. 1.0 marks a big change for sab vs 0.7 so I recommend deleting the config folder and starting fresh to be safe. Some of the settings changed. Remember to set the "article cache limit" to something like 64m or 128m as I found it likes to crash on Unraid with large downloads unless that value is increased. There's definitely something weird going on with 1.0.0. I am not sure if it's an issue with the unRAID plugin or SABnzbd or both. In my case ever since I upgraded to 1.0.0 I get endless errors like this: 2016-03-27 11:47:25,100::ERROR::[config:842] Cannot create backup file for /boot/sabnzbd/sabnzbd.ini.bak 2016-03-27 11:47:25,100::INFO::[config:843] Traceback: Traceback (most recent call last): File "/usr/local/sabnzbd/sabnzbd/config.py", line 839, in save_config shutil.copymode(filename, bakname) File "/usr/local/PhAzE-Common/usr/lib64/python2.7/shutil.py", line 91, in copymode os.chmod(dst, mode) OSError: [Errno 1] Operation not permitted: '/boot/sabnzbd/sabnzbd.ini.bak' Everything seems to work fine but the real problem is going in to the web interface and changing settings - this error seems to prevent any setting changes from being saved. I also tried a complete clean start after nuking my config folder. I go to the wizard and set everything up but from there it seems unable to save the settings and sabnzbd can't be reached via the web interface. I think it gets stuck in a limbo where the ini settings cannot be saved and there aren't enough settings to launch either. I've tried searching the net for similar issues and the closest thing I've come across is http://forums.sabnzbd.org/viewtopic.php?t=11051 where they are talking about the proper location of the config file. So could the issue be launching sabnzbd via plugin like this: /usr/local/sabnzbd/SABnzbd.py -d -s 0.0.0.0:5847 --config-file /boot/sabnzbd --pidfile /var/run/Sabnzbd/Sabnzbd.pid ? Maybe sabnzbd doesn't like where the config file is placed and gets confused?

I'm a user of the Opera browser and have been using it to login to my unraid server's Web Management Utility. All was going well until the latest version - 11.50. Now I get the following error: "Connection closed by remote server." I don't even get as far as the login dialog box popping up. Everything works fine on Firefox. I can login to my SABnzbd server running on my unraid box using either Opera or Firefox. This leads me to believe that something in the way the unraid server Web Management Utility authenticates is upsetting Opera. Any other Opera users care to comment? And before you ask - normal web browsing, etc. works fine in Opera as well as Firefox. It's clearly not a network connectivity problem but something Opera doesn't like about unraid. If someone else can confirm the issue then I could probably file a report with Opera as well.