On Nov 1, 2014, at 8:09 AM, jani <jani.talikka at 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:0000] (005/002) 5.510156 - VendorID : 0001 5.510202 - ProductID : 0000 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:0000] 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 at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser-- Charles Lepple clepple at gmail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20141101/57e360af/attachment.html>
Hello again, I ran the commands again, checking to make sure the UPS was still device 005/002, and the results is:> root at 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 <clepple at gmail.com> wrote:> On Nov 1, 2014, at 8:09 AM, jani <jani.talikka at 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:0000] (005/002) > 5.510156 - VendorID : 0001 > 5.510202 - ProductID : 0000 > 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:0000] 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 at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser > > > -- > Charles Lepple > clepple at gmail > > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20141104/c1a2511c/attachment.html>
On Nov 3, 2014, at 9:01 PM, jani <jani.talikka at 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 at 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 at gmail -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20141103/07cbefc5/attachment.html>