apcupsd doesn't shutdown?

Please move this to "user customization" or "Application" please? I apparently posted it in the wrong place.

Mar 28 14:35:35 Tower apcupsd[16321]: apcupsd 3.14.3 (20 January 2008) slackware startup succeeded
Mar 28 14:35:35 Tower apcupsd[16321]: NIS server startup succeeded
//I pull the power here
Mar 28 14:38:16 Tower apcupsd[16321]: Power failure.
Mar 28 14:38:22 Tower apcupsd[16321]: Running on UPS batteries.
[..transmission logs..]
Mar 28 14:43:23 Tower apcupsd[16321]: Reached run time limit on batteries.
Mar 28 14:43:23 Tower apcupsd[16321]: Initiating system shutdown!
Mar 28 14:43:23 Tower apcupsd[16321]: User logins prohibited

Manually typing "powerdown" works fine in terminal:-

root@Tower:~# powerdown
Capturing information to syslog. Please wait...
[..lots and lots of logs about how it's copying the system log 'n stopping array..]
Broadcast message from root (pts/0) (Thu Mar 28 14:48:27 2013):

The system is going down for system halt NOW!
root@Tower:~# 

Am I missing something? I'm going to go ahead and fiddle with some stuff, however, I will note:-

Sabnzbd, transmission & a parity check were all using the drives, so, the drives were in use. In this a problem? If so, how do I get it to kill everything to get it to shutdown?

EDIT:- After a restart & pulling the plug, it's logging loads of smart data to the log.

EDIT:- After smart, it went onto ethernet data, and, now it's back to smart data.

EDIT:- After smart, it went onto emhttp data, and, now it's back to smart data. It loves 'tis smart data, eh? So far been a good two minutes worth of smart logging, I can't think this is too good during a powercut, wasting power on smart data.

EDIT:- After smart, it's onto share data, and, now it's back to smart.

EDIT:- Now it's turning off my NIC on eth0. I honestly don't think this is really what it should be doing during a powercut...

Now I can't even log the data or remotely turn it off due to the fact it's turned eth0 off. So, I guess I will really just have to wait and let the power cut. Greeaattt, I'm going to have to do a parity check.

EDIT:- Well, apparently the UPS was making so much noise I didn't hear the computer turn off...

Two things however:-

A. Wasn't it meant to turn the UPS off? How do I get that to work?

B. How do I tell it not to log every disk's smart report twelve times over. The best thing in a power cut I feel would be to power off, I can grab smart reports when it turns on. Unless someone can tell me why this isn't a good idea?

EDIT:-

If you were to reboot your computer during the grace period, the UPS could then suddenly turn off the power (this happened to me). To avoid this problem, always wait for your UPS to power itself off, or power if off manually before restarting your computer. On my system, the UPS is configured as at the factory to have a 180 second grace period before shutting off the power. During this type of testing, 180 seconds seems like an eternity, so please take care to either wait or manually power off your UPS. To determine what grace period is programmed into your UPS EEPROM, run 'apcaccess eprom' and look at the "Shutdown grace delay".

http://www.apcupsd.org/manual/manual.html

I only waited ~ 60 seconds. Let's try this again.

EDIT:- Just got to pulling the plug because apparently I just noticed my whole sabnzbd plg install configuration got corrupted some how. Had to fix that & all the DIRs it randomly made. Pulled the plug, got to wait about 10 minutes.

EDIT:- Went to go place my HTPC in it's case (That came at the same time as the UPS), throughout building it I heard the MOBO pass BIOS twice, meaning, it shut down twice in the last hour and a half. I guess the UPS isn't providing enough power? This is directly plugged into the wall, FYI. But, the UPS also didn't shutdown.