User's Manual UPS control system
Table Of Contents
- Apcupsd User's Manual
- Release Notes
- How To Use This Manual
- Basic User's Guide
- Planning Your Installation
- Building and Installing apcupsd
- After Installation
- Configuration Examples
- Testing Apcupsd
- Troubleshooting Your Installation
- Monitoring and Tuning your UPS
- Maintaining Your UPS
- Frequently-Asked Questions
- Apcupsd Bugs
- Advanced topics
- Customizing Event Handling
- Master/Slave Configurations
- Controlling Multiple UPSes on one Machine
- Support for SNMP UPSes
- Alternate Ways To Run The Network Information Server
- apcupsd System Logging
- Installation: Windows
- Windows Version of apcupsd
- Installation: Serial-Line UPSes
- Overview of Serial-Interface UPSes
- Connecting a Serial-Line UPS to a USB Port
- Connecting a APC USB UPS to either a PC USB or Serial Port
- Cables
- Smart-Custom Cable for SmartUPSes
- Smart Signalling Cable for BackUPS CS Models
- Voltage-Signalling Cable for "dumb" UPSes
- Other APC Cables that apcupsd Supports
- Voltage Signalling Features Supported by Apcupsd for Various Cables
- Voltage Signalling
- Back-UPS Office 500 signals
- Analyses of APC Cables
- Win32 Implementation Restrictions for Simple UPSes
- Internal Apcupsd Actions for Simple Cables
- RS232 Wiring and Signal Conventions
- Pin Assignment for the Serial Port (RS-232C), 25-pin and 9-pin, Female End
- Ioctl to RS232 Correspondence
- Testing Serial-Line UPSes
- Troubleshooting Serial Line communications
- Recalibrating the UPS Runtime
- DATA Logging
- Technical Reference
- Configuration Directive Reference
- apcupsd Status Logging
- Shutown Sequence and its Discontents
- APC smart protocol
- Apcupsd --- RPM Packaging FAQ
- Credits
- Kernel Config
If you see a message to the effect of:
attach_shmarea: shared memory version mismatch (or UPS not yet ready to report)
or if all the displayed values are zero, you have not waited long enough.
Wait a bit longer and then re-execute the apcaccess status command.
If you see a message to the effect of:
APCACCESS FATAL ERROR in apcaccess.c at line 336
tcp_open: cannot connect to server localhost on port 3551.
It means that you have probably not enabled the Network Information
Server in your configuration file for apcaccess to work. This is done by
setting:
NETSERVER on
NISPORT 3551
in your apcupsd.conf file.
Communications Test
At this point, you should ensure that apcupsd is handling the connection to
the UPS correctly. This test assumes you have a UPS that speaks apcsmart
protocol, over either USB or a serial port. If you have an old-style voltage-
signaling UPS, please skip to the next section (Simulated Power Fail Test).
When apcupsd detects a problem, it generates an EVENT, which consists
of sending a message to the system log then invoking the apccontrol script
(normally in /etc/acpupsd/apccontrol) to handle the event.
In order to create an event, remove the serial port plug from the back of
your computer or from the back of the UPS. Within 6 seconds, apcupsd
should detect the lack of serial port communications and broadcast a wall
message indicating that the serial port communications was lost:
Warning communications lost with UPS lost.
63










