<html><head></head><body><div dir="ltr">Hi,<div><br></div><div>I tried your suggestions on another Proxmox environment with the following ups.conf:</div><div><br></div><div><font face="monospace"># Wait 10 seconds for the driver to finish starting.<br>maxstartdelay = 10<br><br># Try 3 times to start the driver, before giving up.<br>maxretry = 3<br><br># Wait 5 seconds between attempts to start the driver.<br>retrydelay = 5<br><br># Poll the ups every 5 seconds<br>pollinterval = 5<br><br><br>[pve1]<br> # Cyber Power Systems, Inc<br> driver = usbhid-ups<br> port = auto<br> desc = "Cyber Power CP1500 AVR UPS"<br> vendorid = 0764<br> productid = 0501<br> # if the charge is less than 75 percent trigger a LB status<br> override.battery.charge.low = 75<br> # Some drivers reset battery.charge.low to the default value. lowbatt addresses this</font></div><div><font face="monospace"> # See chapter 2.7 in <a href="https://rogerprice.org/NUT/ConfigExamples.A5.pdf">https://rogerprice.org/NUT/ConfigExamples.A5.pdf</a><br> lowbatt = 75<br> # if the remaining charge is less than 1200s (20 minutes) trigger a low battery status<br> override.battery.runtime.low = 1200<br> # Wait 10 minutes before attempting to restart the ups load after a power cut<br> ondelay = 600<br> # wait 5 minutes for ups to power off<br> override.ups.delay.shutdown = 300<br><font color="#ff0000"> # Could offdelay act as an ovverride for override.ups.delay.shutdown?</font><br> offdelay = 300<br> # serial = 0<br></font></div><div><br></div><div>Is the comment about offdelay (in red) correct / can this line be eliminated?. </div><div><br></div><div>When I unplugged the power cord off the ups. I got an email (2 actually - not a problem). and a prompt on the console.</div><div><br></div><div>On the console I got another prompt that comes up when a shutdown command is issued. I was concerned because the 5 minute offdelay (or override.up.delay.shutdown) were not reflected in this prompt and the VMs and containers would not have neatly shut down. In fact the server kept running while Proxmox started shutting down the the guests.</div><div><br></div><div>After that (I don't have accurate timing as yet), the UPS shut down. </div><div><br></div><div>Can the UPS automatically come online one the ondelay passes -- I presume this can vary with the UPS brand and NUT driver.</div><div><br></div><div>----------------------------------------------</div><div><br></div><div>My goal is to tell a story of how Proxmox with Windows Guests can be configured with NUT so that if there is a power failure. I hope to design this such that others can add alternative methods and update HowTo modules for each step.</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div>I feel I am at the tail end of a long long learning curve and would like to document the story of how one should go abo</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, 2 Jun 2024 at 08:14, Roger Price <<a href="mailto:roger_at_rogerprice.org_chribonn@duck.com" target="_blank">roger_at_rogerprice.org_chribonn@duck.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sat, 1 Jun 2024, Alan via Nut-upsuser wrote:<br>
<br>
> root@proxmox-01:~# cat nano /etc/nut/ups.conf<br>
<br>
If you send us hundreds of lines of comments it makes your post difficult to <br>
understand. Could you trim out the comments with for example<br>
<br>
cat /etc/nut/ups.conf | grep -v "#"<br>
<br>
which would show us the following, which is what we need to see.<br>
<br>
> maxretry = 3<br>
> <br>
> offdelay = 120<br>
> ondelay = 240<br>
> <br>
> [pve1]<br>
> driver = "usbhid-ups"<br>
> port = "auto"<br>
> vendorid = "06DA"<br>
> productid = "FFFF"<br>
> desc = "Phoenixtec Power Co., Ltd Innova Unity"<br>
> serial = "CPANM2436540037"<br>
> override.battery.charge.low = 70<br>
> override.battery.runtime.low = 2500<br>
> # wait 5 minutes for ups to power off<br>
> override.ups.delay.shutdown = 300<br>
<br>
I don't see the line<br>
<br>
lowbatt = 70<br>
<br>
which you need to make a permanent change to the value. If you use the <br>
"override", the driver will restore the default. See chapter 2.7 in <br>
<a href="https://rogerprice.org/NUT/ConfigExamples.A5.pdf" rel="noreferrer" target="_blank">https://rogerprice.org/NUT/ConfigExamples.A5.pdf</a><br>
<br>
Try re-running your test with lowbatt = 70 . Roger_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote></div>
</body></html>