Thank Charles. I've bookmarked this and will try to experiment a bit.
On Mon, 3 Jun 2024, 04:33 Charles Lepple via Nut-upsuser, <
nut-upsuser_at_alioth-lists.debian.net_chrib...@duck.com> wrote:
> On Jun 2, 2024, at 12:14 PM, Roger Price wrote:
> >
> >> Is the comment about offdelay (in red)
On Jun 2, 2024, at 12:14 PM, Roger Price wrote:
>
>> Is the comment about offdelay (in red) correct / can this line be
>> eliminated?.
>
> My understanding is "yes", but others may have deeper knowledge.
I don't have a ton of direct experience with this post-v2.7.4, but someone else
wrote
On Sun, 2 Jun 2024, chrib...@duck.com wrote:
# if the charge is less than 75 percent trigger a LB status
override.battery.charge.low = 75
# if the remaining charge is less than 1200s (20 minutes) trigger a low
battery status
override.battery.runtime.low = 1200
# wait 5 minutes for
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 =
My bad. I'll check it out.
On Sun, 2 Jun 2024 at 08:14, Roger Price <
roger_at_rogerprice.org_chrib...@duck.com> wrote:
> On Sat, 1 Jun 2024, Alan via Nut-upsuser wrote:
>
> > root@proxmox-01:~# cat nano /etc/nut/ups.conf
>
> If you send us hundreds of lines of comments it makes your post
On Sat, 1 Jun 2024, Alan via Nut-upsuser wrote:
root@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
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
12 matches
Mail list logo