Re: [Nut-upsuser] nutdrv_atcl_usb
The output of the ldd command is: root@minime:~# ldd /lib/nut/nutdrv_atcl_usb linux-gate.so.1 (0xb7722000) libusb-0.1.so.4 = /lib/i386-linux-gnu/libusb-0.1.so.4 (0xb76fe000) libpthread.so.0 = /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 (0xb76e2000) libc.so.6 = /lib/i386-linux-gnu/i686/cmov/libc.so.6 (0xb7536000) /lib/ld-linux.so.2 (0xb7725000) The UPS was connected to device 001/002 again as I ran the strace. The output is attached. On 6 November 2014 00:22, Charles Lepple clep...@gmail.com wrote: On Nov 5, 2014, at 1:36 AM, jani jani.tali...@gmail.com wrote: Ok, I installed a fresh Debian testing (jessie) onto a laptop to try making sure it wasn't my current Ubuntu server causing the issue. Kernel is 3.16-3-686-pae #1 SMP Debian 3.16.5-1 (2014-10-10). The only thing installed besides the stock debian desktop is nut. The UPS still refuses to talk to the driver, the error messages appear to be identical, but I attached them just in case I'm missing something important. I tried changing the permissions and running as root just in case, and they made no difference. Hmm, maybe those aren't the /dev node names that it is using. Can please you send the output of: strace -o nutdrv_atcl_usb.strace /lib/nut/nutdrv_atcl_usb -a name -DD Also, if you run 'ldd /lib/nut/nutdrv_atcl_usb', is it linking against 'libusb-0.1.so.4' or libusb-compat? -- Charles Lepple clepple@gmail nutdrv_atcl_usb.strace.gz Description: GNU Zip compressed data ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nutdrv_atcl_usb
I'm running Ubuntu 14.04.1 LTS with kernel 3.13.0-39-generic x86_64. The security mechanisms I haven't played with at all, and up until last week nut was running just fine on an Eaton E series NV UPS with a USB connection (from memory it used the blazer_usb driver). I installed the nut packages from debian sid (ubuntu is still stuck on nut version 2.7.1) to get the 2.7.2 version with the nutdrv_atcl_usb driver. I tried adding the -u root to the driver command line, that didn't change anything. I might try to find a spare machine to run Debian on to see if it works that way. On Tue Nov 04 2014 at 3:38:21 PM Charles Lepple clep...@gmail.com wrote: On Nov 3, 2014, at 9:01 PM, jani jani.tali...@gmail.com wrote: Hello again, I ran the commands again, checking to make sure the UPS was still device 005/002, and the results is: root@microserver:~# ls -l /dev/bus/usb/005/002 crw-rw-r-- 1 root nut 189, 513 Nov 4 12:55 /dev/bus/usb/005/002 I tried setting permissions of /dev/bus/usb/005/002 to 777 and ran the test again to see what that would do, but there was no difference in the status interrupt read error messages. Well, that's odd. Can you provide a little more detail about your system? (distribution, kernel version, any security mechanisms like SELinux or AppArmor, etc.) Also, what happens if you add -u root to the driver command line? (The 'chmod 777' should have been sufficient...) -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nutdrv_atcl_usb
Ok, I installed a fresh Debian testing (jessie) onto a laptop to try making sure it wasn't my current Ubuntu server causing the issue. Kernel is 3.16-3-686-pae #1 SMP Debian 3.16.5-1 (2014-10-10). The only thing installed besides the stock debian desktop is nut. The UPS still refuses to talk to the driver, the error messages appear to be identical, but I attached them just in case I'm missing something important. I tried changing the permissions and running as root just in case, and they made no difference. On 5 November 2014 11:55, jani jani.tali...@gmail.com wrote: I'm running Ubuntu 14.04.1 LTS with kernel 3.13.0-39-generic x86_64. The security mechanisms I haven't played with at all, and up until last week nut was running just fine on an Eaton E series NV UPS with a USB connection (from memory it used the blazer_usb driver). I installed the nut packages from debian sid (ubuntu is still stuck on nut version 2.7.1) to get the 2.7.2 version with the nutdrv_atcl_usb driver. I tried adding the -u root to the driver command line, that didn't change anything. I might try to find a spare machine to run Debian on to see if it works that way. On Tue Nov 04 2014 at 3:38:21 PM Charles Lepple clep...@gmail.com wrote: On Nov 3, 2014, at 9:01 PM, jani jani.tali...@gmail.com wrote: Hello again, I ran the commands again, checking to make sure the UPS was still device 005/002, and the results is: root@microserver:~# ls -l /dev/bus/usb/005/002 crw-rw-r-- 1 root nut 189, 513 Nov 4 12:55 /dev/bus/usb/005/002 I tried setting permissions of /dev/bus/usb/005/002 to 777 and ran the test again to see what that would do, but there was no difference in the status interrupt read error messages. Well, that's odd. Can you provide a little more detail about your system? (distribution, kernel version, any security mechanisms like SELinux or AppArmor, etc.) Also, what happens if you add -u root to the driver command line? (The 'chmod 777' should have been sufficient...) -- Charles Lepple clepple@gmail atcl_logs.tar.gz Description: GNU Zip compressed data ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nutdrv_atcl_usb
Hello again, I ran the commands again, checking to make sure the UPS was still device 005/002, and the results is: root@microserver:~# ls -l /dev/bus/usb/005/002 crw-rw-r-- 1 root nut 189, 513 Nov 4 12:55 /dev/bus/usb/005/002 I tried setting permissions of /dev/bus/usb/005/002 to 777 and ran the test again to see what that would do, but there was no difference in the status interrupt read error messages. On 1 November 2014 23:55, Charles Lepple clep...@gmail.com wrote: On Nov 1, 2014, at 8:09 AM, jani jani.tali...@gmail.com wrote: Hi Charles, Here is the output of those. I also ran the driver a second time with debug level 4, just in case there were any extra hints in there. Here's the culprit: 5.338858 status interrupt read: error sending control message: Operation not permitted What does 'ls -l /dev/bus/usb/005/002' say? If the UPS has been unplugged since the logs were generated, replace 005/002 with the path suffix from this set of messages: 5.499162 Checking USB device [0001:] (005/002) 5.510156 - VendorID : 0001 5.510202 - ProductID: 5.510209 - Manufacturer : ATCL FOR UPS 5.510219 - Product : ATCL FOR UPS 5.510225 - Serial Number: ATCL FOR UPS 5.510231 - Bus : 005 5.510237 Matched expected vendor='ATCL FOR UPS'. 5.512216 USB device [0001:] opened Depending on your distribution and how you installed NUT, some extra steps may be necessary to fix the permissions every time the UPS is plugged in. (NUT ships with a udev rules file.) We need to fix the logging levels - the permissions message should have been logged at a higher priority. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] nutdrv_atcl_usb
Hi Charles, Here is the output of those. I also ran the driver a second time with debug level 4, just in case there were any extra hints in there. cheers, Jani On 1 November 2014 22:12, Charles Lepple clep...@gmail.com wrote: On Nov 1, 2014, at 1:30 AM, jani wrote: Hi Charles, I just bought a UPS that announces itself as 'ATCL FOR UPS' with VendorId of 0001. It seems to be a re-badged unit manufactured by Guangdong East Power company, and besides the little brand stamp it looks identical to: http://eastups.com/en/productshow.aspx?CateId=473Id=164PCateId=447 It came with a windows cd containing the windows software entitled UPSmart2000I version 3.7 and while I haven't installed it the screenshots show that you can get input and output voltage and battery voltage information out of the thing. The problem is the nutdrv_atcl_usb driver out of nut 2.7.2 doesn't seem to function, I get the following in my logs: Nov 1 16:28:49 microserver nutdrv_atcl_usb[2242]: Warning: excessive comm failures, limiting error reporting Nov 1 16:28:49 microserver nutdrv_atcl_usb[2242]: Communications with UPS lost: Query to UPS failed Is there anything I can do to help troubleshoot the issue? Please run (as root) 'killall nutdrv_atcl_usb' and re-run the driver with the debug level set to at least 2: /path/to/nutdrv_atcl_usb -a *name* -DD 21 | tee nutdrv_atcl_usb.log Then, please gzip and send the log as an attachment (to keep the size down, and to prevent the lines from getting mangled). Also, the output of 'lsusb -vvv -d 0001:' (run as root) would be useful for comparison. atcl_usb_logs.tar.gz Description: GNU Zip compressed data ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
