Warning communications lost with UPS

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Warning communications lost with UPS

ph.l@libertysurf.fr
Hello,

I recently got a pretty old BackUPS Pro 650 but it runs fine and is
enought for my small server.

It is connected using a 940-0095A cable on my serial port.

When I power on my USB printer, I get the message :

Diffusion de message de root@phlsys (somewhere) (Sun Dec  4 12:02:00
2016) :
Warning communications lost with UPS PHLUPS.

and the log shows

2016-12-04 08:47:19 +0100  apcupsd 3.14.12 (29 March 2014) debian
startup succeeded
2016-12-04 12:02:00 +0100  Communications with UPS lost.

doing  service apcupsd status, it shows

apcupsd.service - LSB: Starts apcupsd daemon
   Loaded: loaded (/etc/init.d/apcupsd)
   Active: active (running) since dim. 2016-12-04 08:47:19 CET; 4h 11min ago
  Process: 925 ExecStart=/etc/init.d/apcupsd start (code=exited,
status=0/SUCCESS)
   CGroup: /system.slice/apcupsd.service
           └─991 /sbin/apcupsd

déc. 04 08:47:19 phlsys apcupsd[925]: Starting UPS power management:
apcupsd.
déc. 04 08:47:19 phlsys apcupsd[991]: apcupsd 3.14.12 (29 March 2014)
debian startup succeeded
déc. 04 08:47:19 phlsys apcupsd[991]: NIS server startup succeeded
déc. 04 08:47:19 phlsys systemd[1]: Started LSB: Starts apcupsd daemon.
déc. 04 12:02:00 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:12:00 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:22:00 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:32:01 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:42:01 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:52:02 phlsys apcupsd[991]: Communications with UPS lost.

Then after restart status shows :

apcupsd.service - LSB: Starts apcupsd daemon
   Loaded: loaded (/etc/init.d/apcupsd)
   Active: active (running) since dim. 2016-12-04 08:47:19 CET; 4h 13min ago
  Process: 925 ExecStart=/etc/init.d/apcupsd start (code=exited,
status=0/SUCCESS)
   CGroup: /system.slice/apcupsd.service
           └─991 /sbin/apcupsd

déc. 04 08:47:19 phlsys apcupsd[991]: apcupsd 3.14.12 (29 March 2014)
debian startup succeeded
déc. 04 08:47:19 phlsys apcupsd[991]: NIS server startup succeeded
déc. 04 08:47:19 phlsys systemd[1]: Started LSB: Starts apcupsd daemon.
déc. 04 12:02:00 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:12:00 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:22:00 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:32:01 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:42:01 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:52:02 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 13:00:26 phlsys systemd[1]: Started LSB: Starts apcupsd daemon.

Any  idea on what happen ?

Thanks a lot for any suggestion

Philippe


Please find on below what my config is :

## apcupsd.conf v1.1 ##
#  for apcupsd release 3.14.12 (29 March 2014) - debian
# "apcupsd" POSIX config file

UPSNAME PHLUPS
UPSCABLE 940-0095A
UPSTYPE apcsmart
DEVICE /dev/ttyS0
ONBATTERYDELAY 6
BATTERYLEVEL 5
MINUTES 3
TIMEOUT 0
ANNOY 300
ANNOYDELAY 60
NOLOGON disable
KILLDELAY 0
NETSERVER on
UPSCLASS standalone
UPSMODE disable


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Warning communications lost with UPS

Adam Płaszczyca

Can you access ups on console via apcaccess?


4 gru 2016 13:21 "[hidden email]" <[hidden email]> napisał(a):
Hello,

I recently got a pretty old BackUPS Pro 650 but it runs fine and is
enought for my small server.

It is connected using a 940-0095A cable on my serial port.

When I power on my USB printer, I get the message :

Diffusion de message de root@phlsys (somewhere) (Sun Dec  4 12:02:00
2016) :
Warning communications lost with UPS PHLUPS.

and the log shows

2016-12-04 08:47:19 +0100  apcupsd 3.14.12 (29 March 2014) debian
startup succeeded
2016-12-04 12:02:00 +0100  Communications with UPS lost.

doing  service apcupsd status, it shows

apcupsd.service - LSB: Starts apcupsd daemon
   Loaded: loaded (/etc/init.d/apcupsd)
   Active: active (running) since dim. 2016-12-04 08:47:19 CET; 4h 11min ago
  Process: 925 ExecStart=/etc/init.d/apcupsd start (code=exited,
status=0/SUCCESS)
   CGroup: /system.slice/apcupsd.service
           └─991 /sbin/apcupsd

déc. 04 08:47:19 phlsys apcupsd[925]: Starting UPS power management:
apcupsd.
déc. 04 08:47:19 phlsys apcupsd[991]: apcupsd 3.14.12 (29 March 2014)
debian startup succeeded
déc. 04 08:47:19 phlsys apcupsd[991]: NIS server startup succeeded
déc. 04 08:47:19 phlsys systemd[1]: Started LSB: Starts apcupsd daemon.
déc. 04 12:02:00 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:12:00 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:22:00 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:32:01 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:42:01 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:52:02 phlsys apcupsd[991]: Communications with UPS lost.

Then after restart status shows :

apcupsd.service - LSB: Starts apcupsd daemon
   Loaded: loaded (/etc/init.d/apcupsd)
   Active: active (running) since dim. 2016-12-04 08:47:19 CET; 4h 13min ago
  Process: 925 ExecStart=/etc/init.d/apcupsd start (code=exited,
status=0/SUCCESS)
   CGroup: /system.slice/apcupsd.service
           └─991 /sbin/apcupsd

déc. 04 08:47:19 phlsys apcupsd[991]: apcupsd 3.14.12 (29 March 2014)
debian startup succeeded
déc. 04 08:47:19 phlsys apcupsd[991]: NIS server startup succeeded
déc. 04 08:47:19 phlsys systemd[1]: Started LSB: Starts apcupsd daemon.
déc. 04 12:02:00 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:12:00 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:22:00 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:32:01 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:42:01 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 12:52:02 phlsys apcupsd[991]: Communications with UPS lost.
déc. 04 13:00:26 phlsys systemd[1]: Started LSB: Starts apcupsd daemon.

Any  idea on what happen ?

Thanks a lot for any suggestion

Philippe


Please find on below what my config is :

## apcupsd.conf v1.1 ##
#  for apcupsd release 3.14.12 (29 March 2014) - debian
# "apcupsd" POSIX config file

UPSNAME PHLUPS
UPSCABLE 940-0095A
UPSTYPE apcsmart
DEVICE /dev/ttyS0
ONBATTERYDELAY 6
BATTERYLEVEL 5
MINUTES 3
TIMEOUT 0
ANNOY 300
ANNOYDELAY 60
NOLOGON disable
KILLDELAY 0
NETSERVER on
UPSCLASS standalone
UPSMODE disable


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Warning communications lost with UPS

ph.l@libertysurf.fr
Thank you Adam for your reply :)

I have to tell that my UPS perfectly runs.
Since I installed it (around 6 month) I had some small power downs and
it did its job like a charm !

Yes, I have access to acpaccess and the result seems good:

# apcaccess
APC      : 001,048,1104
DATE     : 2016-12-04 12:00:36 +0100
HOSTNAME : phlsys
VERSION  : 3.14.12 (29 March 2014) debian
UPSNAME  : PHLUPS
CABLE    : Custom Cable Smart
DRIVER   : APC Smart UPS (any)
UPSMODE  : Stand Alone
STARTTIME: 2016-12-04 08:47:19 +0100
MODEL    : Back-UPS Pro 650
STATUS   : COMMLOST
LINEV    : 233.2 Volts
LOADPCT  : 13.0 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 64.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
MAXLINEV : 234.7 Volts
MINLINEV : 230.4 Volts
OUTPUTV  : 233.2 Volts
SENSE    : High
DWAKE    : 0 Seconds
DSHUTD   : 20 Seconds
DLOWBATT : 2 Minutes
LOTRANS  : 208.0 Volts
HITRANS  : 253.0 Volts
RETPCT   : 0.0 Percent
ALARMDEL : 5 Seconds
BATTV    : 13.8 Volts
LINEFREQ : 50.0 Hz
LASTXFER : Automatic or explicit self test
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : NO
STESTI   : 336
STATFLAG : 0x05000108
REG1     : 0x00
REG2     : 0x00
REG3     : 0x00
MANDATE  : 09/30/99
SERIALNO : NB9940151901
BATTDATE : 09/30/99
NOMOUTV  : 230 Volts
NOMBATTV : 12.0 Volts
FIRMWARE : 12.4.I
END APC  : 2016-12-04 17:54:44 +0100


Le 04/12/2016 à 13:28, Adam Płaszczyca a écrit :

>
> Can you access ups on console via apcaccess?
>
>
> 4 gru 2016 13:21 "[hidden email] <mailto:[hidden email]>"
> <[hidden email] <mailto:[hidden email]>> napisał(a):
>
>     Hello,
>
>     I recently got a pretty old BackUPS Pro 650 but it runs fine and is
>     enought for my small server.
>
>     It is connected using a 940-0095A cable on my serial port.
>
>     When I power on my USB printer, I get the message :
>
>     Diffusion de message de root@phlsys (somewhere) (Sun Dec  4 12:02:00
>     2016) :
>     Warning communications lost with UPS PHLUPS.
>
>     and the log shows
>
>     2016-12-04 08:47:19 +0100  apcupsd 3.14.12 (29 March 2014) debian
>     startup succeeded
>     2016-12-04 12:02:00 +0100  Communications with UPS lost.
>
>     doing  service apcupsd status, it shows
>
>     apcupsd.service - LSB: Starts apcupsd daemon
>        Loaded: loaded (/etc/init.d/apcupsd)
>        Active: active (running) since dim. 2016-12-04 08:47:19 CET; 4h
>     11min ago
>       Process: 925 ExecStart=/etc/init.d/apcupsd start (code=exited,
>     status=0/SUCCESS)
>        CGroup: /system.slice/apcupsd.service
>                └─991 /sbin/apcupsd
>
>     déc. 04 08:47:19 phlsys apcupsd[925]: Starting UPS power management:
>     apcupsd.
>     déc. 04 08:47:19 phlsys apcupsd[991]: apcupsd 3.14.12 (29 March 2014)
>     debian startup succeeded
>     déc. 04 08:47:19 phlsys apcupsd[991]: NIS server startup succeeded
>     déc. 04 08:47:19 phlsys systemd[1]: Started LSB: Starts apcupsd
>     daemon.
>     déc. 04 12:02:00 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:12:00 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:22:00 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:32:01 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:42:01 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:52:02 phlsys apcupsd[991]: Communications with UPS lost.
>
>     Then after restart status shows :
>
>     apcupsd.service - LSB: Starts apcupsd daemon
>        Loaded: loaded (/etc/init.d/apcupsd)
>        Active: active (running) since dim. 2016-12-04 08:47:19 CET; 4h
>     13min ago
>       Process: 925 ExecStart=/etc/init.d/apcupsd start (code=exited,
>     status=0/SUCCESS)
>        CGroup: /system.slice/apcupsd.service
>                └─991 /sbin/apcupsd
>
>     déc. 04 08:47:19 phlsys apcupsd[991]: apcupsd 3.14.12 (29 March 2014)
>     debian startup succeeded
>     déc. 04 08:47:19 phlsys apcupsd[991]: NIS server startup succeeded
>     déc. 04 08:47:19 phlsys systemd[1]: Started LSB: Starts apcupsd
>     daemon.
>     déc. 04 12:02:00 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:12:00 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:22:00 phlsys apprettycupsd[991]: Communications with
>     UPS lost.
>     déc. 04 12:32:01 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:42:01 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:52:02 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 13:00:26 phlsys systemd[1]: Started LSB: Starts apcupsd
>     daemon.
>
>     Any  idea on what happen ?
>
>     Thanks a lot for any suggestion
>
>     Philippe
>
>
>     Please find on below what my config is :
>
>     ## apcupsd.conf v1.1 ##
>     #  for apcupsd release 3.14.12 (29 March 2014) - debian
>     # "apcupsd" POSIX config file
>
>     UPSNAME PHLUPS
>     UPSCABLE 940-0095A
>     UPSTYPE apcsmart
>     DEVICE /dev/ttyS0
>     ONBATTERYDELAY 6
>     BATTERYLEVEL 5
>     MINUTES 3
>     TIMEOUT 0
>     ANNOY 300
>     ANNOYDELAY 60
>     NOLOGON disable
>     KILLDELAY 0
>     NETSERVER on
>     UPSCLASS standalone
>     UPSMODE disable
>
>
>     ------------------------------------------------------------------------------
>     Check out the vibrant tech community on one of the world's most
>     engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>     _______________________________________________
>     Apcupsd-users mailing list
>     [hidden email]
>     <mailto:[hidden email]>
>     https://lists.sourceforge.net/lists/listinfo/apcupsd-users
>     <https://lists.sourceforge.net/lists/listinfo/apcupsd-users>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> Apcupsd-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Warning communications lost with UPS

Adam Płaszczyca
Well, comlost - looks like issue with connection. What apctest will tell (stop apcupsd before launching)?

4 gru 2016 18:03 "[hidden email]" <[hidden email]> napisał(a):
Thank you Adam for your reply :)

I have to tell that my UPS perfectly runs.
Since I installed it (around 6 month) I had some small power downs and
it did its job like a charm !

Yes, I have access to acpaccess and the result seems good:

# apcaccess
APC      : 001,048,1104
DATE     : 2016-12-04 12:00:36 +0100
HOSTNAME : phlsys
VERSION  : 3.14.12 (29 March 2014) debian
UPSNAME  : PHLUPS
CABLE    : Custom Cable Smart
DRIVER   : APC Smart UPS (any)
UPSMODE  : Stand Alone
STARTTIME: 2016-12-04 08:47:19 +0100
MODEL    : Back-UPS Pro 650
STATUS   : COMMLOST
LINEV    : 233.2 Volts
LOADPCT  : 13.0 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 64.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
MAXLINEV : 234.7 Volts
MINLINEV : 230.4 Volts
OUTPUTV  : 233.2 Volts
SENSE    : High
DWAKE    : 0 Seconds
DSHUTD   : 20 Seconds
DLOWBATT : 2 Minutes
LOTRANS  : 208.0 Volts
HITRANS  : 253.0 Volts
RETPCT   : 0.0 Percent
ALARMDEL : 5 Seconds
BATTV    : 13.8 Volts
LINEFREQ : 50.0 Hz
LASTXFER : Automatic or explicit self test
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : NO
STESTI   : 336
STATFLAG : 0x05000108
REG1     : 0x00
REG2     : 0x00
REG3     : 0x00
MANDATE  : 09/30/99
SERIALNO : NB9940151901
BATTDATE : 09/30/99
NOMOUTV  : 230 Volts
NOMBATTV : 12.0 Volts
FIRMWARE : 12.4.I
END APC  : 2016-12-04 17:54:44 +0100


Le 04/12/2016 à 13:28, Adam Płaszczyca a écrit :
>
> Can you access ups on console via apcaccess?
>
>
> 4 gru 2016 13:21 "[hidden email] <mailto:[hidden email]>"
> <[hidden email] <mailto:[hidden email]>> napisał(a):
>
>     Hello,
>
>     I recently got a pretty old BackUPS Pro 650 but it runs fine and is
>     enought for my small server.
>
>     It is connected using a 940-0095A cable on my serial port.
>
>     When I power on my USB printer, I get the message :
>
>     Diffusion de message de root@phlsys (somewhere) (Sun Dec  4 12:02:00
>     2016) :
>     Warning communications lost with UPS PHLUPS.
>
>     and the log shows
>
>     2016-12-04 08:47:19 +0100  apcupsd 3.14.12 (29 March 2014) debian
>     startup succeeded
>     2016-12-04 12:02:00 +0100  Communications with UPS lost.
>
>     doing  service apcupsd status, it shows
>
>     apcupsd.service - LSB: Starts apcupsd daemon
>        Loaded: loaded (/etc/init.d/apcupsd)
>        Active: active (running) since dim. 2016-12-04 08:47:19 CET; 4h
>     11min ago
>       Process: 925 ExecStart=/etc/init.d/apcupsd start (code=exited,
>     status=0/SUCCESS)
>        CGroup: /system.slice/apcupsd.service
>                └─991 /sbin/apcupsd
>
>     déc. 04 08:47:19 phlsys apcupsd[925]: Starting UPS power management:
>     apcupsd.
>     déc. 04 08:47:19 phlsys apcupsd[991]: apcupsd 3.14.12 (29 March 2014)
>     debian startup succeeded
>     déc. 04 08:47:19 phlsys apcupsd[991]: NIS server startup succeeded
>     déc. 04 08:47:19 phlsys systemd[1]: Started LSB: Starts apcupsd
>     daemon.
>     déc. 04 12:02:00 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:12:00 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:22:00 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:32:01 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:42:01 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:52:02 phlsys apcupsd[991]: Communications with UPS lost.
>
>     Then after restart status shows :
>
>     apcupsd.service - LSB: Starts apcupsd daemon
>        Loaded: loaded (/etc/init.d/apcupsd)
>        Active: active (running) since dim. 2016-12-04 08:47:19 CET; 4h
>     13min ago
>       Process: 925 ExecStart=/etc/init.d/apcupsd start (code=exited,
>     status=0/SUCCESS)
>        CGroup: /system.slice/apcupsd.service
>                └─991 /sbin/apcupsd
>
>     déc. 04 08:47:19 phlsys apcupsd[991]: apcupsd 3.14.12 (29 March 2014)
>     debian startup succeeded
>     déc. 04 08:47:19 phlsys apcupsd[991]: NIS server startup succeeded
>     déc. 04 08:47:19 phlsys systemd[1]: Started LSB: Starts apcupsd
>     daemon.
>     déc. 04 12:02:00 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:12:00 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:22:00 phlsys apprettycupsd[991]: Communications with
>     UPS lost.
>     déc. 04 12:32:01 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:42:01 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 12:52:02 phlsys apcupsd[991]: Communications with UPS lost.
>     déc. 04 13:00:26 phlsys systemd[1]: Started LSB: Starts apcupsd
>     daemon.
>
>     Any  idea on what happen ?
>
>     Thanks a lot for any suggestion
>
>     Philippe
>
>
>     Please find on below what my config is :
>
>     ## apcupsd.conf v1.1 ##
>     #  for apcupsd release 3.14.12 (29 March 2014) - debian
>     # "apcupsd" POSIX config file
>
>     UPSNAME PHLUPS
>     UPSCABLE 940-0095A
>     UPSTYPE apcsmart
>     DEVICE /dev/ttyS0
>     ONBATTERYDELAY 6
>     BATTERYLEVEL 5
>     MINUTES 3
>     TIMEOUT 0
>     ANNOY 300
>     ANNOYDELAY 60
>     NOLOGON disable
>     KILLDELAY 0
>     NETSERVER on
>     UPSCLASS standalone
>     UPSMODE disable
>
>
>     ------------------------------------------------------------------------------
>     Check out the vibrant tech community on one of the world's most
>     engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>     _______________________________________________
>     Apcupsd-users mailing list
>     [hidden email]
>     <mailto:[hidden email]>
>     https://lists.sourceforge.net/lists/listinfo/apcupsd-users
>     <https://lists.sourceforge.net/lists/listinfo/apcupsd-users>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> Apcupsd-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Warning communications lost with UPS

ph.l@libertysurf.fr
Hi Adam,

When I received your email, I was re reading my mine to you and saw the
COMLOST ... I just stop and restart the service.
(This morning I relaunched the service without stop it.)

Now it is better :
# apcaccess
APC      : 001,048,1102
DATE     : 2016-12-04 18:20:22 +0100
HOSTNAME : phlsys
VERSION  : 3.14.12 (29 March 2014) debian
UPSNAME  : PHLUPS
CABLE    : Custom Cable Smart
DRIVER   : APC Smart UPS (any)
UPSMODE  : Stand Alone
STARTTIME: 2016-12-04 18:20:10 +0100
MODEL    : Back-UPS Pro 650
STATUS   : ONLINE
LINEV    : 234.7 Volts
LOADPCT  : 12.3 Percent
BCHARGE  : 100.0 Percent
TIMELEFT : 69.0 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
MAXLINEV : 234.7 Volts
MINLINEV : 233.2 Volts
OUTPUTV  : 234.7 Volts
SENSE    : High
DWAKE    : 0 Seconds
DSHUTD   : 20 Seconds
DLOWBATT : 2 Minutes
LOTRANS  : 208.0 Volts
HITRANS  : 253.0 Volts
RETPCT   : 0.0 Percent
ALARMDEL : 5 Seconds
BATTV    : 13.8 Volts
LINEFREQ : 50.0 Hz
LASTXFER : Automatic or explicit self test
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : NO
STESTI   : 336
STATFLAG : 0x05000008
REG1     : 0x00
REG2     : 0x00
REG3     : 0x00
MANDATE  : 09/30/99
SERIALNO : NB9940151901
BATTDATE : 09/30/99
NOMOUTV  : 230 Volts
NOMBATTV : 12.0 Volts
FIRMWARE : 12.4.I
END APC  : 2016-12-04 18:20:23 +0100

Le 04/12/2016 à 18:20, Adam Płaszczyca a écrit :

> Well, comlost - looks like issue with connection. What apctest will
> tell (stop apcupsd before launching)?
>
> 4 gru 2016 18:03 "[hidden email] <mailto:[hidden email]>"
> <[hidden email] <mailto:[hidden email]>> napisał(a):
>
>     Thank you Adam for your reply :)
>
>     I have to tell that my UPS perfectly runs.
>     Since I installed it (around 6 month) I had some small power downs and
>     it did its job like a charm !
>
>     Yes, I have access to acpaccess and the result seems good:
>
>     # apcaccess
>     APC      : 001,048,1104
>     DATE     : 2016-12-04 12:00:36 +0100
>     HOSTNAME : phlsys
>     VERSION  : 3.14.12 (29 March 2014) debian
>     UPSNAME  : PHLUPS
>     CABLE    : Custom Cable Smart
>     DRIVER   : APC Smart UPS (any)
>     UPSMODE  : Stand Alone
>     STARTTIME: 2016-12-04 08:47:19 +0100
>     MODEL    : Back-UPS Pro 650
>     STATUS   : COMMLOST
>     LINEV    : 233.2 Volts
>     LOADPCT  : 13.0 Percent
>     BCHARGE  : 100.0 Percent
>     TIMELEFT : 64.0 Minutes
>     MBATTCHG : 5 Percent
>     MINTIMEL : 3 Minutes
>     MAXTIME  : 0 Seconds
>     MAXLINEV : 234.7 Volts
>     MINLINEV : 230.4 Volts
>     OUTPUTV  : 233.2 Volts
>     SENSE    : High
>     DWAKE    : 0 Seconds
>     DSHUTD   : 20 Seconds
>     DLOWBATT : 2 Minutes
>     LOTRANS  : 208.0 Volts
>     HITRANS  : 253.0 Volts
>     RETPCT   : 0.0 Percent
>     ALARMDEL : 5 Seconds
>     BATTV    : 13.8 Volts
>     LINEFREQ : 50.0 Hz
>     LASTXFER : Automatic or explicit self test
>     NUMXFERS : 0
>     TONBATT  : 0 Seconds
>     CUMONBATT: 0 Seconds
>     XOFFBATT : N/A
>     SELFTEST : NO
>     STESTI   : 336
>     STATFLAG : 0x05000108
>     REG1     : 0x00
>     REG2     : 0x00
>     REG3     : 0x00
>     MANDATE  : 09/30/99
>     SERIALNO : NB9940151901
>     BATTDATE : 09/30/99
>     NOMOUTV  : 230 Volts
>     NOMBATTV : 12.0 Volts
>     FIRMWARE : 12.4.I
>     END APC  : 2016-12-04 17:54:44 +0100
>
>
>     Le 04/12/2016 à 13:28, Adam Płaszczyca a écrit :
>     >
>     > Can you access ups on console via apcaccess?
>     >
>     >
>     > 4 gru 2016 13:21 "[hidden email]
>     <mailto:[hidden email]> <mailto:[hidden email]
>     <mailto:[hidden email]>>"
>     > <[hidden email] <mailto:[hidden email]>
>     <mailto:[hidden email] <mailto:[hidden email]>>> napisał(a):
>     >
>     >     Hello,
>     >
>     >     I recently got a pretty old BackUPS Pro 650 but it runs fine
>     and is
>     >     enought for my small server.
>     >
>     >     It is connected using a 940-0095A cable on my serial port.
>     >
>     >     When I power on my USB printer, I get the message :
>     >
>     >     Diffusion de message de root@phlsys (somewhere) (Sun Dec  4
>     12:02:00
>     >     2016) :
>     >     Warning communications lost with UPS PHLUPS.
>     >
>     >     and the log shows
>     >
>     >     2016-12-04 08:47:19 +0100  apcupsd 3.14.12 (29 March 2014)
>     debian
>     >     startup succeeded
>     >     2016-12-04 12:02:00 +0100  Communications with UPS lost.
>     >
>     >     doing  service apcupsd status, it shows
>     >
>     >     apcupsd.service - LSB: Starts apcupsd daemon
>     >        Loaded: loaded (/etc/init.d/apcupsd)
>     >        Active: active (running) since dim. 2016-12-04 08:47:19
>     CET; 4h
>     >     11min ago
>     >       Process: 925 ExecStart=/etc/init.d/apcupsd start (code=exited,
>     >     status=0/SUCCESS)
>     >        CGroup: /system.slice/apcupsd.service
>     >                └─991 /sbin/apcupsd
>     >
>     >     déc. 04 08:47:19 phlsys apcupsd[925]: Starting UPS power
>     management:
>     >     apcupsd.
>     >     déc. 04 08:47:19 phlsys apcupsd[991]: apcupsd 3.14.12 (29
>     March 2014)
>     >     debian startup succeeded
>     >     déc. 04 08:47:19 phlsys apcupsd[991]: NIS server startup
>     succeeded
>     >     déc. 04 08:47:19 phlsys systemd[1]: Started LSB: Starts apcupsd
>     >     daemon.
>     >     déc. 04 12:02:00 phlsys apcupsd[991]: Communications with
>     UPS lost.
>     >     déc. 04 12:12:00 phlsys apcupsd[991]: Communications with
>     UPS lost.
>     >     déc. 04 12:22:00 phlsys apcupsd[991]: Communications with
>     UPS lost.
>     >     déc. 04 12:32:01 phlsys apcupsd[991]: Communications with
>     UPS lost.
>     >     déc. 04 12:42:01 phlsys apcupsd[991]: Communications with
>     UPS lost.
>     >     déc. 04 12:52:02 phlsys apcupsd[991]: Communications with
>     UPS lost.
>     >
>     >     Then after restart status shows :
>     >
>     >     apcupsd.service - LSB: Starts apcupsd daemon
>     >        Loaded: loaded (/etc/init.d/apcupsd)
>     >        Active: active (running) since dim. 2016-12-04 08:47:19
>     CET; 4h
>     >     13min ago
>     >       Process: 925 ExecStart=/etc/init.d/apcupsd start (code=exited,
>     >     status=0/SUCCESS)
>     >        CGroup: /system.slice/apcupsd.service
>     >                └─991 /sbin/apcupsd
>     >
>     >     déc. 04 08:47:19 phlsys apcupsd[991]: apcupsd 3.14.12 (29
>     March 2014)
>     >     debian startup succeeded
>     >     déc. 04 08:47:19 phlsys apcupsd[991]: NIS server startup
>     succeeded
>     >     déc. 04 08:47:19 phlsys systemd[1]: Started LSB: Starts apcupsd
>     >     daemon.
>     >     déc. 04 12:02:00 phlsys apcupsd[991]: Communications with
>     UPS lost.
>     >     déc. 04 12:12:00 phlsys apcupsd[991]: Communications with
>     UPS lost.
>     >     déc. 04 12:22:00 phlsys apprettycupsd[991]: Communications with
>     >     UPS lost.
>     >     déc. 04 12:32:01 phlsys apcupsd[991]: Communications with
>     UPS lost.
>     >     déc. 04 12:42:01 phlsys apcupsd[991]: Communications with
>     UPS lost.
>     >     déc. 04 12:52:02 phlsys apcupsd[991]: Communications with
>     UPS lost.
>     >     déc. 04 13:00:26 phlsys systemd[1]: Started LSB: Starts apcupsd
>     >     daemon.
>     >
>     >     Any  idea on what happen ?
>     >
>     >     Thanks a lot for any suggestion
>     >
>     >     Philippe
>     >
>     >
>     >     Please find on below what my config is :
>     >
>     >     ## apcupsd.conf v1.1 ##
>     >     #  for apcupsd release 3.14.12 (29 March 2014) - debian
>     >     # "apcupsd" POSIX config file
>     >
>     >     UPSNAME PHLUPS
>     >     UPSCABLE 940-0095A
>     >     UPSTYPE apcsmart
>     >     DEVICE /dev/ttyS0
>     >     ONBATTERYDELAY 6
>     >     BATTERYLEVEL 5
>     >     MINUTES 3
>     >     TIMEOUT 0
>     >     ANNOY 300
>     >     ANNOYDELAY 60
>     >     NOLOGON disable
>     >     KILLDELAY 0
>     >     NETSERVER on
>     >     UPSCLASS standalone
>     >     UPSMODE disable
>     >
>     >
>     >  
>      ------------------------------------------------------------------------------
>     >     Check out the vibrant tech community on one of the world's most
>     >     engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>     >     _______________________________________________
>     >     Apcupsd-users mailing list
>     >     [hidden email]
>     <mailto:[hidden email]>
>     >     <mailto:[hidden email]
>     <mailto:[hidden email]>>
>     >     https://lists.sourceforge.net/lists/listinfo/apcupsd-users
>     <https://lists.sourceforge.net/lists/listinfo/apcupsd-users>
>     >     <https://lists.sourceforge.net/lists/listinfo/apcupsd-users
>     <https://lists.sourceforge.net/lists/listinfo/apcupsd-users>>
>     >
>     >
>     >
>     >
>     ------------------------------------------------------------------------------
>     > Check out the vibrant tech community on one of the world's most
>     > engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>     >
>     >
>     > _______________________________________________
>     > Apcupsd-users mailing list
>     > [hidden email]
>     <mailto:[hidden email]>
>     > https://lists.sourceforge.net/lists/listinfo/apcupsd-users
>     <https://lists.sourceforge.net/lists/listinfo/apcupsd-users>
>
>
>
>     ------------------------------------------------------------------------------
>     Check out the vibrant tech community on one of the world's most
>     engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>     _______________________________________________
>     Apcupsd-users mailing list
>     [hidden email]
>     <mailto:[hidden email]>
>     https://lists.sourceforge.net/lists/listinfo/apcupsd-users
>     <https://lists.sourceforge.net/lists/listinfo/apcupsd-users>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>
>
> _______________________________________________
> Apcupsd-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/apcupsd-users



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Apcupsd-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/apcupsd-users
Loading...