Cannot resolve slave name XXX
To contact the slave, the slave name given in the configuration file must be resolved to an IP address. In this case, apcupsd could not get the IP address. Either the slave name is incorrect or your DNS may not be working.Got slave shutdown from SSS
This message should not be printed as it is not yet used.Cannot write to slave SSS
This message occurs when the master attempts to send a message to the slave SSS and gets an error. It indicates that either the slave machine is not responding (apcupsd died, the system crashed, ...) or that the network is down.Cannot read magic from slave SSS
This message indicates that the master attempted to read the code key from the slave SSS and it did not match the value expected. A common cause of this problem is that the master and slave versions of apcupsd are not the same. Please be sure you are running the same version of apcupsd on all your master and slave machines.Connect to slave SSS failed
This message is logged when the master attempts to connect to slave SSS and no connection is accepted. The most common cause of this problem is that the slave copy of apcuspd is not yet ready to accept connections or is not running. Generally, apcupsd will retry the connection a bit later. If the problem is persistent, it can indicate a network problem or the slave name on the SLAVE directive of the master's configuration file is incorrect.Cannot open stream socket
This indicates a fundamental networking problem on your system -- either a lack of sufficient resources or you have not configured TCP/IP operations.Can't resolve master name MMM
This message is logged when the slave attempts to resolve the name given on the MASTER configuration directive to an IP address. It probably means that the master name MMM is not defined or that your DNS is not properly working. Check the name MMM, or use an explicit IP address on the MASTER configuration directive in the slave's configuration file.Cannot bind local address, probably already in use
This means that the slave has attempted to bind the port number so that it can listen for messages from the master. This can occur if already have a copy of apcupsd running, or you have previously run apcupsd in the past 5 or 10 minutes, because occasionally the operating system will not shutdown a port correctly for 5 to 10 minutes after a program exits. In this case, you can either wait a few minutes for the problem to go away, or use a different port in both your master and slave configuration files.Socket accept error
The slave got an error waiting on the accept() system call. This is probably due to a fundamental networking problem.Unauthorised attempt from master MMM
The master named MMM (probably an IP address) contacted the slave but MMM is not the master that was listed on the MASTER configuration directive in /etc/apcupsd.conf, and consequently, it is not authorized to communicate with the slave. Please check that your MASTER and SLAVE names in your slave and master configuration files respectively are correct.Read failure from socket
The slave got an error reading the socket open to the master. This indicates a fundamental networking problem.Bad APC magic from master: MMM
The slave received a code key from the master that does not correspond to the one expected by the slave. The most common cause of this problem is that you are running a different version of apcupsd on the master and the slave. Please ensure that you are running the same version of apcupsd on all your master and slaves.Bad user magic from master: MMM
This message indicates that the master and slave have previously communicated, but that the code key transmitted with the most recent message from the master does not correspond to what the slave expects. This problem is probably due to a network error or some other user or machine contacting the slave on the network port.
I thought I'd pass on some information I've obtained which you'll probably eventually need. Besides, by writing it down I'll be able to find it the next time. I started installing mine in 1995-1996. Lead-acid batteries have a finite life even if not subjected to deep discharge cycles. For the batteries used by APC, this is typically four to six years. As part of the self-test cycle, the UPS measures the voltage of the battery at full charge (which falls as the battery ages), and if it's below about 90% of the value for a new battery, it sets off the "Replace battery" alarm, which it repeats every day. [on apcupsd versions prior to 3.8.0, this message is sent once, on version 3.8.0, it is sent every 9 hours - KES]. You will occasionally get a false alarm. It's a good idea if you get an alarm to repeat the self-test the next day and see if the alarm goes away. If the alarm is persistent, you need to replace the batteries, which can be done without powering down the UPS or load-you just open up the battery door, take out the old batteries, and hook up the new ones.And André Hendrick says:APC makes "Replacement Battery Units" for each of the SmartUPS models, but they sell them directly only in the U.S.
It's best to wait until the low battery alarm before ordering a replacement-keeping batteries on the shelf reduces their life unless you keep them fully charged.
[For replacement batteries] You need to goto you your local Yamaha SeaDoo shop. There are 35 AMP Hour deep cycle marine batteries that are direct replacements. These are gel-cel and will double the runtime and/or cut your recharge time in half.JetWorks
WP-ACC Battery, JET WORKS
1587 Monrovia Ave
Newport Beach, CA 92663WP-35
This is in my SU1250 and with 70% load I get 38 minutes. NO JOKE! My SU3000NET did not get a boost in runtime but I have a 45 minute full recovery after drain a 95% drain.
make apctest
Then, you simply execute it with:./apctest
and follow the instructions. It will place the output from the session in the file apctest.output. If you are not able to resolve your problem, sometimes we can help if you email us this output file along with your apcupsd.conf file.