[Nut-upsuser] Can't get iDowell to work

[Arjen de Korte]

Citeren Mick <michaelkintzios op gmail.com>:

> While nut is running, my logs fill up with:
>
> Jan 10 22:50:06 compaq usbhid-ups[5083]: libusb_get_report: No error
> Jan 10 22:50:08 compaq usbhid-ups[5083]: libusb_get_report: No error
> Jan 10 22:50:10 compaq usbhid-ups[5083]: libusb_get_report: No error
> Jan 10 22:50:12 compaq usbhid-ups[5083]: libusb_get_report: No error
>
> regularly at 2 second intervals.  Is there a way to tell it to not log
> such messages (or log them only once?)

Yes. Make your system not log messages at LOG_DEBUG. Usually you can  
configure this in '/etc/syslog.conf'. On a production system, you  
should not log messages with LOG_DEBUG since this is reserved for  
debugging messages and can be very verbose (risking flooding the logs).

> If I add "pollonly" in ups.conf I get these messages:
>
> Jan 10 23:15:57 compaq upsd[5995]: listening on 127.0.0.1 port 3493
> Jan 10 23:15:57 compaq upsd[5995]: Connected to UPS [iDowell]:
> usbhid-ups-iDowell
> Jan 10 23:15:57 compaq upsd[5995]: allowfrom in upsd.users is no longer used
> Jan 10 23:15:57 compaq upsd[5996]: Startup successful
> Jan 10 23:15:57 compaq usbhid-ups[5945]: libusb_get_report: could not
> claim interface 0: Device or resource busy
> Jan 10 23:15:57 compaq usbhid-ups[5945]: Got disconnected by another
> driver: Device or resource busy
> Jan 10 23:15:59 compaq usbhid-ups[5945]: libusb_get_report: could not
> claim interface 0: Device or resource busy
> Jan 10 23:15:59 compaq usbhid-ups[5945]: Got disconnected by another
> driver: Device or resource busy
> ... and so on.
>
> Not sure if this is how it should be - but within a few minutes I get:
>
> # upsc iDowell
> Error: Data stale

You *must* stop the usbhid-ups driver for a UPS before starting a new  
one. The message "Got disconnected by another driver: Device or  
resource busy" is a tell tale sign that you didn't. Before running  
'upsdrvctl start', always run 'upsdrvctl stop' first. A crude method  
would be to reboot the system, if you can't find the running  
usbhid-ups processes. I usually use 'top -u upsd' ('upsd' is the name  
of the NUT user on my system) to find any drivers running.

> PS. What is the meaning of:  battery.capacity: 0.03 ?

This is a mapping problem. The UPS is reporting 100% battery capacity  
is available and I mistakenly mapped this to the battery capacity (Ah)  
value. I will remove this later on.

Best regards, Arjen
-- 
Please keep list traffic on the list (off-list replies will be rejected)