Arjen, all,
Just dropping a note on two points. First, Voltages are perfect in
2.4.1 for
the Cyberpower ups's. Glad to see I'm not pushing 20+ any more:
http://www.3111skyline.com/nut/
Second, even though the changes to where the monitor lines go in the
configs
and changes from ACCEPT, etc.. to LISTEN are fairly old now, the documentation
for setting up monitoring for multiple UPSs isn't that clear. (I may not have it
100% correct either - see 3 below). In my case, I have 2 server each with
identical CP1000AVRLCD upses where I simply want each to server as the master
for the machine they are attached to, but be able to monitor both from each
machine.
Third, each machine has identical configs (accept for swapping the
master/slave
designations and IP addresses in the LISTEN lines). I have it working with the
following config:
hosts.conf
MONITOR [email protected] "Archangel CP1000AVRLCD UPS"
MONITOR nirvana_...@localhost "Nirvana CP1000AVRLCD UPS"
nut.conf
MODE = standalone
ups.conf
[nirvana_ups]
driver = usbhid-ups
port = /dev/hiddev0
desc = "Nirvana CP1000AVRLCD UPS"
[archangel_ups]
driver = usbhid-ups
port = /dev/hiddev0
desc = "Archangel CP1000AVRLCD UPS"
upsd.conf
LISTEN 127.0.0.1
LISTEN 192.168.6.17
upsd.users
[upsmaster]
password = notRealm
upsmon master
[upsslave]
password = notReals
upsmon slave
[david]
password = notReald
actions = SET
instcmds = ALL
upsmon.conf
MONITOR [email protected] 1 david notReald slave
MONITOR nirvana_...@localhost 1 david notReald master
MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -h +0"
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 15
DEADTIME 15
POWERDOWNFLAG /etc/killpower
RBWARNTIME 43200
NOCOMMWARNTIME 300
FINALDELAY 5
upssched.conf
CMDSCRIPT /usr/bin/upssched-cmd
upsset.conf
I_HAVE_SECURED_MY_CGI_DIRECTORY
The problem is, while it seems to work fine (check with the url above),
it is
filling my syslog up with:
Mar 11 22:23:03 nirvana kernel: usb 2-1: usbfs: process 7534 (usbhid-ups) did
not claim interface 0 before use
Mar 11 22:23:03 nirvana usbhid-ups[7534]: Got disconnected by another driver:
Device or resource busy
Mar 11 22:23:06 nirvana kernel: usb 2-1: usbfs: process 7537 (usbhid-ups) did
not claim interface 0 before use
Mar 11 22:23:06 nirvana kernel: usb 2-1: usbfs: process 7537 (usbhid-ups) did
not claim interface 0 before use
Mar 11 22:23:06 nirvana usbhid-ups[7537]: Got disconnected by another driver:
Device or resource busy
I don't know if this is a problem with my config, or if it is a problem
with
dbus, etc... (dbus is a black box to me)
Let me know what you think and what I can do to fix this. Getting
messages
every 3 soconds from nut will fill the logs pretty quickly. Thanks.
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
_______________________________________________
Nut-upsdev mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
