similar to: Nut-upsuser Digest, Vol 175, Issue 30

On 1/25/20 10:53 AM, Georgi D. Sotirov wrote: > OK, so yesterday evening I done a real test cutting of the power to > the UPS. And it went good... the UPS supported my server for 28:50 > minutes (i.e. the expected runtime with this load), before forcing > shutdown. The batteries could still hold as charge was 30 % with about > 15 minutes run time. And the UPS did hold for

Hello. I sometimes encountered batteries that were ok, but at times one of the cells would develop a random short/open, therefore reducing the real capacity even if voltage reading was ok. In the absence of a battery load tester i would suggest running multiple tests with a load (car headlight bulb or similar) on the battery outside the ups. This is to eliminate the suspicion of a software or UPS

OK, so yesterday evening I done a real test cutting of the power to the UPS. And it went good... the UPS supported my server for 28:50 minutes (i.e. the expected runtime with this load), before forcing shutdown. The batteries could still hold as charge was 30 % with about 15 minutes run time. And the UPS did hold for another full 10 minutes before powering off. These are the relevant lines

On January 11, 2020 1:18:27 PM GMT+02:00, "Georgi D. Sotirov" <gdsotirov at gmail.com> wrote: >Hello, > >I'm experiencing a strange early shutdown behavior with the following >system: > > * */OS/*: Slackware Linux 14.2 x86_64 > * */NUT/*: 2.7.4 (from my own package > <https://sotirov-bg.net/slackpack/pack.cgi?id=4083>) > * */UPS/*: MGE

Hello, I'm experiencing a strange early shutdown behavior with the following system: * */OS/*: Slackware Linux 14.2 x86_64 * */NUT/*: 2.7.4 (from my own package <https://sotirov-bg.net/slackpack/pack.cgi?id=4083>) * */UPS/*: MGE Ellipse PRO 1600 <powerquality.eaton.com/Products-services/Backup-Power-UPS/Ellipse-PRO.aspx> (bought in September 2017) */Problem

On January 24, 2020 6:13:31 PM GMT+02:00, "Georgi D. Sotirov" <gdsotirov at gmail.com> wrote: >OK, my UPS turned out to be older that I thought. I apparently bought >and installed it in September 2016 (not 2017 as I initially wrote). >That >makes for over 3 years of work, which is over the life expectancy of >the >batteries, Good batteries can last 4-5 years.

On Tue, 29 Sep 2020, João Luis Meloni Assirati wrote: > The UPS I am developing a driver to is able to report several flags for > critical hardware conditions, like overheat, overload, inverter failure, > output short etc. What should be the correct policy of operation when such a > condition occurs? I think that the an UPS in such a condition is not reliable > and therefore a

I found something interesting that I think may apply here. Check this out... https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave *I have the latest version of the Windows port of NUT (A UPS management package) installed on my Windows 7 machine. The UPS I am using is a very old APC BK650M which is controlled and sends its status via a special serial cable to the

On Fri, 14 Aug 2020, Todd Benivegna wrote: > https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave  > > I have the latest version of the Windows port of NUT (A UPS management package) installed on my Windows 7 machine. The UPS I am using is a > very old APC BK650M which is controlled and sends its status via a special serial cable to the Windows

Hi, recently I observed that during a power outage, my NUT setup doesn't shutdown properly. Indeed it never reaches the LowBattery state to notify and initiate shutdown on clients. Reviewing my setup and logs I think I'm facing multiple problems and I'm unable to point to real root cause. First, let me focus on my scenario and current setup: In normal status (ONLINE, fully charged)

Sorry, I guess it is */usr/syno/bin/synoups* On Fri, Aug 14, 2020 at 2:27 PM Todd Benivegna <todd at benivegna.com> wrote: > I found something interesting that I think may apply here. Check this > out... > > > > https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave > > *I have the latest version of the Windows port of NUT (A UPS

On January 11, 2020 3:42:15 PM GMT+02:00, Roger Price <roger at rogerprice.org> wrote: >On Sat, 11 Jan 2020, Georgi D. Sotirov wrote: > >> Jan 11 11:49:15 sotirov-bg upsmon[2677]: UPS mgeups at localhost on >battery >> Jan 11 11:49:15 sotirov-bg upssched[29746]: Executing command: >ups-on-battery >> Jan 11 11:49:15 sotirov-bg upssched-cmd: Unrecognized command:

Hello. Battery, battery, battery. I am only thinking at worn batteries. I recently had the same symptoms with an hp/eaton g3 1500va. One of the 3 batteries was reading a healthy 12.8v, but when put under load it would quickly drain. I would measure each battery and test them under load, like with a car headlight bulb switched on both fillaments. On Thu, 23 Apr 2020, 16:54 Marc Franquesa,

> On 9 Jun 2019, at 21:19, Roger Price <roger at rogerprice.org> wrote: > Using upssched and a upssched-cmd script to shut down the system is an alternative to using the builtin upsmon SHUTDOWNCMD on status [OB LB]. A upssched-cmd script can provide a managed shutdown well before [OB LB] is reached, but should the UPS reach that status upsmon's SHUTDOWNCMD will take over and

On Sat, 11 Jan 2020, Georgi D. Sotirov wrote: > Jan 11 11:49:15 sotirov-bg upsmon[2677]: UPS mgeups at localhost on battery > Jan 11 11:49:15 sotirov-bg upssched[29746]: Executing command: ups-on-battery > Jan 11 11:49:15 sotirov-bg upssched-cmd: Unrecognized command: ups-on-battery These lines say that you have something like AT ONBATT mgeups at localhost EXECUTE ups-on-battery

Here is patch 2 of 2. Roger diff -rup -x '*.html' -x '*.8' -x '*.5' nut-2.7.4.orig/docs/man/upsd.txt nut-2.7.4.dev/docs/man/upsd.txt --- nut-2.7.4.orig/docs/man/upsd.txt 2015-12-29 09:42:34.000000000 +0100 +++ nut-2.7.4.dev/docs/man/upsd.txt 2016-07-07 10:08:51.939354892 +0200 @@ -119,6 +119,16 @@ administrative functions like SET and IN controlled in

Hello, I am a new user of NUT and trying to wrap my ahead around a couple of things. I installed NUT 2.7.4-13 from package on RasPi 4, running Raspbian Linux 11 (bullseye). I have Cyberpower SL700U connected to it. For testing I set battery.charge.low to 90, so I wouldn't have to wait a long time. See all relevant config below. First of all, what seems to happen is that UPS gets to the low

Hi! I'm trying to setup a small mobile server rack with key switch to power on/off the whole system. Used USP is an APC Smart-UPS 1500 SMT1500RMI2U with extra AP9613 IO card [1] to get the key switch "connected" to the UPS. The IO card has several inputs which can trigger actions like power on and "gracefully" shutdown. On key switch OFF this SMT ups model changes ups

I have the latest version of the Windows port of NUT installed on my Windows?7?machine. The UPS is connected via serial cable to the Windows machine. I also have my Synology NAS (which uses NUT) connected over the local network as a slave to the Windows NUT master. The Synology slave is configured to immediately go into "safe mode" whenever an FSD or OB+LB indication is received from the