<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
This is the first time that i had to use E-mail like forums i'm only hitting reply to mail NOT replay to all mails</div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="background-color: rgb(255, 255, 0);">THIS IS upssched.conf</span></div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
# This file is auto-generated by openmediavault (https://www.openmediavault.org)</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
# WARNING: Do not edit this file, your changes will get lost.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
CMDSCRIPT /usr/bin/upssched-cmd</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
PIPEFN /run/nut/upssched.pipe</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
LOCKFN /run/nut/upssched.lock</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
AT COMMOK * EXECUTE notify</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
AT COMMBAD * EXECUTE notify</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
AT REPLBATT * EXECUTE notify</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
AT NOCOMM * EXECUTE notify</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
AT FSD * EXECUTE forced-shutdown</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
AT NOPARENT * EXECUTE notify</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
AT SHUTDOWN * EXECUTE notify</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
AT ONLINE * CANCEL-TIMER shutdown</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
AT ONLINE * EXECUTE resume</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
AT ONBATT * START-TIMER shutdown 15</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
AT ONBATT * EXECUTE shutdown-warning</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
AT LOWBATT * START-TIMER shutdown</div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
AT LOWBATT * EXECUTE shutdown-warning</div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
BTW i finished the last TEST with everything hooked to my UPS and it seems that this line POWERDOWNFLAG /etc/killpower</div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
was what causing my UPS to shut itself down after a period of time</div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
i really don't know if deleting POWERDOWNFLAG was the right choice or not but if there is anything i can do to properly fix it please let me know<br>
<br>
<br>
<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Nut-upsuser <nut-upsuser-bounces+princemodey=hotmail.com@alioth-lists.debian.net> on behalf of nut-upsuser-request@alioth-lists.debian.net
<nut-upsuser-request@alioth-lists.debian.net><br>
<b>Sent:</b> Sunday, September 8, 2024 2:00 PM<br>
<b>To:</b> nut-upsuser@alioth-lists.debian.net <nut-upsuser@alioth-lists.debian.net><br>
<b>Subject:</b> Nut-upsuser Digest, Vol 231, Issue 4</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Send Nut-upsuser mailing list submissions to<br>
nut-upsuser@alioth-lists.debian.net<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser">
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
or, via email, send a message with subject or body 'help' to<br>
nut-upsuser-request@alioth-lists.debian.net<br>
<br>
You can reach the person managing the list at<br>
nut-upsuser-owner@alioth-lists.debian.net<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Nut-upsuser digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Nut-upsuser Digest, Vol 231, Issue 2 (Roger Price)<br>
2. Re: Nut-upsuser Digest, Vol 231, Issue 2 (Jim Klimov)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sat, 7 Sep 2024 17:16:40 +0200 (CEST)<br>
From: Roger Price <roger@rogerprice.org><br>
To: Mega DooOooM via Nut-upsuser <nut-upsuser@alioth-lists.debian.net><br>
Subject: Re: [Nut-upsuser] Nut-upsuser Digest, Vol 231, Issue 2<br>
Message-ID: <fa5f98c0-4330-35c0-6c17-571ba631ce8d@rogerprice.org><br>
Content-Type: text/plain; charset=US-ASCII; format=flowed<br>
<br>
On Sat, 7 Sep 2024, Mega DooOooM via Nut-upsuser wrote:<br>
<br>
> and this is UPSMON.CONF lines<br>
> <br>
> # This file is auto-generated by openmediavault (<a href="https://www.openmediavault.org">https://www.openmediavault.org</a>)<br>
> # WARNING: Do not edit this file, your changes will get lost.<br>
> MONITOR back-ups 1 monmaster 4L[p9<0Vi|Z>xKgK master<br>
> MINSUPPLIES 1<br>
> SHUTDOWNCMD "/sbin/shutdown -h +0"<br>
> NOTIFYCMD "/sbin/upssched"<br>
> POLLFREQ 5<br>
> POLLFREQALERT 5<br>
> HOSTSYNC 15<br>
> DEADTIME 555<br>
> POWERDOWNFLAG /etc/killpower<br>
> NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC<br>
> NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC<br>
> NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC<br>
> NOTIFYFLAG COMMOK SYSLOG+WALL+EXEC<br>
> NOTIFYFLAG COMMBAD SYSLOG+WALL+EXEC<br>
> NOTIFYFLAG SHUTDOWN SYSLOG+WALL+EXEC<br>
> NOTIFYFLAG REPLBATT SYSLOG+WALL+EXEC<br>
> NOTIFYFLAG NOCOMM SYSLOG+WALL+EXEC<br>
> NOTIFYFLAG FSD SYSLOG+WALL+EXEC<br>
> RBWARNTIME 43200<br>
> NOCOMMWARNTIME 300<br>
> FINALDELAY 5<br>
<br>
The EXEC flag with the NOTIFYFLAG says that when a NOTIFY event occurs, upsmon <br>
calls the program identified by NOTIFYCMD "/sbin/upssched". Does this program <br>
have a configuration file? Perhaps upssched.conf. Could we see it?<br>
<br>
Roger<br>
<br>
PS - You dont have to repeat all the previous messages in the Digest.<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sat, 7 Sep 2024 23:27:36 +0200<br>
From: Jim Klimov <jimklimov+nut@gmail.com><br>
To: Mega DooOooM <princemodey@hotmail.com><br>
Cc: nut-upsuser Mailing List <nut-upsuser@lists.alioth.debian.org><br>
Subject: Re: [Nut-upsuser] Nut-upsuser Digest, Vol 231, Issue 2<br>
Message-ID:<br>
<CAJYg8vKuKxRAj-vbjUExur8r=rCCoaHUD5oTFRg5tOkrOwNSRA@mail.gmail.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Cheers, jumping into the discussion late from some travels, sorry.<br>
<br>
In the original post, is the "Server PC" the OMV with NUT? Are any of your<br>
other machines running NUT (e.g. the `upsmon` client for shutdowns)?<br>
<br>
What I guess may be happening is:<br>
<br>
* OMV has the physical connection needed to monitor and command the UPS,<br>
and its `upsmon` has `MONITOR` for it as `primary` (ex-`master`);<br>
* by definition, such a "primary" instance in case of a power outage (and<br>
"critical state" of the UPS battery, definitions vary) is responsible for<br>
yelling "FSD" (Forced ShutDown) to all other "secondary" clients connected<br>
to tge same `upsd` data server (maybe none in your case), waiting for them<br>
all (if any) to disconnect - presumably meaning they are going down, and<br>
shuts down itself.<br>
* With the "killpower" file in place (created as part of "primary" FSD<br>
handling), and some OS shutdown integration, it would also tell all<br>
connected UPSes to power off (or power-cycle if power came back, aka "power<br>
race condition", to avoid your systems staying down indefinitely), if the<br>
UPS and its NUT driver agree how to support such behavior.<br>
<br>
This seems aligned with what you see in practice.<br>
<br>
One quick fix can be to change the OMV `MONITOR` mode to `secondary`<br>
(ex-`slave`) so only it shuts down when power goes "bad".<br>
<br>
Nuanced criteria for the latter, like time spent on battery, can be set in<br>
`upssched` (as asked about by Roger). Default "bad"ness is defined by UPS<br>
itself claiming a low battery state, maybe also by remaining percentage<br>
(depends on driver and device).<br>
<br>
Hope this helps,<br>
Jim Klimov<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240907/07616461/attachment-0001.htm">http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240907/07616461/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
Nut-upsuser@alioth-lists.debian.net<br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
<br>
<br>
------------------------------<br>
<br>
End of Nut-upsuser Digest, Vol 231, Issue 4<br>
*******************************************<br>
</div>
</span></font></div>
</body>
</html>