RE: [Apcupsd-users] master/slave problems

[Allen C. <all...@ya...>]

Well, I am trying to get version 3.10.5 to work on Red Hat 8 now.  I got it
working great in standalone mode, but now I can't get it to work as a master
because I get the following error:

Old network code disabled.  Use -enable-oldnet to enable
Apcupsd FATAL ERROR in apcupsd.c at line 353
Error setting up master

So, I read up on this and it seems that the old network code is just
disabled in the RPM?  So I figured I'd use the new method of networking
which is to use NIS.  However, I don't really know how to configure the
master for this (unless it is just configured as a standalone and the slave
connects via NIS on port 3551 and the DEVICE directive and does all the work
from there).  But the problem comes back to an earlier issue where I can't
set UPSTYPE net on the slave because it says I don't have a valid driver.
So is there a way to enable the old networking code with the RPM
installation?  I'd prefer not to compile this from source just because the
RPMs are so convenient and simpler to remove usually (not that I really plan
on removing this after I get it working).

Sorry to keep annoying you with these problems, but I was so close to
getting things to work earlier that I just can't stop now.

Oh, and once I get everything working, I plan on doing a real test without
the TIMEOUT directive on the master to make sure my UPS will actually tell
the master when the battery is almost exhausted.  Because I definitely want
to milk it for as long as possible.

Thanks again.  I'll keep reading, but I've read the entire manual at least
once I'm sure.

-----Original Message-----
From: Kern Sibbald [mailto:ke...@si...]
Sent: Monday, April 07, 2003 4:20 PM
To: Allen Crawford
Cc: APCUPSD List
Subject: RE: [Apcupsd-users] master/slave problems

Hello,

I don't understand the reason for the backups/dumb problem, but
it should be no problem to have dumb in the slave machine as it
is really the same as backups (on version 3.10.x).

In principle, version 3.8.6 *should* network with 3.10, but
I haven't tested it for ages, then throw Windows into the pot
and there are likely to be problems.

Your config statements all look OK to me.

At this point, I don't have many suggestions (sorry) other than to
try running 3.10.5 (or 3.10.6 from the CVS) on your RH 8.0
server. I'd give it about a 50-50 chance of fixing the
problems.

Best regards,

Kern

PS: By the way you *should* be able to remove the TIMEOUT
    from your master since the 20C cable supports the low
    battery signal. This might give you more than 10 minutes
    of time on batteries.  That said -- test before you rely
    on it.


On Mon, 2003-04-07 at 22:38, Allen Crawford wrote:
> Well, when I set UPSTYPE to backups (as it is in my master config file) I
> cannot start the service (I get the error 1067: the process terminated
> unexpectedly).  If I change it to UPSTYPE dumb, then it will load just
fine,
> but it doesn't ever appear to connect to the master.  And watching the
> apcupsd.events file on the master doesn't ever show it connecting to the
> slave.  But in case you forgot, I am running version 3.8.6 on Red Hat 8
for
> my master, and the latest Win32 version on my Windows 2000 Server.  Will
> this be a problem?  Do I need to run a 3.10 version on my Red Hat 8 box?
I
> checked out your examples and mine seem to be correct except for possibly
> the UPSTYPE directive.  But I cannot make the master file use "dumb" and I
> can't seem to make the slave use "backups".  Here is what I have right
now:
>
> Master:
>
> UPSCABLE 940-0020C
> UPSTYPE backups
> DEVICE /dev/ttyS0
> LOCKFILE /var/lock/subsys
> BATTERYLEVEL 5
> MINUTES 3
> TIMEOUT 600
> ANNOY 300
> ANNOYDELAY 60
> NOLOGON disable
> KILLDELAY 0
> NETSERVER on
> NISPORT 7000
> EVENTSFILE /var/log/apcupsd.events
> STATTIME 0
> STATFILE /var/log/apcupsd.status
> LOGSTATS off
> DATATIME 0
> UPSNAME BACK-UPS
> UPSCLASS netmaster
> UPSMODE net
> NETACCESS true
> NETTIME 100
> NETPORT 6666
> SLAVE 192.168.1.4
>
> Slave:
>
> UPSCABLE ether
> UPSTYPE dumb  <-- setting "UPSTYPE backups" fails each time
> DEVICE /dev/com1  <-- should be ignored from what I've read
> LOCKFILE /apcupsd/etc/apcupsd
> BATTERYLEVEL 5
> MINUTES 3
> TIMEOUT 30
> ANNOY 300
> ANNOYDELAY 10
> NOLOGON disable
> KILLDELAY 0
> NETSERVER off
> EVENTSFILE /apcupsd/etc/apcupsd/apcupsd.events
> EVENTSFILEMAX 10
> UPSCLASS netslave
> UPSMODE net
> NETTIME 100
> NETPORT 6666
> MASTER 192.168.1.3
> STATTIME 0
> STATFILE /apcupsd/etc/apcupsd/apcupsd.status
> LOGSTATS off
> DATATIME 0
> UPSNAME BACK-UPS
>
> Any other tips?