From owner-freebsd-questions@FreeBSD.ORG  Thu Dec 18 08:31:18 2003
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 34CF216A4CE
	for <questions@freebsd.org>; Thu, 18 Dec 2003 08:31:18 -0800 (PST)
Received: from web41401.mail.yahoo.com (web41401.mail.yahoo.com
	[66.218.93.67])	by mx1.FreeBSD.org (Postfix) with SMTP id 752BB43DDB
	for <questions@freebsd.org>; Thu, 18 Dec 2003 08:29:38 -0800 (PST)
	(envelope-from davemac11@yahoo.com)
Message-ID: <20031218162937.15703.qmail@web41401.mail.yahoo.com>
Received: from [168.91.4.66] by web41401.mail.yahoo.com via HTTP;
	Thu, 18 Dec 2003 08:29:37 PST
Date: Thu, 18 Dec 2003 08:29:37 -0800 (PST)
From: Dave McCammon <davemac11@yahoo.com>
To: questions@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: (UPDATE) apcupsd 3.10.8 master/slave setup(whoops 3.10.6) 
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Dec 2003 16:31:18 -0000

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.
http://photos.yahoo.com/