OK... Thank you Arjen.

I've killed the extra processes... But have some new problems. And I still
cannot connect to the device.

If I run upsdrvctl start (with or without '-u root'):

------
[EMAIL PROTECTED]:/etc/nut$ sudo upsdrvctl start
Network UPS Tools - UPS driver controller 2.2.1-
Network UPS Tools: 0.29 USB communication driver - core 0.32 (2.2.1-)

Using subdriver: TrippLite HID 0.2 (experimental)
Startup timer elapsed, continuing...
[EMAIL PROTECTED]:/etc/nut$
------

I don't think the driver is actually connecting to the device.

If I try to manually start upsd:

------
[EMAIL PROTECTED]:/etc/nut$ sudo upsd
Network UPS Tools upsd 2.2.1-
listening on 0.0.0.0 port 3493
Can't connect to UPS [OMNI1000] (usbhid-ups-OMNI1000): No such file or
directory
[EMAIL PROTECTED]:/etc/nut$
------

I'm not sure what is going on.

I am on Ubuntu Server 8.04 and when I try to "/etc/init.d/nut start" (after
having killed the above processes), NOTHING starts. Even though it says [ OK
] when I run init.d.

-Ken L.



-----Original Message-----
From: Arjen de Korte [mailto:[EMAIL PROTECTED] 
Sent: Monday, September 08, 2008 4:05 PM
To: [EMAIL PROTECTED]
Cc: [email protected]
Subject: Re: [Nut-upsuser] OMNIPLUS1000LCD is "unavailable"

Citeren Kenneth R Litko <[EMAIL PROTECTED]>:

> Sep  8 13:58:48 bigdog kernel: [ 4460.019306] usb 7-3: new low speed 
> USB device using ohci_hcd and address 5 Sep  8 13:58:48 bigdog kernel: 
> [ 4460.524141] usb 7-3: configuration #1 chosen from 1 choice Sep  8 
> 13:58:50 bigdog kernel: [ 4461.867256] hiddev96hidraw0: USB HID v1.10 
> Device [Tripp Lite  TRIPP LITE UPS ] on usb-0000:02:01.0-3 Sep  8 
> 14:15:05 bigdog kernel: [ 5436.779146] usb 7-3: usbfs: process 6636
> (usbhid-ups) did not claim interface 0 before use Sep  8 14:15:05 
> bigdog kernel: [ 5436.779577] usb 7-3: usbfs: process 6886
> (usbhid-ups) did not claim interface 0 before use

There are two 'usbhid-ups' process that are attempting to claim the same
device (on usb 7-3). That doesn't fly. Make sure that you stop
*all* drivers before starting a new one and that there are no duplicate
entries in 'ups. conf'. The same might happen if you have multiple UPSes of
identical make and model that can't be distinguished through the regex
matching.

[...]

> Path: UPS.PowerSummary.PresentStatus.ShutdownImminent, Type: Input,
> ReportID: 0x32, Offset: 0, Size: 1, Value: 0.000000
> Report[buf]: (2 bytes) => 32 06
> Path: UPS.PowerSummary.PresentStatus.TLACPresent, Type: Input, ReportID:
> 0x32, Offset: 1, Size: 1, Value: 1.000000
> ------
>
> The above "Report" goes on ad nauseam until I manually kill the process.

Sure, that's what you're warned about when running drivers in debug mode.

Best regards, Arjen
--
Eindhoven - The Netherlands
Key fingerprint - 66 4E 03 2C 9D B5 CB 9B  7A FE 7E C1 EE 88 BC 57

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Reply via email to