I'm new to UPS monitoring, but I googled that the most appropriate tool
for my needs (single server attached to an APC MartUPS 750XL) is acupsd.
I "aptitude install"'d it (testing) and then looked through
/etc/apcupsd/apcupsd.conf, and left everything alone; to my untrained
eye, everything looks satisfactory. I then edited /etc/default/apcupsd
so that the ISCONFIGURED line = yes.
I then "/etc/init.d/apcupsd start".
ps ax reveals:
28402 ? Ssl 0:00 /sbin/apcupsd
The online web documentation suggested running apcaccess, which reveals:
[EMAIL PROTECTED]:/var/log:> sudo apcaccess
Password:
APC : 001,051,1213
DATE : Tue Jul 15 10:29:02 CDT 2008
HOSTNAME : goshen
RELEASE : 3.12.4
VERSION : 3.12.4 (19 August 2006) debian
UPSNAME : UPS_IDEN
CABLE : Custom Cable Smart
MODEL : Smart-UPS 750 XL
UPSMODE : Stand Alone
STARTTIME: Tue Jul 15 10:10:57 CDT 2008
STATUS : TRIM ONLINE
LINEV : 127.4 Volts
LOADPCT : 16.9 Percent Load Capacity
BCHARGE : 100.0 Percent
TIMELEFT : 55.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME : 0 Seconds
MAXLINEV : 127.4 Volts
MINLINEV : 126.7 Volts
OUTPUTV : 113.0 Volts
SENSE : High
DWAKE : 000 Seconds
DSHUTD : 090 Seconds
DLOWBATT : 02 Minutes
LOTRANS : 106.0 Volts
HITRANS : 127.0 Volts
RETPCT : 000.0 Percent
ITEMP : 27.9 C Internal
ALARMDEL : 5 seconds
BATTV : 27.5 Volts
LINEFREQ : 60.2 Hz
LASTXFER : Unacceptable line voltage changes
NUMXFERS : 0
TONBATT : 0 seconds
CUMONBATT: 0 seconds
XOFFBATT : N/A
SELFTEST : NO
STESTI : OFF
STATFLAG : 0x0700000A Status Flag
REG1 : 0x00 Register 1
REG2 : 0x00 Register 2
REG3 : 0x00 Register 3
MANDATE : 11/19/04
SERIALNO : AS0447133208
BATTDATE : 11/19/04
NOMOUTV : 120
NOMBATTV : 24.0
EXTBATTS : 0
FIRMWARE : 630.3.D
APCMODEL : FWD
END APC : Tue Jul 15 10:29:05 CDT 2008
That same documentation says I need to test communication
(http://www.apcupsd.com/manual/Testing_Apcupsd.html) by disconnecting
the serial cable and seeing if a message pops up or shows up in the log
files (/var/log/syslog I assume, or /var/log/apcupsd.events). I
unplugged it for about 10-15 seconds, then reconnected it.
syslog shows:
Jul 15 09:52:46 goshen apcupsd[28224]: apcupsd 3.12.4 (19 August 2006)
debian startup succeeded
Jul 15 09:52:48 goshen apcupsd[28224]: NIS server startup succeeded
and apcupsd.events shows:
[EMAIL PROTECTED]:/var/log:> sudo cat apcupsd.events
Tue Jul 15 09:52:46 CDT 2008 apcupsd 3.12.4 (19 August 2006) debian
startup succeeded
I then modified the /etc/apcupsd/apcupsd.conf file, changing the
STATTIME from 0 (default, disabled) to 10, and then did an
"/etc/init.d/apcupsd restart".
The expected /var/log/apcupsd.status file did not appear, and the only
changes in /var/log/apcupsd.events was an additional note of
stopping/starting the daemon:
[EMAIL PROTECTED]:/var/log:> sudo cat apcupsd.events
Tue Jul 15 09:52:46 CDT 2008 apcupsd 3.12.4 (19 August 2006) debian
startup succeeded
Tue Jul 15 10:10:46 CDT 2008 apcupsd exiting, signal 15
Tue Jul 15 10:10:46 CDT 2008 apcupsd shutdown succeeded
Tue Jul 15 10:11:11 CDT 2008 apcupsd 3.12.4 (19 August 2006) debian
startup succeeded
I then ran apcaccess again, and now the /var/log/apcupsd.status file
exists, with the contents of the output of apcaccess. Later I ran
apcaccess again, and it seems to have overwritten the
/var/log/apcupsd.status file with the new run.
In short, I'm not seeing the activity in the apcupsd.event and
apcupsd.status logfiles I would expect to see based on my understanding
of the documentation.
Any suggestions/clues?
Thanks!
--
Kent West <*)))><
http://kentwest.blogspot.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
