I'm not sure I understand your question. The UPS was running for more than
15 minutes before it went below the battery.charge.low: of 70.
Below is my /etc/nut/nut.conf.
My goal is that when the UPS report a battery.charge.low of < 70 (or, if
possible has been running for 5 minutes) it starts
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
On Sat, 1 Jun 2024, chrib...@duck.com wrote:
Yes. I received both the email and the update from the console.
>From your email, I understand that the expected behaviour should have been
that the os should have started the shutdown process.
NUT requires that 3 os services be running. If you
Yes. I received both the email and the update from the console.
>From your email, I understand that the expected behaviour should have been
that the os should have started the shutdown process.
Is there a log I could look at (Nut or Debian) to understand what is
happening?
On Sat, 1 Jun 2024 at
On Sat, 1 Jun 2024, Alan via Nut-upsuser wrote:
I modified ./etc/nut/upssched-cmd and modified the script to send an email
(happy to share).
NUT wrote a message to the console and I received an email to inform me that
the UPS was on battery.
Have you also specified an e-mail when power is
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
