Jump to content

6.1.8 Lost Comm with UPS


a12vman

Recommended Posts

Hi-

    I am seeing the dreaded lost communication with UPS message.  

 

Was working fine for quite a while but suddenly stopped.  I have the APC Backup-UPS 550

 

Nothing wrong with the APC UPS itself, I tested communication between my Win 7 Laptop via USB and the APC Software.

 

Here are my UPS Settings, I don't have any extra UPS-related plugins installed:

 

APC 001,017,0449 DATE 2017-04-30 13:48:34 -0400
HOSTNAME MediaTower VERSION 3.14.13 (02 February 2015) slackware
CABLE Custom Cable Smart DRIVER APC Smart UPS (any)
UPSMODE Stand Alone STARTTIME 2017-04-30 13:47:34 -0400
STATUS Lost communication MBATTCHG 40 Percent
MINTIMEL 10 Minutes MAXTIME 0 Seconds
NUMXFERS 0 TONBATT 0 Seconds
CUMONBATT 0 Seconds XOFFBATT N/A
STATFLAG 0x05000100 END APC 2017-04-30 15:34:07 -0400
Link to comment

I can suggest two things.  First, get a diagnostics file  (  "Tools"   >>>    "Diagnostics"   )    and post it up with your next post.  Second Thing:  Try and new UPS cable (I've got a pile of them laying around-- hopefully you do to)  and use a UBS2 port.  (Some UBS3 ports on some MB's seem to occasionally get 'lost' with unRAID.) 

 

EDIT:  and don't reboot before you get that diagnostics!

Link to comment

Start and stop the UPS service (   'Settings'  >>>  'UPS Settings'   >>>   'UPS Settings'   ) after each change you make while testing things.  I don't know if this is necessary as I haven't seen a lot of problems with the UPS software and unRAID on the forum so no one has a lot of experience in trouble shooting...  

Link to comment

Try setting 'UPS Cable: usb' and 'UPS Type: usb'.  Based on the logs you are using a USB cable and not the APC serial to USB cable so I don't see a need for the custom cable type.  Your Back-UPS ES 550G is not a 'smart' UPS so the standard USB driver is needed.  Unplug and plug back in the USB cable after making the changes, if needed.

Link to comment

 

9 minutes ago, a12vman said:

Online 100.0 Percent        11.6 Minutes            - - 29.0 Percent

 

Make sure your 'Time on Battery before shutdown' is very short.  (I would be setting it for less than a minute.)   You don't have a lot of battery reserve and this becomes an issue when you have a power outage and then the power in all restored.  You think everything is alright and turn the server back on.  Now the power goes out again and the battery hasn't recharged enough to be able to get the server shutdown before the battery is discharged.  (Full recharge time is more than eight hours for inexpensive UPS's.)

Link to comment
  • 9 months later...

Setup a new server (second server) running 6.2.4 and unable to get the UPS set up correctly.

 

Have read the posts above and a few others. Not able to resolve.

 

Initially sees the APC UPS and then "lost communication."

 

I had the NUT plugin (deprecated and current) installed for a brief time but wanted to stick with the APCUPSD instead.

 

Attached is a screen shot of the details and the log.

 

Any help solving would be appreciated....

UPS 1.PNG

UPS Log.txt

Link to comment

Here is the log....

 

Feb 27 18:20:30 Tower2 root: plugin: creating: /tmp/start_nut - from INLINE content
Feb 27 18:20:30 Tower2 root: plugin: setting: /tmp/start_nut - mode to 0770
Feb 27 18:20:30 Tower2 root: plugin: running: anonymous
Feb 27 18:27:52 Tower2 php: /usr/local/emhttp/plugins/nut/scripts/start
Feb 27 18:27:54 Tower2 usbhid-ups[26902]: Startup successful
Feb 27 18:27:55 Tower2 upsd[26909]: listening on 0.0.0.0 port 3493
Feb 27 18:27:55 Tower2 upsd[26909]: Connected to UPS [ups]: usbhid-ups-ups
Feb 27 18:27:55 Tower2 upsd[26910]: Startup successful
Feb 27 18:28:17 Tower2 emhttp: cmd: /usr/local/emhttp/plugins/nut/scripts/nutscan
Feb 27 18:29:05 Tower2 php: /usr/local/emhttp/plugins/nut/scripts/start
Feb 27 18:29:19 Tower2 emhttp: cmd: /usr/local/emhttp/plugins/nut/scripts/nutscan
Feb 27 18:29:46 Tower2 emhttp: cmd: /usr/local/emhttp/plugins/nut/scripts/nutscan
Feb 27 18:30:06 Tower2 emhttp: cmd: /usr/local/emhttp/plugins/nut/scripts/nutscan
Feb 27 18:30:35 Tower2 php: /usr/local/emhttp/plugins/nut/scripts/stop
Feb 27 18:30:37 Tower2 upsd[26910]: mainloop: Interrupted system call
Feb 27 18:30:37 Tower2 upsd[26910]: Signal 15: exiting
Feb 27 18:30:39 Tower2 usbhid-ups[26902]: Signal 15: exiting
Feb 27 18:30:57 Tower2 php: /usr/local/emhttp/plugins/nut/scripts/start
Feb 27 18:32:16 Tower2 emhttp: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin remove nut.plg
Feb 27 18:32:16 Tower2 root: plugin: running: anonymous
Feb 27 18:34:45 Tower2 apcupsd[411]: apcupsd 3.14.13 (02 February 2015) slackware startup succeeded
Feb 27 18:34:45 Tower2 apcupsd[411]: NIS server startup succeeded
Feb 27 18:35:46 Tower2 apcupsd[411]: apcupsd exiting, signal 15
Feb 27 18:35:46 Tower2 apcupsd[411]: apcupsd shutdown succeeded
Feb 27 18:35:56 Tower2 apcupsd[1083]: apcupsd 3.14.13 (02 February 2015) slackware startup succeeded
Feb 27 18:35:56 Tower2 apcupsd[1083]: NIS server startup succeeded
Feb 27 18:37:06 Tower2 apcupsd[1083]: Communications with UPS lost.
Feb 27 18:37:06 Tower2 sSMTP[2031]: Creating SSL connection to host
Feb 27 18:37:07 Tower2 sSMTP[2031]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Feb 27 18:37:09 Tower2 sSMTP[2031]: Sent mail for XXXXXXXXXXXXX (221 Service Closing transmission) uid=0 username=root outbytes=666
Feb 27 18:43:19 Tower2 apcupsd[1083]: apcupsd exiting, signal 15
Feb 27 18:43:19 Tower2 apcupsd[1083]: apcupsd shutdown succeeded
Feb 27 18:44:57 Tower2 apcupsd[6083]: apcupsd 3.14.13 (02 February 2015) slackware startup succeeded
Feb 27 18:44:57 Tower2 apcupsd[6083]: NIS server startup succeeded
Feb 27 18:46:07 Tower2 apcupsd[6083]: Communications with UPS lost.
Feb 27 18:46:07 Tower2 sSMTP[6676]: Creating SSL connection to host
Feb 27 18:46:07 Tower2 sSMTP[6676]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256
Feb 27 18:46:09 Tower2 sSMTP[6676]: Sent mail for XXXXXXXXXXXX (221 Service Closing transmission) uid=0 username=root outbytes=666

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...