Hi,
I tried your suggestions on another Proxmox environment with the following
ups.conf:
# Wait 10 seconds for the driver to finish starting.
maxstartdelay = 10
# Try 3 times to start the driver, before giving up.
maxretry = 3
# Wait 5 seconds between attempts to start the driver.
retrydelay = 5
# Poll the ups every 5 seconds
pollinterval = 5
[pve1]
# Cyber Power Systems, Inc
driver = usbhid-ups
port = auto
desc = "Cyber Power CP1500 AVR UPS"
vendorid = 0764
productid = 0501
# if the charge is less than 75 percent trigger a LB status
override.battery.charge.low = 75
# Some drivers reset battery.charge.low to the default value. lowbatt
addresses this
# See chapter 2.7 in https://rogerprice.org/NUT/ConfigExamples.A5.pdf
lowbatt = 75
# if the remaining charge is less than 1200s (20 minutes) trigger a low
battery status
override.battery.runtime.low = 1200
# Wait 10 minutes before attempting to restart the ups load after a power
cut
ondelay = 600
# wait 5 minutes for ups to power off
override.ups.delay.shutdown = 300
# Could offdelay act as an ovverride for override.ups.delay.shutdown?
offdelay = 300
# serial = 0
Is the comment about offdelay (in red) correct / can this line be
eliminated?.
When I unplugged the power cord off the ups. I got an email (2 actually -
not a problem). and a prompt on the console.
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.
After that (I don't have accurate timing as yet), the UPS shut down.
Can the UPS automatically come online one the ondelay passes -- I presume
this can vary with the UPS brand and NUT driver.
----------------------------------------------
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.
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
On Sun, 2 Jun 2024 at 08:14, Roger Price <
roger_at_rogerprice.org_chribonn at duck.com> wrote:
> On Sat, 1 Jun 2024, Alan via Nut-upsuser wrote:
>
> > root at proxmox-01:~# cat nano /etc/nut/ups.conf
>
> If you send us hundreds of lines of comments it makes your post difficult
> to
> understand. Could you trim out the comments with for example
>
> cat /etc/nut/ups.conf | grep -v "#"
>
> which would show us the following, which is what we need to see.
>
> > maxretry = 3
> >
> > offdelay = 120
> > ondelay = 240
> >
> > [pve1]
> > driver = "usbhid-ups"
> > port = "auto"
> > vendorid = "06DA"
> > productid = "FFFF"
> > desc = "Phoenixtec Power Co., Ltd Innova Unity"
> > serial = "CPANM2436540037"
> > override.battery.charge.low = 70
> > override.battery.runtime.low = 2500
> > # wait 5 minutes for ups to power off
> > override.ups.delay.shutdown = 300
>
> I don't see the line
>
> lowbatt = 70
>
> which you need to make a permanent change to the value. If you use the
> "override", the driver will restore the default. See chapter 2.7
in
> https://rogerprice.org/NUT/ConfigExamples.A5.pdf
>
> Try re-running your test with lowbatt = 70 .
> Roger_______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240602/2ec99fda/attachment.htm>