(UPDATE) apcupsd 3.10.8 master/slave setup(whoops 3.10.6)

Dave McCammon davemac11 at yahoo.com
Thu Dec 18 08:31:18 PST 2003

For the record.

The quick fix for Apcupsd 3.10.6 hangup problems was
to delete the "apcaccess status" parts out of the
scripts in /usr/local/etc/apcupsd/. (commok,
onbattery, etc...). Event messages still get "wall"ed
and mail still gets sent. Just non of the UPS status
information in messages. The status info can still be
gotten by doing a "apcaccess status" on the command
line (which used to not work, either).

What was happening was that when the power to the UPS
was pulled...the master server's apcupsd got stuck in
the script(or something associate with the "status"
part of the script) which stalled apcupsd. No slaves
could contact the master and, when power was restored,
apcupsd wouldn't respond to the event.

I believe this also happened when in standalone mode,
come to think of it.

Anyway, thanks to Lewis Watson in the apcupsd-user list.

Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.

More information about the freebsd-questions mailing list