<br><div class="gmail_quote">2011/2/15 Lupe Christoph<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On Monday, 2011-02-14 at 21:54:20 -0000, Arnaud Quette wrote:<br>
> I definitely need more info!<br>
> please reply to ALL:<br>
<br>
> - what is the exact model and date of manufacturing?<br>
<br>
</div>SmartUPS 300I NET. I have the serial number (GS9809283199) but no date.<br></blockquote><div><br> it seems to be a recent model.<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
> - are you sure this unit is ok?<br>
<br>
</div>You can't prove the absence of faults.<br></blockquote><div><br>this was related to the following question...<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
> - have you really checked the cabling or made the whole (cable + UPS) work<br>
> somehow (using APC's software or apcupsd)?<br>
<br>
</div>Well, as I said this is working OK for days or weeks. Then something<br>
happens that triggers a bug in apcsmart.<br></blockquote><div><br> quickly reading back the thread, I can't find these info...<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
> - what is the meantime between occurrences of these issues?<br>
<br>
</div>I don;t have enough data. It's in the range of weeks or months.<br></blockquote><div><br>as per your previous posts, this seemed more to be a matter of minutes / hours.<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">
> - is the device reachable (using upsc for example) between issues?<br>
<br>
</div>Sure, everything works fine.<br>
<div class="im"><br>
> A driver debug output is really needed!<br>
<br>
</div>I'm running it again, but no promises. Reboots are much more frequent<br>
than this misbehaviour.<br>
<div class="im"><br>
> Note that I'm not the developer of this driver, nor have any acquaintance<br>
> with APC.<br>
<br>
</div>Same here. Though I will probably try to locate this bug if we don;t<br>
make progress with the debugging output, either because it does not tell<br>
us enough or because I don't manage to capture it.<br>
<br>
I would have thought finding the place in the code where it is trying to<br>
reset the UPS connection wouldn't be this hard.<br></blockquote></div><br clear="all">this is not the problem. This code is in the smartmode() function of apcsmart.c:<br><a href="http://svn.debian.org/wsvn/nut/trunk/drivers/apcsmart.c">http://svn.debian.org/wsvn/nut/trunk/drivers/apcsmart.c</a><br>
<br>we see the 5 attempts to go to smart mode ('Y' command), but my aim is to understand why it is failing, and how to cleanly solve this without impacting support for other units.<br><br>Some more questions:<br>- how are you handling the device's permissions?<br>
Refer to § II, section 3:<br><a href="http://git.debian.org/?p=collab-maint/nut.git;a=blob_plain;f=debian/nut.README.Debian;hb=HEAD">http://git.debian.org/?p=collab-maint/nut.git;a=blob_plain;f=debian/nut.README.Debian;hb=HEAD</a><br>
<br>cheers<br>Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://powerquality.eaton.com" target="_blank">http://powerquality.eaton.com</a><br>Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/" target="_blank">http://www.networkupstools.org/</a><br>
Debian Developer - <a href="http://www.debian.org" target="_blank">http://www.debian.org</a><br>Free Software Developer - <a href="http://arnaud.quette.free.fr/" target="_blank">http://arnaud.quette.free.fr/</a><br>--<br>
Conseiller Municipal - Saint Bernard du Touvet<br>