Nut upsdev - Mar 2010 - 2.4.1 Voltages are Great for CP1000AVRLCD, but usbfs messages in logs (a lot)

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 archangel_ups at archangel.3111skyline.com "Archangel CP1000AVRLCD
UPS"
MONITOR nirvana_ups at 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 archangel_ups at archangel.3111skyline.com 1 david notReald slave
MONITOR nirvana_ups at 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

On 03/11/2010 10:38 PM, David C. Rankin wrote:
> 	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/
> 
Guys:

	This is strange. I have shutdown and restarted a couple of times since the
first email and what is happening is that whatever box has nut started last gets
the usbfs errors written to its logs?? In my first post notice it is box nirvana
that has the usbfs errors. The last shutdown/restart cycle for nut, I started
nirvana fist this time, then archangel. The syslog for nirvana is fine now:

Mar 11 23:00:10 nirvana usbhid-ups[7853]: Startup successful
Mar 11 23:00:10 nirvana upsd[7854]: listening on 192.168.6.17 port 3493
Mar 11 23:00:10 nirvana upsd[7854]: listening on 127.0.0.1 port 3493
Mar 11 23:00:10 nirvana upsd[7854]: Connected to UPS [nirvana_ups]:
usbhid-ups-nirvana_ups
Mar 11 23:00:10 nirvana upsd[7855]: Startup successful
Mar 11 23:00:10 nirvana upsmon[7857]: Startup successful

	but the syslog for archangel now has the 3 second usbfs problem.

Mar 11 23:04:16 archangel kernel: usb 2-1: usbfs: process 20899 (usbhid-ups) did
not claim interface 0 before use
Mar 11 23:04:18 archangel kernel: usb 2-1: usbfs: process 20875 (usbhid-ups) did
not claim interface 0 before use
Mar 11 23:04:18 archangel kernel: usb 2-1: usbfs: process 20875 (usbhid-ups) did
not claim interface 0 before use

	Does this make any sense?? Is machine 1 trying to take control over machine
2's
usb port with the ups on it before nut starts on box 2??

	In a related matter, on the box that is started second (box 2), your get the
follow errors issued once on startup:

Mar 11 23:00:10 nirvana upsmon[7859]: Login on UPS
[archangel_ups at archangel.3111skyline.com] failed - got [ERR ACCESS-DENIED]
Mar 11 23:00:10 nirvana upsmon[7859]: Login on UPS [nirvana_ups at localhost]
failed - got [ERR ACCESS-DENIED]

What is it that nut is trying to log into and where can I change the
permissions? This is on Arch Linux if it makes a difference and I compiled nut
with:

./configure --with-user=nut \
--prefix=/usr \
--datadir=/usr/share/ups \
--sysconfdir=/etc/ups \
--with-group=nut \
--with-hal \
--with-usb \
--with-cgi \
--with-cgipath=/srv/http/cgi-bin/nut \
--with-htmlpath=/srv/http/nut \
--with-udev-dir=/etc/udev || return 1

Let me know what else I can provide and I'll be happy to do it.

-- 
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

Citeren "David C. Rankin" <drankinatty op suddenlinkmail.com>:
> [upsmaster]
>         password = notRealm
>         upsmon master
> [upsslave]
>         password = notReals
>         upsmon slave
> [david]
>         password = notReald
>         actions = SET
>         instcmds = ALL
The above configuration for [david] is invalid. You *must* specify  
whether the user has upsmon master or slave privileges. Neither is  
listed, which will not be a problem for logging in on pre-2.4.2  
versions, but will be in later versions.

Best regards, Arjen
-- 
Please keep list traffic on the list