Thinking of it, one purpose of upssched is to delay reaction to short-lived
flukes (e.g. if we go on battery for 20 seconds and set a delay for 30, if
we're back on line within that time frame, it is ok to go on living).
I wonder if your UPS went under 70% and you aborted the experiment too
early (compared to the delay you had set, possibly with a margin for the
frequency of UPS polling rate and regular `upsmon` interactions with `upsd`
- typically 5 to 30 sec each)?..
Jim
On Sat, Jun 1, 2024 at 1:32?PM Alan via Nut-upsuser <
nut-upsuser at alioth-lists.debian.net> wrote:
> Hi,
>
> A while back I set up a NUT server on a debian machine (Proxmox). I
> followed the guide at https://wiki.debian.org/Exim4Gmail so that I would
> receive email notifications and verified that emails work.
>
> I modified .*/etc/nut/upssched-cmd* and modified the script to send an
> email (happy to share).
>
> I then wanted to test the solution so I unplugged the UPS.
> NUT wrote a message to the console and I received an email to inform me
> that the UPS was on battery.
>
> I had configured the battery.charge.low: 70 and battery.runtime.low: 2500.
> My thought was when one of these conditions are met the server would bring
> down the guests and shut itself down. The UPS battery.charge went under 70
> but nothing happened. Below is the output from upsc and what happened when
> I plugged the power back into the ups.
>
> upsc pve1 at localhost
> Init SSL without certificate database
> battery.charge: 63
> battery.charge.low: 70
> battery.runtime: 3133
> battery.runtime.low: 2500
> battery.type: PbAc
> battery.voltage: 36.80
> battery.voltage.nominal: 36.00
> device.mfr: PHOENIXTEC
> device.model: Innova Unity
> device.serial: CPANM2436540037
> device.type: ups
> driver.name: usbhid-ups
> driver.parameter.pollfreq: 30
> driver.parameter.pollinterval: 2
> driver.parameter.port: auto
> driver.parameter.productid: FFFF
> driver.parameter.serial: CPANM2436540037
> driver.parameter.synchronous: auto
> driver.parameter.vendorid: 06DA
> driver.version: 2.8.0
> driver.version.data: Phoenixtec/Liebert HID 0.41
> driver.version.internal: 0.47
> driver.version.usb: libusb-1.0.26 (API: 0x1000109)
> output.frequency: 50.00
> output.voltage: 229.6
> ups.delay.shutdown: 300
> ups.load: 13
> ups.mfr: PHOENIXTEC
> ups.model: Innova Unity
> ups.productid: ffff
> ups.serial: CPANM2436540037
> ups.status: OB DISCHRG
> ups.vendorid: 06da
>
> *<< UPS plugged back in >>*
>
> Broadcast message from root at proxmox-01 (somewhere) (Sat Jun 1 12:36:17
> 2024):
>
>
> UPS pve1 at localhost on line power
>
> How can I diagnose / resolve this?
>
> Thanks
> Alan
>
>
> _______________________________________________
> 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/20240601/3f533c18/attachment-0001.htm>