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

Mick michaelkintzios at gmail.com
Tue Jan 11 15:32:21 UTC 2011

On 11 January 2011 07:50, Arjen de Korte <nut+users at de-korte.org> wrote:
> Citeren Mick <michaelkintzios at gmail.com>:
>> While nut is running, my logs fill up with:

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

Oops!  Yes, that had been left uncommented for some reason.  Thanks.

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

I am sure I did stop both upsd and upsdrv and then restarted them
after I added pollonly... but will check again.

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


More information about the Nut-upsuser mailing list