Hello,
I am presently upgrading my servers. The old ones are running Suse 10.1 and I
am upgrading to the most recent Debian.
Oh, and I am not an IT guy rather a hacker who loves Linux and seems to enjoy
getting myself confused.
Presently I am trying to get the Nut running and am having problems.
I have the master server working but it does not inform the slave server to
shut down.
For the most part I borrowed the settings from my present servers (the ones
running Suse 10.1).
Below is the setup (all references are from the Nut perspective) and when I
supply low batter/AC the master server shuts down but the client server does
not.
Keep in mind I copied the parameters from my existing server (master
192.168.0.3, clien 192.168.0.4) which has been running fine for years (although
I remember many head banging times getting that to run at the time).
My new server IP's are: 192.168.0.7 is the master 192.168.0.6 is the
client
Thank you for any help - Steve
On the Master
Server I have:
nut.conf
MODE=netserver
ups.conf
[sdrups]
driver =
genericups
port = /dev/ttyS1
desc = "For
Server & Backup"
upstype=9
upsd.conf
ACL all 0.0.0.0/0
ACL localhost
127.0.0.1/255.255.255.0
ACL server
192.168.0.6/255.255.255.0
ACCEPT localhost
ACCEPT server
REJECT all
upsd.users
[root]
password =
autocadba2
upsmon master
instcmds = ALL
On the Client
Server I have:
nut.conf
MODE=netserver
ups.conf
[sdrups]
driver =
genericups
port = /dev/ttyS1
desc = "For
Server & Backup"
upstype=9
upsd.conf
ACL all 0.0.0.0/0
ACL localhost
127.0.0.1/255.255.255.0
ACL backup
192.168.0.7/255.255.255.0
ACCEPT localhost
ACCEPT backup
REJECT all
upsd.users
[root]
password =
autocadba2
upsmon master
instcmds = ALL
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser