<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 07/06/2017 12:19 AM, Ambrogio
Coletti wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKkaXqp811an96YfMd8QVmfo+L7=1xdCXM+Nz5+wpY0UEH-Bhg@mail.gmail.com">
<div dir="ltr">I've eventually installed Manuel's packages (nut
and nut-client).
<div><br>
<div>When I run the driver as root (for my tripplite ups) I
get:</div>
<div><br>
</div>
<font face="monospace">/usr/sbin/upsdrvctl start<br>
Network UPS Tools - Generic HID driver 0.42
(v2.7.4-418-gb1314c62.7.4.1)<br>
USB communication driver (libusb 0.1) 0.33<br>
writepid: fopen </font><font face="monospace"><font
face="monospace">/var/run/nut/</font>usbhid-ups-trippliteups.pid:
Permission denied<br>
</font></div>
</div>
</blockquote>
that is odd because nut-client should have created <font
face="monospace">/var/run/nut/. If you run rpm -ql nut-client you
will notice that /var/run/nut is listed in the very last line:<br>
<br>
[root@belgrade ~]# rpm -ql --qf
"%{name}-%{version}-%{release}\n\n"
nut-client <br>
nut-client-2.7.5-0.20170613gitb1314c6.el6.wolfy.usb01 (ignore the
"usb01" tag, I added it for my personal reference since I built
against various libusb versions)<br>
<br>
/etc/rc.d/init.d/ups<br>
/etc/ups<br>
/etc/ups/upsmon.conf<br>
/etc/ups/upssched.conf<br>
[...]<br>
/usr/share/pixmaps/nut-monitor.png<br>
/var/lib/ups<br>
/var/run/nut <=============<br>
<br>
<br>
</font><br>
<blockquote type="cite"
cite="mid:CAKkaXqp811an96YfMd8QVmfo+L7=1xdCXM+Nz5+wpY0UEH-Bhg@mail.gmail.com">
<div dir="ltr">
<div><font face="monospace">Can't claim USB device [09ae:1330]:
could not detach kernel driver from interface 0: Operation
not permitted<br>
</font></div>
</div>
</blockquote>
That's the error I get with one of my UPSes ( an Eaton ) as well. No
solution so far for me.<br>
<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAKkaXqp811an96YfMd8QVmfo+L7=1xdCXM+Nz5+wpY0UEH-Bhg@mail.gmail.com">
<div dir="ltr">
<div><font face="monospace">Driver failed to start (exit
status=1) </font></div>
<div><font face="monospace"><br>
</font></div>
<div>And I had to create manually /var/run/nut.</div>
<div><br>
</div>
<div>What is the problem there? <font face="monospace"><br>
</font></div>
</div>
</blockquote>
I am really puzzled. Do you get any selinux related errors ( running
aureport -ts today -a should list the AVCs if any )?<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAKkaXqp811an96YfMd8QVmfo+L7=1xdCXM+Nz5+wpY0UEH-Bhg@mail.gmail.com"><br>
<div class="gmail_quote">
<div dir="ltr">On Fri, Jun 23, 2017 at 8:27 PM Manuel Wolfshant
<<a href="mailto:wolfy@nobugconsulting.ro"
moz-do-not-send="true">wolfy@nobugconsulting.ro</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">On
06/24/2017 04:52 AM, Charles Lepple wrote:<br>
> On Jun 23, 2017, at 5:50 PM, Ambrogio Coletti <<a
href="mailto:ambrojohn@gmail.com" target="_blank"
moz-do-not-send="true">ambrojohn@gmail.com</a>> wrote:<br>
>> "This TrippLite device (09ae:1330) is not (or perhaps
not yet) supported by usbhid-ups. [...]"<br>
>> but my device (SU2200RTXLCD2U) is supported, as
clearly state here.<br>
> No, the HCL also mentions "protocol 4001". For
Tripp-Lite, a USB PID other than 0001 is generally the
protocol number. So your SU2200* model is different.<br>
><br>
> <a
href="https://github.com/networkupstools/nut/issues/64"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/networkupstools/nut/issues/64</a><br>
><br>
>> Then I thought I needed the last src code (2.7.4),
hence I built it for my machine, but when I run it by:<br>
>> /usr/local/ups/sbin/upsdrvctl start<br>
> The Protocol 1330 support was added after 2.7.4 was
released. You might be able to use a 2.7.4 tarball with
"productid = 1330" in ups.conf, but voltages might be off by a
factor of 10. You will also need to adjust the udev files
manually to fix /dev/bus/usb permissions.<br>
><br>
> If you do choose to build using the latest source code
from Git, be aware that you will need more tools, as specified
in the Developer Guide: <a
href="http://networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://networkupstools.org/docs/developer-guide.chunked/ar01s03.html#building</a><br>
><br>
> It may be easier to use the 2.7.4 tarball, and add the
patch which introduces Protocol 1330 support to the RPM spec
file: <a
href="https://github.com/networkupstools/nut/commit/4eff5b7068e9873ce11b5a296f403e8cdf0e3580"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/networkupstools/nut/commit/4eff5b7068e9873ce11b5a296f403e8cdf0e3580</a><br>
I've uploaded to <a href="http://wolfy.fedorapeople.org/nut"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://wolfy.fedorapeople.org/nut</a>
a new set of packages<br>
based on the latest source code from git. Unfortunately they
do not<br>
include any man pages, I did not have time to find a
workaround for the<br>
hard requirement of newer versions for the tools used by the
build<br>
process to create the man pages. I will fix that in a later
set of packages.<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@lists.alioth.debian.org"
target="_blank" moz-do-not-send="true">Nut-upsuser@lists.alioth.debian.org</a><br>
<a
href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser"
rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>