<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Op 21-10-2010 9:58, Arnaud Quette schreef:
<blockquote
cite="mid:AANLkTinsheypTYtZ_j7B_TVhM595nko9=pEQk1EqHTWE@mail.gmail.com"
type="cite">Hi Mark,<br>
<br>
<div class="gmail_quote">2010/10/20 Mark Ruys<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;"> Op 19-10-2010 23:57, Arjen de Korte
schreef:
<div class="im">
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
Citeren Mark Ruys :<br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
How to prevent these messages? Is something wrong
(probably). How to debug it.<br>
<br>
Thanks,<br>
<br>
Mark<br>
<br>
CentOS 5.4<br>
nut-2.2.0-7.el5<br>
nut-client-2.2.0-7.el5<br>
</blockquote>
<br>
Upgrade NUT to the latest version first. Loads of changes
have been made to the usbhid-ups driver since nut-2.2.0
was released well over three years ago. We no longer
support this version.<br>
<br>
Best regards, Arjen<br>
</blockquote>
<br>
</div>
Okay, I upgraded to 2.4.3 and restarted nut. I still get:<br>
<br>
Oct 20 11:33:16 alkmene kernel: usb 3-1: usbfs: process 16588
<div class="im"><br>
(usbhid-ups) did not claim interface 0 before use<br>
</div>
Oct 20 11:33:48 alkmene last message repeated 43 times<br>
Oct 20 11:34:50 alkmene last message repeated 85 times<br>
</blockquote>
</div>
<br clear="all">
upgrading NUT is not enough: you also have to stop the old
instances and start new ones that use the newly installed version.<br>
this remark comes from the fact the PID above (16588) is the same
than the previous "faulty" one.<br>
</blockquote>
<br>
Ah, this is a very good observation of you! I did run a 'service ups
restart', but the usbhid-ups process wasn't killed. I had to
manually kill it. From now on, a restart of the ups service does
restart the usbhid-ups process as expected. Perhaps I should have
issued a 'service ups stop' before I upgraded from 2.2 to 2.4 as I
expect that the 2.2 /etc/init.d/ups would killed the usbhid-ups
process.<br>
<br>
Furthermore, the 'usbhid-ups did not claim interface 0 before use'
messages now have disappeared. So also Arjen's advice to upgrade was
useful :)<br>
<br>
Thanks,<br>
Mark<br>
<br>
<blockquote
cite="mid:AANLkTinsheypTYtZ_j7B_TVhM595nko9=pEQk1EqHTWE@mail.gmail.com"
type="cite"><br>
cheers,<br>
Arnaud<br>
-- <br>
Linux / Unix Expert R&D - Eaton - <a moz-do-not-send="true"
href="http://www.eaton.com/mgeops">http://www.eaton.com/mgeops</a><br>
Network UPS Tools (NUT) Project Leader - <a
moz-do-not-send="true" href="http://www.networkupstools.org/">http://www.networkupstools.org/</a><br>
Debian Developer - <a moz-do-not-send="true"
href="http://www.debian.org">http://www.debian.org</a><br>
Free Software Developer - <a moz-do-not-send="true"
href="http://arnaud.quette.free.fr/">http://arnaud.quette.free.fr/</a><br>
<br>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Oudenhof 14b, 4191 NW Geldermalsen, The Netherlands
Web site and travel directions: <a class="moz-txt-link-abbreviated" href="http://www.in2sports.net">www.in2sports.net</a>
Phone +31.88.0084102 :: Mobile +31.6.51298623</pre>
</body>
</html>