It works fine without, its only because I wanted to upgrade to to powerdown 2.07 which is now installed with Dynamix 2.28 I believe.

powerdown 2.06 is still on github so it should work fine with other versions or unmenu.

@megalodon

 

I just tried your 2.07 modified script.  It does not install.  I believe the fact that you did not update the MD5 check-sum is the reason.  If I manually download the power down 2.07 script and place it in \flash\packages\, it installs fine.

You mean the APCUPSD script doesn't work. Explain to me about the MD5 check-sum and how that affects it if you wouldn't mind Switchman, I only found out about all these issues today when updating Dynamix 2.2.8 and powerdown 2.07 and Im trying to stop other users updating to powerdown 2.07 and then finding out ACUPSD is still referencing powerdown 2.06. Thanks

The APCUPSD script doesn't work.  It compares the MD5 hash in the script against the file it downloads to verify a good download is my understanding.  Change the checksum to "bc2099bf945a0bc21f1527ad358e2974" and it downloads the new power-down script.

 

To verify,I changed the md5 checksum, renamed the Powerdown 2.07 script in the boot\packages\ directory and rebooted. My system downloaded the file and installed APCUPS.

 

 

Edit:  The above statement may or may not be true about requiring the correct MD5 checksum.  I subsequently identified a race condition on my system where the network interface was not up when APCUPSD is executed.  The modified plugin I made for my use is here: http://lime-technology.com/forum/index.php?topic=15583.msg324909#msg324909

 

 

<FILE Name="/boot/packages/powerdown-2.07-noarch-unRAID.tgz" Run="CTRLALTDEL=YES upgradepkg --install-new">
<URL>--no-check-certificate https://github.com/dlandon/unraid-snap/raw/master/powerdown-2.07-noarch-unRAID.tgz</URL>
<MD5>bc2099bf945a0bc21f1527ad358e2974</MD5>

Changed the MD5 checksum as you suggested in the script. Thanks. Im going to look into this some more but its good that you spotted it. I wonder if powerdown 2.07 that was installed manually by myself means it knows its already there so its not bothering to install it and hence I get no failure message. Where did you find the MD5 checksum, no mention of it is on the powerdown page 1 when dlandon talks about changing the APCUPSD script so it loads 2.07 and not a prior version?

Attached is a modified version of the script I made for my use.  If the network interface is not up, it can't download the files if it needs to.  I am sharing it in-case anyone else wants the changes.

 

2014-08-31 (6_nr-1sd) - Switchman - Changed the MD5 checksum for "powerdown-2.07-noarch-unRAID.tg".  Identified a race condition, on my
system, where the network interface was not up yet when the trying to install the powerdown script.  Copied code from PhAzE's pluggins that check
if the network is up before proceeding with installation.

 

Apcupsd-3.14.12-i486-6_nr-1sd.plg.txt

I wonder if powerdown 2.07 that was installed manually by myself means it knows its already there so its not bothering to install it and hence I get no failure message.

 

That is exactly what it does.  If you look in /boot/packages/ you will see the "powerdown-2.07-noarch-unRAID.tgz" file.  If the file already exists, it will not download it.  If it does not exist, it will download it.

 

 

Where did you find the MD5 checksum, no mention of it is on the powerdown page 1 when dlandon talks about changing the APCUPSD script so it loads 2.07 and not a prior version?

 

 

Not sure if it is on Github.  Probably is but I don't know where to find it so I cheated.

 

Telnet into server

cd /boot/

wget --no-check-certificate https://github.com/dlandon/unraid-snap/raw/master/powerdown-2.07-noarch-unRAID.tgz

md5sum powerdown-2.07-noarch-unRAID.tgz

# Deleted the file and did it a second time to ensure I got the same hash.

 

I am not 100% sure the correct MD5 hash must be present, but it does not hurt.  The first failure I experienced may have been due to the race condition I identified on my system.  That is why I posted my mods to the script.

I couldn't find it on github so thats why I was asking. Interesting about your network, did many others have had the same problem as you. Im tempted to instal your mod of the script but as I don't have no issues with the network coming up in time its not really worth it now the MD5 checksum has been changed thanks to you and I will be moving to v6 before I change anything that would affect my network speed.

... did many others have had the same problem as you.

 

No clue, I just purchased and installed the UPS about a week ago.  Never installed APCUPSD till then.  The powerdown script was installed from Unraid.  I wanted the changes introduced in 2.07 so used your version of the script when I hit an issue.  In reality, after the 2.07 powerdown script was on my system it would have been fine as it would not need to be downloaded again, but I wanted it to work correctly so made the extra mods. 

 

This is the second test of deleting the powerdown script from the /packages/ directory. It pauses until the network is up then downloads the file.

 

 

 

Aug 31 16:49:09 Tower logger: Installing user plugins

Aug 31 16:49:09 Tower logger: installing plugin: Apcupsd-3.14.12-i486-6_nr-1sd

Aug 31 16:49:09 Tower logger:  file /tmp/chk-network: successfully wrote INLINE file contents

Aug 31 16:49:12 Tower kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx (Network)

Aug 31 16:49:13 Tower logger:  /bin/bash /tmp/chk-network ... success

Aug 31 16:49:13 Tower logger:  file /boot/packages/apcupsd-3.14.12-i486-1_nro.tgz: already exists

Aug 31 16:49:13 Tower logger:  upgradepkg --install-new /boot/packages/apcupsd-3.14.12-i486-1_nro.tgz ...

Aug 31 16:49:13 Tower logger: +==============================================================================

Aug 31 16:49:13 Tower logger: | Installing new package /boot/packages/apcupsd-3.14.12-i486-1_nro.tgz

Aug 31 16:49:13 Tower logger: +==============================================================================

Aug 31 16:49:13 Tower logger:

Aug 31 16:49:13 Tower logger: Verifying package apcupsd-3.14.12-i486-1_nro.tgz.

Aug 31 16:49:13 Tower logger: Installing package apcupsd-3.14.12-i486-1_nro.tgz:

---> Removed lines associated with PACKAGE DESCRIPTION

Aug 31 16:49:14 Tower logger: Executing install script for apcupsd-3.14.12-i486-1_nro.tgz.

Aug 31 16:49:14 Tower logger: Package apcupsd-3.14.12-i486-1_nro.tgz installed.

Aug 31 16:49:14 Tower logger:

Aug 31 16:49:14 Tower logger:

Aug 31 16:49:14 Tower logger: success

Aug 31 16:49:15 Tower logger:  file /boot/packages/powerdown-2.07-noarch-unRAID.tgz: downloading from --no-check-certificate https://github.com/dlandon/unraid-snap/raw/master/powerdown-2.07-noarch-unRAID.tgz ... success

Aug 31 16:49:15 Tower logger:  CTRLALTDEL=YES upgradepkg --install-new /boot/packages/powerdown-2.07-noarch-unRAID.tgz ...

 

 

 

Should I install the old version from the pkg manager apcupsd-3.14.10-i486-1 or the new version from the plug in page? 3.14.10-i486-4_rlw  http://lime-technology.com/wiki/index.php/UnRAID5_Plugins....  Im running on the stable 5.0.5....

 

just bought my self a APC Back-UPS Pro 1000 ..... thank you.

 

NVM I got it working.... thank you all!    Cheers!  Wen't with the latest version on the plug in page....

APCUPSD Plugin updated along with MD5 checksum for powerdown 2.10.

Remember to remove the .txt from the end of the file.

Apcupsd-3.14.12-i486-7_nr-aw.plg.txt

Thanks for the plugin. Just bought a small UPS and the plugin seems to load properly.

 

However, I don't really know, as I'm not sure what the plugin is really supposed to achieve other than showing me the UPS status and shutting down the server if the power fails. (Haven't actually tested if it powers down yet or not.)

 

Obviously that's the major function of the UPS, but I was wondering whether there is any more to this plugin? i.e. is there a way of saying if the UPS ever kicks in, to immediately power down. That kind of thing. No idea if this is possible or not, but I'm genuinely just wondering if I'm missing something, given there's no obvious documentation.

Thanks for the plugin. Just bought a small UPS and the plugin seems to load properly.

 

However, I don't really know, as I'm not sure what the plugin is really supposed to achieve other than showing me the UPS status and shutting down the server if the power fails. (Haven't actually tested if it powers down yet or not.)

 

Obviously that's the major function of the UPS, but I was wondering whether there is any more to this plugin? i.e. is there a way of saying if the UPS ever kicks in, to immediately power down. That kind of thing. No idea if this is possible or not, but I'm genuinely just wondering if I'm missing something, given there's no obvious documentation.

 

Set the 'Timeout:' to the number of seconds to wait until the array shuts down.  If you set it to zero, the timeout is turned off.  I would set it to something greater than 60 seconds so you don't shut down too quickly in case the power returns.

Thanks for the plugin. Just bought a small UPS and the plugin seems to load properly.

 

However, I don't really know, as I'm not sure what the plugin is really supposed to achieve other than showing me the UPS status and shutting down the server if the power fails. (Haven't actually tested if it powers down yet or not.)

 

Obviously that's the major function of the UPS, but I was wondering whether there is any more to this plugin? i.e. is there a way of saying if the UPS ever kicks in, to immediately power down. That kind of thing. No idea if this is possible or not, but I'm genuinely just wondering if I'm missing something, given there's no obvious documentation.

 

Set the 'Timeout:' to the number of seconds to wait until the array shuts down.  If you set it to zero, the timeout is turned off.  I would set it to something greater than 60 seconds so you don't shut down too quickly in case the power returns.

 

Ok thanks. The UPS I have is just a little guy, so I think it'd probably max out at ten minutes anyway, so 60 seconds sounds good. (APC Back-UPS® NS 600VA 8-Outlet Power-Saving UPS)

 

What are the other settings here? (sorry if this is documented, I couldn't find anything)

 

Thanks for the plugin. Just bought a small UPS and the plugin seems to load properly.

 

However, I don't really know, as I'm not sure what the plugin is really supposed to achieve other than showing me the UPS status and shutting down the server if the power fails. (Haven't actually tested if it powers down yet or not.)

 

Obviously that's the major function of the UPS, but I was wondering whether there is any more to this plugin? i.e. is there a way of saying if the UPS ever kicks in, to immediately power down. That kind of thing. No idea if this is possible or not, but I'm genuinely just wondering if I'm missing something, given there's no obvious documentation.

 

Set the 'Timeout:' to the number of seconds to wait until the array shuts down.  If you set it to zero, the timeout is turned off.  I would set it to something greater than 60 seconds so you don't shut down too quickly in case the power returns.

 

Ok thanks. The UPS I have is just a little guy, so I think it'd probably max out at ten minutes anyway, so 60 seconds sounds good. (APC Back-UPS® NS 600VA 8-Outlet Power-Saving UPS)

 

What are the other settings here? (sorry if this is documented, I couldn't find anything)

 

That's because it is already documented by apcupsd,  here is a link to some of the commands.  http://www.apcupsd.com/manual/manual.html#configuration-directives-used-during-power-failures

 

Just to let you know, The way you have it set up in the picture, the ups will shut down when there is 10% of power left in the batteries or when the batteries have less than 10 minutes of runtime left or after 300 seconds (5 minutes) of running without power.

Thanks.

 

I just picked this thing up on a whim because it was cheap, so I'm about as clueless as it gets about this crap. Thanks for the link. Time to make some tweaks.

Ok thanks. The UPS I have is just a little guy, so I think it'd probably max out at ten minutes anyway, so 60 seconds sounds good.

I suspect you will actually only see a couple minutes, and it may not have enough juice to get you all the way through a proper shutdown. Do you have access to a watt meter to see how much power your rig draws with all the drives spun up? The UPS you quoted is rated to power 360 Watts (its full load capacity) for 3 minutes.

No watt meter, no. But it's not that big an array, drive-wise, so I can't imagine it being that much of a hog.

 

Anyway, once it charged up to 90%, I unplugged it. It immediately decided that 90%  would last about 12 minutes. It hit 10 minutes and then shut down, as desired. When I brought it back online, the tool reported the battery was 55% full.

 

The array was spun down at the time, but generally when I stop the array it's 15-20 seconds, nothing more.

 

So yeah, it's not going to do much more than give a minute to see if power is coming back online, but it should be adequate to shut the thing down rather than see it just fail. My power never really just flickers, if it's going off, it's because half of Philadelphia is going off, so I'm happy enough with it just shutting down asap.

 

Obviously it could be a concern when the battery loses some of it's charge, but I'll keep an eye on it.

dlandon updated the power down script to 2.13, http://lime-technology.com/forum/index.php?topic=31735.msg288775#msg288775

 

I updated my copy of APCUPSD to the new version.  Here are the changes needed in the pkg to use the new version of Powerdown and its MD5 checksum.

 

Old code:

<FILE Name="/boot/packages/powerdown-2.12-noarch-unRAID.tgz" Run="CTRLALTDEL=YES upgradepkg --install-new">
<URL>--no-check-certificate https://github.com/dlandon/unraid-snap/raw/master/powerdown-2.12-noarch-unRAID.tgz</URL>
<MD5>122bfe1b9af60b2241ac9d5fabe2057a</MD5>

 

to

 

<FILE Name="/boot/packages/powerdown-2.13-noarch-unRAID.tgz" Run="CTRLALTDEL=YES upgradepkg --install-new">
<URL>--no-check-certificate https://github.com/dlandon/unraid-snap/raw/master/powerdown-2.13-noarch-unRAID.tgz</URL>
<MD5>6fdf7064e1862ca40735dbc848a05357</MD5>

 

Shutdown and rebooted my system as a test.  It downloaded and installed the new script.

I installed the latest version of the plugin and upon testing, it appears to stop the array cleanly after a simulated power failure.  However, it doesn't seem to kill my UPS with the option set to YES after the server finishes stopping the array.  I thought perhaps the UPS would shutoff after the server shuts down (the array is stopped but remains powered up), but turning the server off manually also does not kill the UPS.  The UPS reports has a "StayOff by UI for: 60s" on the display, and it is an APC SMX1000.  Any ideas on if this is abnormal behavior?  Should unRAID shutdown after the array is stopped?  Should the UPS be killed after the array is stopped?

Should unRAID shutdown after the array is stopped?  Should the UPS be killed after the array is stopped?

Yes, and yes!

Can I use this plugin with unRAID 6.0b12 and how can I install it correctly?

Can I use this plugin with unRAID 6.0b12 and how can I install it correctly?

 

See this Thread:

 

    http://lime-technology.com/forum/index.php?topic=34994.0

Thanks...found it a minute ago.

Does anybody know if the Kill UPS function works in a specific way? it seems to work but it kills it quite some time after my server shuts off.

 

 

Thanks