Fabio Cecamore
2012-Sep-06 14:02 UTC
[Nut-upsuser] Communications with UPS lost: No status from UPS
Hello, i've a problem, this is my configuration: - Atlantis Land UPS with serial port - a generic RS232 to USB cable adapter (QinHeng Electronics HL-340 USB-Serial adapter for linux). The problem is in the syslog file where i find: [...] Aug 19 09:07:25 ProLiant megatec[1126]: Communications with UPS lost: No status from UPS. Aug 19 09:07:26 ProLiant megatec[1126]: Communications with UPS re-established Aug 19 09:09:36 ProLiant megatec[1126]: Communications with UPS lost: No status from UPS. Aug 19 09:09:36 ProLiant megatec[1126]: Communications with UPS re-established [...] and using the driver (blazer_ser or megatec, is the same) in debug mode i read: 0.000000 debug level is '12' 0.037842 DTR=1, RTS=0 0.041830 send_to_all: SETINFO device.type "ups" 0.041906 send_to_all: SETINFO driver.version "2.4.3" 0.041924 send_to_all: SETINFO driver.version.internal "1.6" 0.041942 send_to_all: SETINFO driver.name "megatec" [........] 413.251768 Asking for UPS status [Q1]... 415.854720 Q1 => FAILED [timeout] 415.854786 Poll failure [1]. 415.854803 Communications with UPS lost: No status from UPS. 415.854825 Asking for UPS status [Q1]... 416.455619 Q1 => OK [(229.8 140.0 229.8 004 49.8 13.6 30.7 00001001] 416.455723 Q1 VALUES => [229.8 140.0 229.8 4.0 49.8 13.6 30.7 00001001] 416.455739 Communications with UPS re-established 416.455766 send_to_all: SETINFO input.voltage "229.8" 416.455791 send_to_all: SETINFO output.voltage "229.8" 416.455813 send_to_all: SETINFO input.frequency "49.8" [........] with a infinite loop of this timeout. What can be the problem ? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120906/1cf4b047/attachment.html>
Arnaud Quette
2012-Sep-06 14:52 UTC
[Nut-upsuser] Communications with UPS lost: No status from UPS
Hi Fabio 2012/9/6 Fabio Cecamore <ceca_89 at hotmail.com>> Hello, > i've a problem, this is my configuration: > - Atlantis Land UPS with serial port > - a generic RS232 to USB cable adapter (QinHeng Electronics HL-340 > USB-Serial adapter for linux). > > The problem is in the syslog file where i find: > [...] > Aug 19 09:07:25 ProLiant megatec[1126]: Communications with UPS lost: No > status from UPS. > Aug 19 09:07:26 ProLiant megatec[1126]: Communications with UPS > re-established > Aug 19 09:09:36 ProLiant megatec[1126]: Communications with UPS lost: No > status from UPS. > Aug 19 09:09:36 ProLiant megatec[1126]: Communications with UPS > re-established > [...] > > and using the driver (blazer_ser or megatec, is the same) in debug mode i > read: > > 0.000000 debug level is '12' > 0.037842 DTR=1, RTS=0 > 0.041830 send_to_all: SETINFO device.type "ups" > 0.041906 send_to_all: SETINFO driver.version "2.4.3" > 0.041924 send_to_all: SETINFO driver.version.internal "1.6" > 0.041942 send_to_all: SETINFO driver.name "megatec" > [........] > 413.251768 Asking for UPS status [Q1]... > 415.854720 Q1 => FAILED [timeout] > 415.854786 Poll failure [1]. > 415.854803 Communications with UPS lost: No status from UPS. > 415.854825 Asking for UPS status [Q1]... > 416.455619 Q1 => OK [(229.8 140.0 229.8 004 49.8 13.6 30.7 00001001] > 416.455723 Q1 VALUES => [229.8 140.0 229.8 4.0 49.8 13.6 30.7 00001001] > 416.455739 Communications with UPS re-established > 416.455766 send_to_all: SETINFO input.voltage "229.8" > 416.455791 send_to_all: SETINFO output.voltage "229.8" > 416.455813 send_to_all: SETINFO input.frequency "49.8" > [........] > > with a infinite loop of this timeout. > What can be the problem ? >this old megatec driver, which has since been replaced by blazer, was not as flexible when it comes to transient communication errors. thus, it was syslog'ing every such failures, and declaring staleness more quickly. you should consider updating to a more recent NUT version, such as 2.6.5, along with moving to the blazer drivers. cheers, Arnaud -- Linux / Unix / Opensource Engineering Expert - Eaton - http://opensource.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120906/2abd72f5/attachment.html>
Arnaud Quette
2012-Sep-06 18:04 UTC
[Nut-upsuser] Communications with UPS lost: No status from UPS
Hi Fabio Please keep the list copied. It is indeed worth updating to 2.6.5 and retry blazer, in case a fix is needed. Cheers Arnaud (sent from my S3... please excuse my brevity) Le 6 sept. 2012 16:58, "Fabio Cecamore" <ceca_89 at hotmail.com> a ?crit :> Dear Arnaud, thanks for your fast reply. > I?m using 2.4.3 version of nut package and if is necessary i can update, > but.. > i yet tryied to use blazer driver but i have the same problem: > > Aug 30 09:22:34 ProLiant blazer_ser[1084]: Communications with UPS lost: > status read failed! > Aug 30 09:22:35 ProLiant blazer_ser[1084]: Communications with UPS > re-established > > Do you think updating nut is the right way too ? > Thank you again. > Bye > > *From:* Arnaud Quette <aquette.dev at gmail.com> > *Sent:* Thursday, September 06, 2012 4:52 PM > *To:* Fabio Cecamore <ceca_89 at hotmail.com> > *Cc:* nut-upsuser at lists.alioth.debian.org > *Subject:* Re: [Nut-upsuser] Communications with UPS lost: No status from > UPS > > Hi Fabio > > 2012/9/6 Fabio Cecamore <ceca_89 at hotmail.com> > >> Hello, >> i've a problem, this is my configuration: >> - Atlantis Land UPS with serial port >> - a generic RS232 to USB cable adapter (QinHeng Electronics HL-340 >> USB-Serial adapter for linux). >> >> The problem is in the syslog file where i find: >> [...] >> Aug 19 09:07:25 ProLiant megatec[1126]: Communications with UPS lost: No >> status from UPS. >> Aug 19 09:07:26 ProLiant megatec[1126]: Communications with UPS >> re-established >> Aug 19 09:09:36 ProLiant megatec[1126]: Communications with UPS lost: No >> status from UPS. >> Aug 19 09:09:36 ProLiant megatec[1126]: Communications with UPS >> re-established >> [...] >> >> and using the driver (blazer_ser or megatec, is the same) in debug mode i >> read: >> >> 0.000000 debug level is '12' >> 0.037842 DTR=1, RTS=0 >> 0.041830 send_to_all: SETINFO device.type "ups" >> 0.041906 send_to_all: SETINFO driver.version "2.4.3" >> 0.041924 send_to_all: SETINFO driver.version.internal "1.6" >> 0.041942 send_to_all: SETINFO driver.name "megatec" >> [........] >> 413.251768 Asking for UPS status [Q1]... >> 415.854720 Q1 => FAILED [timeout] >> 415.854786 Poll failure [1]. >> 415.854803 Communications with UPS lost: No status from UPS. >> 415.854825 Asking for UPS status [Q1]... >> 416.455619 Q1 => OK [(229.8 140.0 229.8 004 49.8 13.6 30.7 00001001] >> 416.455723 Q1 VALUES => [229.8 140.0 229.8 4.0 49.8 13.6 30.7 00001001] >> 416.455739 Communications with UPS re-established >> 416.455766 send_to_all: SETINFO input.voltage "229.8" >> 416.455791 send_to_all: SETINFO output.voltage "229.8" >> 416.455813 send_to_all: SETINFO input.frequency "49.8" >> [........] >> >> with a infinite loop of this timeout. >> What can be the problem ? >> > > this old megatec driver, which has since been replaced by blazer, was not > as flexible when it comes to transient communication errors. > thus, it was syslog'ing every such failures, and declaring staleness more > quickly. > > you should consider updating to a more recent NUT version, such as 2.6.5, > along with moving to the blazer drivers. > > cheers, > Arnaud > -- > Linux / Unix / Opensource Engineering Expert - Eaton - > http://opensource.eaton.com > Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org > Debian Developer - http://www.debian.org > Free Software Developer - http://arnaud.quette.fr > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120906/251305e1/attachment.html>