[Nut-upsuser] APC 1500 USB problem

[Peter Selinger]

A couple of suggestions.

First, please read the man page of newhidups, particularly the section
on how to configure multiple USB ups's. ("IMPLEMENTATION"). Newhidups
does not use /dev/usb/hiddev*, and the "port" values you have given
will be ignored in any case.

Second, please follow the instructions in the file INSTALL that comes
with NUT. In other words, use upsd, upsmon, upsdrvctl, and don't use
your distribution's /usr/local/etc/rc.d/nut, at least until you have
found out what the problem is. The problem might be with that script,
which is not part of NUT (and therefore we don't know what it does and
cannot support it here).

Third, the information you gave is insufficient to determine what the
problem is. There are several reasons the newhidups driver might not
be able to connect to your UPS, e.g. (a) another instance of newhidups
is already attached to the UPS, (b) a permissions problem, (c) other ???
So you should check that newhidups is not already running. You should
also check that the device really exists (lsusb or usbview or similar). 
You should also check that the permissions on the file
/proc/bus/usb/XXX/YYY are set correctly. See the file INSTALL, and
also http://www.mathstat.dal.ca/~selinger/ups/backups.html, for
step-by-step instructions. 

Good luck! -- Peter

Czuczy Gergely wrote:
> 
> Hello,
> 
> We have two APC Back-UPS RS 1500 USB stuff, and i've got a bit
> of a problem with it and NUT.
> 
> The usbdevs output:
> addr 2: Back-UPS RS 1500 FW:8.g8 .I USB FW:g8, American Power Conversion
> addr 3: Back-UPS RS 1500 FW:8.g8 .I USB FW:g8, American Power Conversion
> (UPS1 and UPS2)
> 
> I've configured our NUT system to monitor the UPSes, and it went very
> fine till the time had arrived for a test. UPS unpower (-> ONBAT), and
> test what NUT does to the boxes connected to it.
> 
> After I've unplugged the power cable of UPS1, nut started not to notice
> that on its cgi interface. It was showing a duplicate of the on-power 
> UPS.
> 
> After this I've restarted the NUT ups daemon and thus the drivers along
> with it. After this restart the drivers haven't been able to find any
> suitable UPS for them. I've checked this in both the Linux2.6.19.2 box
> it was running in, and in a FreeBSD 6.2-RELEASE-p2. On neither machine
> could the driver handle the UPS.
> 
> I'm using the newhidups driver to handle these UPSes, since i haven't
> been able to find the hidups driver, to check with that.
> 
> My question is, what is going on? :) I don't think that this is the
> desired functionality of NUT, and we'd like to monitor 3 UPSes (1 is not
> yet connected) with NUT, and handle our 7 servers with it in the office.
> 
> Technical details:
> 
> NUT version:
> BSD box: Network UPS Tools upsd 2.0.5
> Linux box: Network UPS Tools upsd 2.0.5
> 
> Driver config:
> [ups1]
>         driver = newhidups
>         port = /dev/usb/hiddev0
> 
> [ups2]
>         driver = newhidups
>         port = /dev/usb/hiddev1
> 
> (this is the linux one. on FreeBSD, it's /dev/ugen{0,1})
> 
> startup output on the BSD box:
> # /usr/local/etc/rc.d/nut start
> Network UPS Tools - UPS driver controller 2.0.5
> Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30
> (2.0.5)
> 
> No matching HID UPS found
> Driver failed to start (exit status=1)
> Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30
> (2.0.5)
> 
> No matching HID UPS found
> Driver failed to start (exit status=1)
> 
> If I've skipped some relevant part, please tell me, and I will
> try to send it.
> 
> Looking forward for your help in order to make this work.
> 
> -- 
> Your Sincerely
> 
> Gergely Czuczy
> Publishing Factory Ltd
> http://www.publishing.hu/
> 
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
>