Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

Smart UPS 420 fails with system overload repeatable on saturday afternoon between 3 and 4 a clock pm

APC UPS Data Center & Enterprise Solutions Forum

Schneider, APC support forum to share knowledge about installation and configuration for Data Center and Business Power UPSs, Accessories, Software, Services.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • APC UPS, Critical Power, Cooling and Racks
  • APC UPS Data Center & Enterprise Solutions Forum
  • Smart UPS 420 fails with system overload repeatable on saturday afternoon between 3 and 4 a clock pm
Options
  • Subscribe to RSS Feed
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
BillP
Administrator BillP Administrator
5060
voidstar_apc
Janeway voidstar_apc
196
Erasmus_apc
Sisko Erasmus_apc
112
TheNotoriousKMP_apc
Sisko TheNotoriousKMP_apc
108
View All

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Back to APC UPS Data Center & Enterprise Solutions Forum
ecaroh_apc
ecaroh_apc
Cadet

Posted: ‎2021-06-30 11:07 PM . Last Modified: ‎2024-03-06 03:24 AM

0 Likes
0
742
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2021-06-30 11:07 PM . Last Modified: ‎2024-03-06 03:24 AM

Smart UPS 420 fails with system overload repeatable on saturday afternoon between 3 and 4 a clock pm

I have an SMART UPS 420 with batteries one year old. There should be no battery overload, cause besides a modem and a router only one small server is attached. APCUPSD says it has 33 % UPS Load, 100 % Battery capacity and 32 mins run time remaining.

The UPS suddenly fails supplying power. The server and the modem are powered of. The UPS has an ongoing beep and the system overload LED is on. I have to switch the UPS on again.

The surprising fact is, that this happened round about 5 times in the last year always on a saturday afternoon between 3 and 4 pm. There are no hints from the apcupsd event logs. I have no clue where to start, cause i can not imagine an overload causing the situation. Especially when there should be not more load on the weekend. The monitoring of the server has no hint of extra cpu load at this time. And there has been more load on it while it worked without outage. To reduce it i bought a second UPS and divided system load between them. 

Below the output of apcupsd running on linux with serial cable. Does anybody have ideas of a saturday afternoon overload? The last outage happend apr. at 4:00 pm 1 and a half hour before the last log line on 2015-11-21 17:23:38 with message unknown startup succeeded when i bring back the ups online again.

Just a guess; can apcupsd on linux shut down the power via the serial cable? Then it maybe a fault on apcupsd side?

This are samples of "unknown startup succeeded" - always saturday after a shutdown/overload where i started the ups again:

  1 2015-11-21 17:23:38 +0100

  2 2015-10-24 16:56:27 +0200

  3 2015-08-29 17:39:41 +0200

  4 2015-07-18 09:20:09 +0200

  5 2015-07-04 11:22:44 +0200

  6 2015-03-21 13:18:41 +0100

  7 2015-01-17 15:28:47 +0100

  8 2014-12-06 15:20:39 +0100

  9 2014-11-15 16:47:59 +0100

10 2014-11-08 17:28:59 +0100

11 2014-10-11 17:20:36 +0200

Monitoring: of-srv-ipf-1
 UPS Model: Smart-UPS 420   
  UPS Name: UPS_IDEN
   APCUPSD: Version 3.14.10
    Status: ONLINE 
Last UPS Self Test: NO
Last Test Date: Not found
Utility Voltage: 233.2 VAC
   Line Minimum: 231.8 VAC
   Line Maximum: 233.2 VAC
    Output Freq: 50.0 Hz

2015-11-21 17:23:38 +0100 apcupsd 3.14.10 (13 September 2011) unknown startup succeeded
2015-10-24 16:56:27 +0200 apcupsd 3.14.10 (13 September 2011) unknown startup succeeded
2015-09-17 15:58:20 +0200 Power is back. UPS running on mains.
2015-09-17 15:58:18 +0200 Power failure.
2015-08-29 17:39:41 +0200 apcupsd 3.14.10 (13 September 2011) unknown startup succeeded
2015-08-29 16:31:06 +0200 apcupsd shutdown succeeded
2015-08-29 16:31:06 +0200 apcupsd exiting, signal 15
2015-08-29 14:52:36 +0200 apcupsd 3.14.10 (13 September 2011) unknown startup succeeded
2015-08-29 14:49:06 +0200 apcupsd shutdown succeeded
2015-08-29 14:49:06 +0200 apcupsd exiting, signal 15
2015-08-25 15:39:32 +0200 Power is back. UPS running on mains.
2015-08-25 15:39:30 +0200 Power failure.
2015-08-15 16:22:47 +0200 UPS Self Test completed: Battery OK
2015-08-15 16:22:39 +0200 UPS Self Test switch to battery.
2015-08-01 16:22:13 +0200 UPS Self Test completed: Battery OK
2015-08-01 16:22:06 +0200 UPS Self Test switch to battery.
2015-07-24 14:44:00 +0200 apcupsd 3.14.10 (13 September 2011) unknown startup succeeded
2015-07-24 14:39:54 +0200 apcupsd shutdown succeeded
2015-07-24 14:39:54 +0200 apcupsd exiting, signal 15
2015-07-18 16:22:30 +0200 UPS Self Test completed: Battery OK
2015-07-18 16:22:27 +0200 UPS Self Test switch to battery.
2015-07-18 09:20:09 +0200 apcupsd 3.14.10 (13 September 2011) unknown startup succeeded
2015-07-18 09:16:43 +0200 apcupsd shutdown succeeded
2015-07-18 09:16:43 +0200 apcupsd exiting, signal 15
2015-07-04 11:22:44 +0200 apcupsd 3.14.10 (13 September 2011) unknown startup succeeded
2015-07-04 11:19:17 +0200 apcupsd shutdown succeeded
2015-07-04 11:19:17 +0200 apcupsd exiting, signal 15
2015-06-01 03:02:31 +0200 Power is back. UPS running on mains.
2015-06-01 03:02:29 +0200 Power failure.
2015-06-01 03:01:47 +0200 Power is back. UPS running on mains.
2015-06-01 03:01:45 +0200 Power failure.
2015-04-01 17:24:35 +0200 apcupsd 3.14.10 (13 September 2011) unknown startup succeeded
2015-04-01 17:21:03 +0200 apcupsd shutdown succeeded
2015-04-01 17:21:03 +0200 apcupsd exiting, signal 15
2015-03-21 13:18:41 +0100 apcupsd 3.14.10 (13 September 2011) unknown startup succeeded
2015-03-21 13:15:17 +0100 apcupsd shutdown succeeded
2015-03-21 13:15:17 +0100 apcupsd exiting, signal 15
2015-01-28 11:11:27 +0100 Power is back. UPS running on mains.
2015-01-28 11:11:26 +0100 Power failure.
2015-01-25 12:40:48 +0100 apcupsd 3.14.10 (13 September 2011) unknown startup succeeded
2015-01-25 12:37:30 +0100 apcupsd shutdown succeeded
2015-01-25 12:37:30 +0100 apcupsd exiting, signal 15
2015-01-17 15:28:47 +0100 apcupsd 3.14.10 (13 September 2011) unknown startup succeeded
2015-01-14 19:23:09 +0100 apcupsd 3.14.10 (13 September 2011) unknown startup succeeded
2015-01-14 19:19:46 +0100 apcupsd shutdown succeeded
2015-01-14 19:19:46 +0100 apcupsd exiting, signal 15
2014-12-20 15:17:33 +0100 UPS Self Test completed: Battery OK
2014-12-20 15:17:26 +0100 UPS Self Test switch to battery.
2014-12-06 15:20:39 +0100 apcupsd 3.14.10 (13 September 2011) unknown startup succeeded
2014-11-15 16:47:59 +0100 apcupsd 3.14.10 (13 September 2011) unknown startup succeeded

output of apcupsd.conf without comments: 

UPSCABLE smart

UPSTYPE apcsmart

DEVICE /dev/ttyS0

LOCKFILE /var/lock

SCRIPTDIR /etc/apcupsd

PWRFAILDIR /etc/apcupsd

NOLOGINDIR /etc

ONBATTERYDELAY 6

BATTERYLEVEL 5

MINUTES 3

TIMEOUT 0

ANNOY 300

ANNOYDELAY 60

NOLOGON disable

KILLDELAY 0

NETSERVER on

NISIP 0.0.0.0

NISPORT 3551

EVENTSFILE /var/log/apcupsd.events

EVENTSFILEMAX 10

UPSCLASS standalone

UPSMODE disable

STATTIME 0

STATFILE /var/log/apcupsd.status

LOGSTATS off

DATATIME 0

Labels
  • Labels:
  • Smart-UPS & Symmetra LX | RM
Reply

Link copied. Please paste this link to share this article on your social media post.

  • All forum topics
  • Previous Topic
  • Next Topic
Replies 0
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of