Re: [Nut-upsuser] [Nut-upsdev] UPS on Freenas
[please keep the list CC'd. nut-upsuser is the best place for this thread.] On Jun 25, 2011, at 11:01 AM, John Lechanski wrote: 1. the specifications of my ups: F6C750-AVR; it has 750VA, more than enough to power my system, which is all that is on the ups. What are the USB Vendor ID and Product ID? You may need to open a shell for that. I haven't used Solaris USB support, so I'm not sure what commands to use. 2. the first picture you'll see is when I unplug and plug in my ups via USB into the same USB port of the NAS. 3. the second picture is going to the UPS feature on Freenas 0.7.2.5543. I have the OS running from a thumb drive and I have two sets of drives you'll see in the pic, one a raid 5 configuration (hard wired raid with addonics raid card) and the other is just a free floating HDD, no back-up. 4. the next pictures you'll see is what happens when I try different configurations on the gui. The first pair (pic 3 4) are the config and what it says on my nas. When I enter this configuration, the nas beeps once and the screen says the first thing you see Broadcast Message... then after about 5 seconds, another beep and the second line UPS ups@localhost is unavailable Any log entries in syslog? 5. picture 5 is what happens when I change my configuration, still same error, and same reaction by nas box. 6. the final picture is what happens when I implement a solution that I found on-line. the gui software says success and my nas box has no change (in other words, nothing happens on my screen when I implement this configuration, no beeping, no nothing). I then try to simulate a power outage by yanking the plug on the ups; the ups is on battery and the nas keeps going as if nothing is wrong. The genericups driver cannot do error checking: http://www.networkupstools.org/docs/man/genericups.html With a USB cable, you would only use genericups if you were sure that the UPS is a basic contact-closure model with a USB-to-serial adapter supported by the OS. I hope this clarifies things, no matter what configuration I use, I either get the error messages on the gui and the nas beeps twice with the above mentioned quotations or I get the one success in #6 but it won't work. My overall impression is that the freenas UPS support needs more diagnostic information. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Belkin F6C1200-UNV on Ubuntu 11.04
On Sat, Jun 25, 2011 at 5:48 PM, Charles Lepple clep...@gmail.com wrote:
On Jun 24, 2011, at 8:50 PM, Martin Ewing wrote:
I had been using NUT's Ubuntu package (64 bit) with no problems until
upgrading to Ubuntu 11.04.
What was the previous NUT package version?
Now, I get the following message when I try usbhid-ups:
$ sudo /lib/nut/usbhid-ups -a mybelkin
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
Can't claim USB device [050d:1100]: could not detach kernel driver from
interface 0: Operation not permitted
Do you get the same error if you add -u root to the command line? If so,
there might be something other than filesystem permissions causing this
error.
ups.conf:
[mybelkin]
driver = usbhid-ups
port = auto
desc = Belkin 1200 VA UPS
The udev rule seems OK:
# F6C1100-UNV, F6C1200-UNV - usbhid-ups
ATTR{idVendor}==050d, ATTR{idProduct}==1100, MODE=664, GROUP=nut
Using udevadm monitor and plugging in the USB:
KERNEL[1308961682.706704] add
/devices/pci:00/:00:**1d.0/usb6/6-1
(usb)
KERNEL[1308961682.709615] add
/devices/pci:00/:00:**1d.0/usb6/6-1/6-1:1.0
(usb)
KERNEL[1308961682.709674] add /devices/pci:00/:00:**
1d.0/usb6/6-1/6-1:1.0/0003:**050D:1100.0007 (hid)
KERNEL[1308961682.979776] add /devices/pci:00/:00:**
1d.0/usb6/6-1/6-1:1.0/usb/**hiddev0 (usb)
KERNEL[1308961682.979802] add /devices/pci:00/:00:**
1d.0/usb6/6-1/6-1:1.0/0003:**050D:1100.0007/hidraw/hidraw0 (hidraw)
However, the usb devices are created in root group and without read access
to nut group.
$ ls -l /dev/usb
crw--- 1 root root 180, 96 2011-06-24 20:43 hiddev0
This device would disappear if the detach error hadn't occurred.
Around the time of the first udev event listed above, udev should have
created /dev/bus/usb/006/001, and that node should be owned by group nut.
I just upgraded to 11.04, and the tripplite_usb driver did not have a
problem attaching to it. (This driver uses the same method of detaching the
kernel HID driver as usbhid-ups.)
If I have time later this weekend, I'll swap out that UPS for one which
uses the usbhid-ups driver and see if I can reproduce the problem.
Charles,
Tried -u root -- different response, but still not right:
$ sudo /lib/nut/usbhid-ups -a mybelkin -u root
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
Using subdriver: Belkin HID 0.12
libusb_get_report: could not claim interface 0: Device or resource busy
libusb_get_report: could not claim interface 0: Device or resource busy
Got disconnected by another driver: Device or resource busy
Can't initialize data from HID UPS
Device:
$ ls -l /dev/bus/usb/006/001
crw-rw-r-- 1 root root 189, 640 2011-06-24 18:29 /dev/bus/usb/006/001
Not in group nut.
But I tried one more thing. I powered down the UPS completely and restarted
everything. (I wondered if the Belkin's USB was hung up.) Now, I get
something different:
$ sudo /lib/nut/usbhid-ups -a mybelkin
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
Using subdriver: Belkin HID 0.12
libusb_get_report: error sending control message: Operation not permitted
libusb_get_report: error sending control message: Operation not permitted
Can't initialize data from HID UPS
and
$ ls -l /dev/usb
total 0
crw--- 1 root root 180, 96 2011-06-25 18:58 hiddev0
crw-rw 1 root lp 180, 0 2011-06-25 18:58 lp0
martin@gimli:~$ ls -l /dev/bus/usb/006/001
crw-rw-r-- 1 root root 189, 640 2011-06-25 18:58 /dev/bus/usb/006/001
If I try -u root
$ sudo /lib/nut/usbhid-ups -a mybelkin -u root
Network UPS Tools - Generic HID driver 0.35 (2.6.0)
USB communication driver 0.31
Using subdriver: Belkin HID 0.12
libusb_get_report: No error
libusb_get_report: No error
libusb_get_report: No error
libusb_get_report: No error
libusb_get_report: No error
libusb_get_report: No error
libusb_get_report: No error
...
and now there is a process
3544 ?Ss 0:00 /lib/nut/usbhid-ups -a mybelkin -u root
I think I am understanding less and less!
Martin
--
Martin Ewing
Branford, Connecticut
martin.s.ew...@gmail.com
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
[Nut-upsuser] Sven Power Pro 1000+
Hello. I recently upgraded from Ubuntu Maverick to Natty and hence upgraded nut from 2.4.3-1ubuntu5 to 2.6.0-1ubuntu3. My Sven PowerPro+ 1000 UPS ( http://en.sven.ru/catalog/ups/power_pro_plus_1000.htm ) worked fine with the previous version, using megatec_usb driver, but doesn't work with the current version, since megatec_usb is no longer available. Here is the output from blazer_usb. sudo /lib/nut/blazer_usb -a sven1 -DDD Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3) 0.00 debug level is '3' 0.251050 Checking device (/) (009/002) 0.295442 - VendorID: 0.295451 - ProductID: 0.295456 - Manufacturer: 0.295460 - Product: 010937 0.295464 - Serial Number: 0.295468 - Bus: 009 0.295472 Trying to match device 0.295477 Device matches 0.295493 failed to claim USB device: could not claim interface 0: Device or resource busy 0.295505 detached kernel driver from USB device... 0.301458 Trying megatec protocol... 0.301466 send: Q1 0.549441 blazer_status: short reply 0.549453 Status read 1 failed 0.549458 send: Q1 1.042431 blazer_status: short reply 1.042444 Status read 2 failed 1.042449 send: Q1 1.291425 blazer_status: short reply 1.291435 Status read 3 failed 1.291440 Trying mustek protocol... 1.291445 send: QS 1.291449 read: QS 1.291453 blazer_status: short reply 1.291457 Status read 1 failed 1.291460 send: QS 1.291464 read: QS 1.291467 blazer_status: short reply 1.291470 Status read 2 failed 1.291473 send: QS 1.291476 read: QS 1.291479 blazer_status: short reply 1.291482 Status read 3 failed 1.291486 Trying megatec/old protocol... 1.291489 send: D 1.291492 read: D 1.291495 blazer_status: short reply 1.291498 Status read 1 failed 1.291502 send: D 1.291505 read: D 1.291508 blazer_status: short reply 1.291511 Status read 2 failed 1.291514 send: D 1.291517 read: D 1.291520 blazer_status: short reply 1.291524 Status read 3 failed 1.291527 No supported UPS detected I downgraded back to 2.4.3, configured nut to use megatec_usb again, and it started working again. However, it seems strange that I cannot use the latest version. -- Vlad ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Sven Power Pro 1000+
On Sat, Jun 25, 2011 at 8:13 PM, Vlad n...@wolf.umail.net wrote: Hello. I recently upgraded from Ubuntu Maverick to Natty and hence upgraded nut from 2.4.3-1ubuntu5 to 2.6.0-1ubuntu3. My Sven PowerPro+ 1000 UPS ( http://en.sven.ru/catalog/ups/power_pro_plus_1000.htm) worked fine with the previous version, using megatec_usb driver, but doesn't work with the current version, since megatec_usb is no longer available. Here is the output from blazer_usb. sudo /lib/nut/blazer_usb -a sven1 -DDD Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3) 0.00debug level is '3' 0.251050Checking device (/) (009/002) 0.295442- VendorID: 0.295451- ProductID: 0.295456- Manufacturer: 0.295460- Product: 010937 0.295464- Serial Number: 0.295468- Bus: 009 0.295472Trying to match device 0.295477Device matches 0.295493failed to claim USB device: could not claim interface 0: Device or resource busy 0.295505detached kernel driver from USB device... 0.301458Trying megatec protocol... 0.301466send: Q1 0.549441blazer_status: short reply 0.549453Status read 1 failed 0.549458send: Q1 1.042431blazer_status: short reply 1.042444Status read 2 failed 1.042449send: Q1 1.291425blazer_status: short reply 1.291435Status read 3 failed 1.291440Trying mustek protocol... 1.291445send: QS 1.291449read: QS 1.291453blazer_status: short reply 1.291457Status read 1 failed 1.291460send: QS 1.291464read: QS 1.291467blazer_status: short reply 1.291470Status read 2 failed 1.291473send: QS 1.291476read: QS 1.291479blazer_status: short reply 1.291482Status read 3 failed 1.291486Trying megatec/old protocol... 1.291489send: D 1.291492read: D 1.291495blazer_status: short reply 1.291498Status read 1 failed 1.291502send: D 1.291505read: D 1.291508blazer_status: short reply 1.291511Status read 2 failed 1.291514send: D 1.291517read: D 1.291520blazer_status: short reply 1.291524Status read 3 failed 1.291527No supported UPS detected I downgraded back to 2.4.3, configured nut to use megatec_usb again, and it started working again. However, it seems strange that I cannot use the latest version. -- Vlad ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser Vlad, This seems very similar to the trouble I have with a Belkin UPS (USB) with Natty (64 bit). Martin -- Martin Ewing Branford, Connecticut martin.s.ew...@gmail.com ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
