Re: [Nut-upsuser] upsd crashes with a broken pipe error
On 12/29/2010 10:00 AM, Zach La Celle wrote: On 12/29/2010 08:34 AM, Charles Lepple wrote: On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote: I ran this in debug mode and captures the backtrace. r...@*:/etc/nut# upsd -D Network UPS Tools upsd 2.4.3 0.00 listening on 0.0.0.0 port 3493 0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups 2.550554 User ups...@127.0.0.1 logged into UPS [rack1ups] *** glibc detected *** upsd: free(): invalid next size (fast): 0x012c9870 *** Can you give us some background information about this system? What OS and version, who built the package, etc. Do you have valgrind available? Your version of glibc probably has some more thorough memory corruption detection algorithms than the default - man malloc on one of my systems suggests that setting the MALLOC_CHECK_ environment variable to either 1 or 2 will print some additional diagnostics. Output of uname -a: Linux www 2.6.32-27-server #49-Ubuntu SMP Thu Dec 2 02:05:21 UTC 2010 x86_64 GNU/Linux Information about glibc: GNU C Library (Ubuntu EGLIBC 2.11.1-0ubuntu7.6) stable release version 2.11.1, by Roland McGrath et al. Compiled by GNU CC version 4.4.3. Compiled on a Linux 2.6.24-28-server system on 2010-11-17. I didn't know about that MALLOC_CHECK_ variable: I've set it and am running the software again to see if I get a better error. I can install valgrind if necessary. Let me see what happens this time. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser After setting the variable, the only further information I have is this: upsd: free(): invalid pointer: 0x0 1d20f30 *** Segmentation fault I'll install valgrind and see if I can catch any memory leaks that way: otherwise, I'm not sure exactly what else to do. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
Citeren Zach La Celle lace...@roboticresearch.com: After setting the variable, the only further information I have is this: upsd: free(): invalid pointer: 0x01d20f30 *** Segmentation fault Try again with debug level set to -DDD. This might provide a little more context of where this occurs. Best regards, Arjen PS You're not attempting to run a 32-bit version of the server here, are you? -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Can't get iDowell to work
Hi all, first message to the list. :-)
I've got an iBox made by iDowell:
http://store.apple.com/uk/product/TR423ZM/A
This seems to be similar to the smaller Microdowell UPS:
http://idowell.eu/
I cannot get it recognised by the drivers. This is what I get when I plug in
the USB connector:
Jan 3 19:27:26 compaq kernel: usb 3-2: new low speed USB device using
uhci_hcd and address 47
Jan 3 19:27:26 compaq kernel: usb 3-2: New USB device found, idVendor=075d,
idProduct=0300
Jan 3 19:27:26 compaq kernel: usb 3-2: New USB device strings: Mfr=3,
Product=1, SerialNumber=2
Jan 3 19:27:26 compaq kernel: usb 3-2: Product: iBox
Jan 3 19:27:26 compaq kernel: usb 3-2: Manufacturer: iDowell
Jan 3 19:27:26 compaq kernel: usb 3-2: SerialNumber: 0001
Jan 3 19:27:26 compaq kernel: generic-usb 0003:075D:0300.00CA: hidraw1: USB
HID v1.10 Device [iDowell iBox] on usb-:00:1d.1-2/input0
Jan 3 19:27:42 compaq kernel: usb 3-2: USB disconnect, address 47
The device keeps disconnecting and reconnecting with a higher numerical
address each time.
I have set up this udev rule in /etc/udev/rules.d/70-nut-usbups.rules:
# iDowell iBox USB
ATTR{idVendor}==075d, ATTR{idProduct}==0300, SYMLINK+=iDowell,
MODE=664, GROUP=nut
When I try to start the upsd I get:
# /etc/init.d/upsd restart
* Starting upsd ...
Network UPS Tools upsd 2.4.3
listening on 127.0.0.1 port 3493
Can't connect to UPS [iDowell] (usbhid-ups-iDowell): No such file or directory
allowfrom in upsd.users is no longer used [ ok ]
The driver(s) is not successful.
With usbhid-ups I get:
=
# /lib/nut/usbhid-ups - -a iDowell
Network UPS Tools - Generic HID driver 0.34 (2.4.3)
USB communication driver 0.31
0.00 send_to_all: SETINFO driver.parameter.port /dev/iDowell
0.48 send_to_all: SETINFO driver.parameter.vendorid 075d
0.81 debug level is '16'
0.000721 upsdrv_initups...
[snip ...]
0.001307 Checking device (075D/0300) (003/061)
0.035384 - VendorID: 075d
0.035399 - ProductID: 0300
0.035408 - Manufacturer: iDowell
0.035414 - Product: iBox
0.035421 - Serial Number: 0001
0.035428 - Bus: 003
0.035435 Trying to match device
0.035443 Device does not match - skipping
[snip ...]
0.071806 Trying to match device
0.071814 Device does not match - skipping
0.071823 No appropriate HID device found
0.071836 No matching HID UPS found
=
with powerpanel I get:
=
# /lib/nut/powerpanel - -a iDowell
Network UPS Tools - CyberPower text/binary protocol UPS driver 0.25 (2.4.3)
Warning: This is an experimental driver.
Some features may not function correctly.
0.00 send_to_all: SETINFO driver.parameter.port /dev/iDowell
0.64 debug level is '16'
0.011711 Trying binary protocol...
0.011745 tcgetattr(/dev/iDowell): Inappropriate ioctl for device
=
with microdowell I get:
=
# /lib/nut/microdowell - -a iDowell
Network UPS Tools - MICRODOWELL UPS driver 0.01 (2.4.3)
0.00 send_to_all: SETINFO driver.parameter.port /dev/iDowell
0.63 debug level is '16'
0.000728 tcgetattr(/dev/iDowell): Inappropriate ioctl for device
=
This is what my /etc/nut/ups.conf contains:
[iDowell]
driver = microdowell
# port = auto
port = /dev/iDowell
# manufacturer = iDowell
# vendorid = 075d
desc = iBox by iDowell
I am not sure if the problem is with the drivers I have been using or
something else, like my udev rule, access rights, etc.
# ls -la /dev/iDowell
lrwxrwxrwx 1 root root 15 Jan 3 19:38 /dev/iDowell - bus/usb/003/091
(BTW, I don't seem to have a dev/hiddev0 or similar that I thought the iBox
would be recognised as).
# ls -la /etc/nut/
total 38
drwxr-xr-x 2 root root 224 Jan 3 19:36 .
drwxr-xr-x 90 root root 6008 Jan 3 18:30 ..
-rw-r--r-- 1 root root 1413 Jan 1 14:02 nut.conf
-rw-r--r-- 1 root root 3798 Jan 3 19:35 ups.conf
-rw-r- 1 root nut 1778 Jan 1 14:37 upsd.conf
-rw-r- 1 root nut 2104 Jan 3 15:47 upsd.users
-rw-r- 1 root nut 11988 Jan 3 15:48 upsmon.conf
-rw-r--r-- 1 root root 3883 Jan 1 14:02 upssched.conf
Is there some other driver, or anything else I could use to get it going?
--
Regards,
Mick
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
On Monday 03 January 2011 20:40:17 Arjen de Korte wrote: Citeren Kjell Claesson kjell.claes...@epost.tidanet.se: So start to send the output of: lsusb -v Cut out the part about the ups, and we have a look on it. Make that lsusb -v -d 075d:0300 to save yourself the trouble of weeding out the interesting stuff from the other USB devices (we already know the VID:PID combination from the udev rule you created). Make sure to run this as root, so that we have a chance of capturing the report descriptor of this device. Best regards, Arjen Here you go guys: # lsusb -v -d 075d:0300 Bus 003 Device 011: ID 075d:0300 Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x075d idProduct 0x0300 bcdDevice0.01 iManufacturer 3 iDowell iProduct1 iBox iSerial 2 0001 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 41 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x60 (Missing must-be-set bit!) Self Powered Remote Wakeup MaxPower 10mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.10 bCountryCode 33 US bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 412 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 20 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0002 1x 2 bytes bInterval 20 Device Status: 0x0001 Self Powered The device gets picked up by the MSWindows default UPS management facility and from what I was told by the guy who sold it to me it is also read by the default AppleMac power manager (no idea what drivers AppleMacs use for USB connected UPS). -- Regards, Mick ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NetworkUPS tools Compatibility update
Hi James, 2011/1/1 Among The Living stinkysmelly...@gmail.com Hey there, After a few hours with tampering I got my UPS up and running. It's a RocketFish 1025/1000va (The model varies and is listed as 1000va as well as 1025va). I got it working with the usbhid-ups driver, which I guess is a no brainer :P. Just figured I'd let you know. This product (As I found out by using good ole google cache on gentoos forums), is just a rebrand of CyberPower's UPS's. thanks for your report. can you please post an upsc output, so that we can validate that everything is fine, and confirm your compatibility submission? cheers, Arnaud -- Linux / Unix Expert RD - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
OK On Monday 03 January 2011 20:40:17 Arjen de Korte wrote: Citeren Kjell Claesson kjell.claes...@epost.tidanet.se: So start to send the output of: lsusb -v Cut out the part about the ups, and we have a look on it. Make that lsusb -v -d 075d:0300 to save yourself the trouble of weeding out the interesting stuff from the other USB devices (we already know the VID:PID combination from the udev rule you created). Make sure to run this as root, so that we have a chance of capturing the report descriptor of this device. Best regards, Arjen Thanks Arjen :-) Here you go guys: # lsusb -v -d 075d:0300 The device class is not HID, but you can try this. Do a ups.conf like this. [iDowell] driver = usbhid-ups port = auto vendorid = 075d productid = 0300 desc = iBox by iDowell Now run it like this: /lib/nut/usbhisd-ups -DD -a iDowell -u root Kjell ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Can't get iDowell to work
On Monday 03 January 2011 22:07:20 you wrote: OK On Monday 03 January 2011 20:40:17 Arjen de Korte wrote: Citeren Kjell Claesson kjell.claes...@epost.tidanet.se: So start to send the output of: lsusb -v Cut out the part about the ups, and we have a look on it. Make that lsusb -v -d 075d:0300 to save yourself the trouble of weeding out the interesting stuff from the other USB devices (we already know the VID:PID combination from the udev rule you created). Make sure to run this as root, so that we have a chance of capturing the report descriptor of this device. Best regards, Arjen Thanks Arjen :-) Here you go guys: # lsusb -v -d 075d:0300 The device class is not HID, but you can try this. Do a ups.conf like this. [iDowell] driver = usbhid-ups port = auto vendorid = 075d productid = 0300 desc = iBox by iDowell Now run it like this: /lib/nut/usbhisd-ups -DD -a iDowell -u root # /lib/nut/usbhid-ups -DD -a iDowell -u root Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 0.00 debug level is '2' 0.000637 upsdrv_initups... 0.001109 Checking device (046D/C069) (002/002) [snip ...] 0.038754 Checking device (075D/0300) (003/026) 0.073483 - VendorID: 075d 0.073496 - ProductID: 0300 0.073505 - Manufacturer: iDowell 0.073511 - Product: iBox 0.073518 - Serial Number: 0001 0.073526 - Bus: 003 0.073534 Trying to match device 0.073543 Device does not match - skipping [snip ...] 0.073737 No appropriate HID device found 0.073749 No matching HID UPS found Same result whether I run it with port auto or port /dev/iDowell. -- Regards, Mick ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] online zinto usv
[cc'ing the list again - please use reply all or reply to list.] On Mon, Jan 3, 2011 at 11:45 AM, Carsten Burkhardt c.burkha...@b-c-s.de wrote: Hello, many thanks for your assitance. The help got unfortunately time outs (explore.txt) Looking at the VendorID and ProductID, it is likelt that this device is recognized as a /dev/tttyUSB(0|1...) device. As such you should probably point the blazer_ser or megatec drivers to this port. I do not have /dev/ttyUSB. Arjen mentioned it was likely, but you never can tell. If I point to /dev/bus/usb/001/006 the blazer or megatec Driver failed to start. The /dev/bus/usb/* nodes are not interchangeable with /dev/ttyUSB* nodes. The serial drivers such as blazer_ser and megatec need tty interfaces. Also note that after you run usbhid-ups, the /dev/ttyUSB* device nodes may not be there anymore. The easiest thing to do is simply unplug and re-plug the USB cable (you only need to do this once). Also on a plug cycle a ttyUSB do not create. Did you try setting the subdriver, vendorid and productid settings per the blazer_usb message as well? (Sorry if I missed that - I didn't see your configuration in the list of attachments.) Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.4.3) Network UPS Tools - UPS driver controller 2.4.3 No supported devices found. Please check your device availability with 'lsusb' and make sure you have an up-to-date version of NUT. If this does not help, try running the driver with at least 'subdriver', 'vendorid' and 'productid' options specified. Please refer to the man page for details about these options (man 8 blazer). Driver failed to start (exit status=1) -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] upsd crashes with a broken pipe error
On Mon, Jan 3, 2011 at 8:29 AM, Zach La Celle lace...@roboticresearch.com wrote: On 12/29/2010 10:00 AM, Zach La Celle wrote: On 12/29/2010 08:34 AM, Charles Lepple wrote: On Dec 27, 2010, at 9:36 AM, Zach La Celle wrote: I ran this in debug mode and captures the backtrace. r...@*:/etc/nut# upsd -D Network UPS Tools upsd 2.4.3 0.00 listening on 0.0.0.0 port 3493 0.000354 Connected to UPS [rack1ups]: apcsmart-rack1ups 2.550554 User ups...@127.0.0.1 logged into UPS [rack1ups] *** glibc detected *** upsd: free(): invalid next size (fast): 0x012c9870 *** Can you give us some background information about this system? What OS and version, who built the package, etc. Just to be sure, are you running the Ubuntu-provided package, or something from another package repository? Which version of Ubuntu? Running valgrind might produce similarly opaque results without debug symbols (which you can enable if you build from source). That is a bit more involved, though (especially if you want to keep the installed files in the same place) so I'd try that after Arjen's suggestion with -DDD. -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
