<p>Hi Fabio</p>
<p>Please keep the list copied.<br>
It is indeed worth updating to 2.6.5 and retry blazer, in case a fix is needed.</p>
<p>Cheers<br>
Arnaud<br>
(sent from my S3... please excuse my brevity)</p>
<div class="gmail_quote">Le 6 sept. 2012 16:58, "Fabio Cecamore" <<a href="mailto:ceca_89@hotmail.com">ceca_89@hotmail.com</a>> a écrit :<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div dir="ltr">
<div style="font-size:12pt;font-family:'Calibri'">
<div>Dear <font face="Times New Roman">Arnaud, thanks for your fast
reply.</font></div>
<div><font face="Times New Roman">I’m using 2.4.3 version of nut package and if
is necessary i can update, but..</font></div>
<div><font face="Times New Roman">i yet tryied to use blazer driver but i have
the same problem:</font></div>
<div> </div><font face="Courier New"><span><font style="FONT-SIZE:9pt" color="#2e8b57">Aug 30 09:22:34 ProLiant blazer_ser[1084]:
Communications with UPS lost: status read failed!</font></span><font style="FONT-SIZE:9pt"><br style="padding-left:0px;padding-right:0px;padding-top:0px;text-indent:0px;letter-spacing:normal;font:12px/15px monaco,'Andale Mono','Courier New',courier,mono;padding-bottom:0px;color:rgb(46,139,87);text-transform:none;white-space:normal;margin:0px;word-spacing:0px">
</font><span><font style="FONT-SIZE:9pt" color="#2e8b57">Aug 30 09:22:35 ProLiant blazer_ser[1084]:
Communications with UPS re-established</font></span></font><font face="Times New Roman"> </font>
<div><font face="Times New Roman"></font> </div>
<div><font face="Times New Roman">Do you think updating nut is the right way too
?</font></div>
<div><font face="Times New Roman">Thank you again.</font></div>
<div><font face="Times New Roman">Bye</font></div>
<div style="font-size:small;font-style:normal;text-decoration:none;font-family:'Calibri';display:inline;font-weight:normal">
<div style="FONT:10pt tahoma">
<div> </div>
<div style="BACKGROUND:#f5f5f5">
<div><b>From:</b> <a title="aquette.dev@gmail.com" href="mailto:aquette.dev@gmail.com" target="_blank">Arnaud Quette</a> </div>
<div><b>Sent:</b> Thursday, September 06, 2012 4:52 PM</div>
<div><b>To:</b> <a title="ceca_89@hotmail.com" href="mailto:ceca_89@hotmail.com" target="_blank">Fabio Cecamore</a> </div>
<div><b>Cc:</b> <a title="nut-upsuser@lists.alioth.debian.org" href="mailto:nut-upsuser@lists.alioth.debian.org" target="_blank">nut-upsuser@lists.alioth.debian.org</a>
</div>
<div><b>Subject:</b> Re: [Nut-upsuser] Communications with UPS lost: No status
from UPS</div></div></div>
<div> </div></div>
<div style="font-size:small;font-style:normal;text-decoration:none;font-family:'Calibri';display:inline;font-weight:normal">Hi
Fabio<br><br>
<div class="gmail_quote">2012/9/6 Fabio Cecamore <span dir="ltr"><<a href="mailto:ceca_89@hotmail.com" target="_blank">ceca_89@hotmail.com</a>></span><br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div dir="ltr">
<div dir="ltr">
<div style="FONT-FAMILY:'Calibri';FONT-SIZE:12pt"><font face="Times New Roman">Hello,<br>i've a problem, this is my
configuration:<br>- Atlantis Land UPS with serial port<br>- a generic RS232 to
USB cable adapter (QinHeng Electronics HL-340 <br>USB-Serial adapter for
linux).<br><br>The problem is in the syslog file where i find:<br>[...]<br>Aug
19 09:07:25 ProLiant megatec[1126]: Communications with UPS lost: No
<br>status from UPS.<br>Aug 19 09:07:26 ProLiant megatec[1126]: Communications
with UPS <br>re-established<br>Aug 19 09:09:36 ProLiant megatec[1126]:
Communications with UPS lost: No <br>status from UPS.<br>Aug 19 09:09:36
ProLiant megatec[1126]: Communications with UPS
<br>re-established<br>[...]<br><br>and using the driver (blazer_ser or
megatec, is the same) in debug mode i <br>read:<br><br>0.000000 debug level is
'12'<br>0.037842 DTR=1, RTS=0<br>0.041830 send_to_all: SETINFO device.type
"ups"<br>0.041906 send_to_all: SETINFO driver.version "2.4.3"<br>0.041924
send_to_all: SETINFO driver.version.internal "1.6"<br>0.041942 send_to_all:
SETINFO <a href="http://driver.name" target="_blank">driver.name</a>
"megatec"<br>[........]<br>413.251768 Asking for UPS status
[Q1]...<br>415.854720 Q1 => FAILED [timeout]<br>415.854786 Poll failure
[1].<br>415.854803 Communications with UPS lost: No status from
UPS.<br>415.854825 Asking for UPS status [Q1]...<br>416.455619 Q1 => OK
[(229.8 140.0 229.8 004 49.8 13.6 30.7 00001001]<br>416.455723 Q1 VALUES =>
[229.8 140.0 229.8 4.0 49.8 13.6 30.7 00001001]<br>416.455739 Communications
with UPS re-established<br>416.455766 send_to_all: SETINFO input.voltage
"229.8"<br>416.455791 send_to_all: SETINFO output.voltage
"229.8"<br>416.455813 send_to_all: SETINFO input.frequency
"49.8"<br>[........]<br><br>with a infinite loop of this timeout.<br>What can
be the problem ?</font></div></div></div></blockquote></div><br>this old megatec
driver, which has since been replaced by blazer, was not as flexible when it
comes to transient communication errors.<br>thus, it was syslog'ing every such
failures, and declaring staleness more quickly.<br><br>you should consider
updating to a more recent NUT version, such as 2.6.5, along with moving to the
blazer drivers.<br><br>cheers,<br>Arnaud<br>-- <br>Linux / Unix / Opensource
Engineering Expert - Eaton - <a href="http://opensource.eaton.com" target="_blank">http://opensource.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.fr" target="_blank">http://arnaud.quette.fr</a><br><br></div></div></div></div>
</blockquote></div>