similar to: Panic timeout?

On Tue, 21 Mar 2017, Arnaud Quette wrote: > Hi Roger, > > reviving this discussion, since we have a Github ticket for 2.7.5: > https://github.com/networkupstools/nut/issues/293 ... > I've made some additions to clarify things on the timer, and complete the script: > https://github.com/networkupstools/nut/compare/upssched-doc?expand=1 Hi Arnaud, Your change to the

Hi, I’ve posted my question on Superuser.com but not had any replies in 2 weeks, so I guess no-one there knows anything about NUT. https://superuser.com/questions/1441153/how-to-shutdown-macos-mac-osx-from-network-ups-tools-client-nut <https://superuser.com/questions/1441153/how-to-shutdown-macos-mac-osx-from-network-ups-tools-client-nut> I’m looking for help in shutting down my iMac on

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 just got at work an MGE UPS Comet EX RT 7 and I can communicate fine with it through mge-shut, it detects correctly when on battery. I am using Nut 2.0.3 on Linux (RHEL 3). I am trying to simulate a low battery condition to test my shutdown procedure by setting lowbatt to 98%: driver.parameter.lowbatt: 98 but the ups reaches this value, goes to 97% and still no LB. I tried to change,

Well it is the season for storms and power outages here in the US PNW. I noticed that today when the power went out, NUT mostly did what I hoped/wanted. But it did not actually turn off the UPS at all. The UPS kept beeping and I had to turn it off manually. I thought that NUT would handle this. But perhaps it cannot for my unit? Or perhaps I have things improperly configured? Any suggestions?

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)

On Jan 21, 2014, at 3:16 AM, Rafa? Oleszek wrote: > I would like to mention that MINSUPPLIES manipulation doesn't work. My nut version is : 2.2.2-4 (RHEL 5) What do your configuration files look like? Setting MINSUPPLIES to 2 should work. You can run upsmon with a debug level of 3 or greater, and it will print the current and minimum "power value", which is what determines

On Sat, 4 Jun 2016, Charles Lepple wrote: > On Jun 3, 2016, at 6:48 AM, Roger Price <roger at rogerprice.org> wrote: >> ... the timer. I don't see it in /var/lib/ups where the locate tool >> finds upsd.pid, and I don't see it in /run or /var/run where I see >> upsmon.pid. >> > ... it seems that the timers are only stored in memory. See >

Hi Arnaud, On Wed, 22 Mar 2017, Arnaud Quette wrote: > The technique is very general and is to send SIGUSR1/SIGUSR2 to the upsd daemon.? SIGUSR1 and SIGUSR2 are events just like ONBATT and ONLINE. > The patch runs successfully on my opensuse 13.2 box, and solves my problem. In upssched.conf I now have declarations such as > > ? ?AT SIGUSR1 * CANCEL-TIMER

On Jun 8, 2019, at 4:16 PM, Roger Price wrote: > > Is your System Shutdown Plan to shut down using upsmon or using the script upsched-cmd? In upssched.conf you do not have a line > > AT LOWBATT ups at ... EXECUTE lowbatt > > and in upssched-cmd there is nothing to shut down the system. Joe, Roger has a good point - the SHUTDOWNCMD should work as long as the master system

Hi! Some systems I have take some time to shut down, so I would like them to shut down if the UPS have been on battery for 2 minutes. Internet has told me that SHUTDOWNCMD ?/sbin/shutdown -h +0? in /etc/nut/upsmon.conf will execute when the UPS is both OB (on battery) and LB (Low battery). Like in wiki.ipfire.org - Detailed NUT Configuration<https://wiki.ipfire.org/addons/nut/detailed>

> What do your configuration files look like? Setting MINSUPPLIES to 2 should work. You can run upsmon with a debug level of 3 or greater, and it will print the current and minimum "power value", which is what determines when to shut down. > > Also, if you don't want to wait for both UPSes to drain to the low battery state, you can set up a pair of dummy-ups drivers. I'm

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 Jan 21, 2014, at 9:24 AM, Rafal Oleszek wrote: > >> I tried all options: >> 1,2 >> and in MINSUPPLIES: 1,2,3,4 >> still didn't work. > > My mistake - I gave you the wrong advice before. For MINSUPPLIES, I'm used > to either a 1:1 UPS-to-server ratio, or 2:1 where the server can run with > either power supply unpowered. > > I just tried

On Sun, 9 Jun 2019, Joe Gervasio wrote: > This question undermines my reading of the documentation.  I had thought that > these were separate things:  > >     SHUTDOWNCMD "/sbin/shutdown -u -h +1"  >     NOTIFYCMD /opt/local/sbin/upssched > > I had assumed that the SHUTDOWNCMD would be used by the Nut client (upsmon) to > shutdown the slave system,  and that

On Jan 21, 2014, at 9:24 AM, Rafal Oleszek wrote: > I tried all options: > 1,2 > and in MINSUPPLIES: 1,2,3,4 > still didn't work. My mistake - I gave you the wrong advice before. For MINSUPPLIES, I'm used to either a 1:1 UPS-to-server ratio, or 2:1 where the server can run with either power supply unpowered. I just tried this in upsmon.conf: MONITOR dummy1 1 monuser

On Mon, 10 Aug 2020, Todd Benivegna wrote: > synoups: https://hastebin.com/xexafofiha.bash Wow! What a mess. It looks as if Synology wanted to write their own "NUT", but decided it would be easier to put their ideas in a script when they saw they could use upssched.conf to call it. NUT intends such a script for timer management. Synology use it for general system management.

I've setup nas4free (latest version 11.0.0.4, which has NUT 2.7.4) in a VM and configured it via webinterface to my APC UPS and set "shutdown mode" to "UPS goes on battery" with a timer of 30s. Then I started runtime calibration on the UPS and after 30s nas4free has shut down! I think this is not the correct behavior, since the status was "OB CAL". The system

On Jun 29, 2017, at 6:52 AM, Andrea de Lutti wrote: >>> Anyway I still not receive any email on any test (power cord disconnected and/or reconnected for example) >> >> Oh, I misinterpreted "working script" as a script that was sending email, rather than work-in-progress. Does that same command work from the command line? Can you add something like "logger"