similar to: Timers fireing too early

Hi, I'm having problems to configure upssched in order to notify me only when the disconnection exceeds the 30 seconds. Now, I'm getting a mail if it is disconnected just for a second, or even worse, when I got low tension. So, mail notifications are well configured, I guess... I think the problem is in upssched. I'm new to this, so it could be a stupid thing that I'm missing...

Hi everyone, new to the list but a long time nut user. I've tried a couple of times to set up a timer to avoid getting annoying messages when the system goes on battery for only a few seconds. in uppsched.conf I added this at the bottom: AT ONBATT * START-TIMER onbattwarn 60 AT ONLINE * CANCEL-TIMER onbattwarn What am I missing? it still doesn't wait before alerting me.

Am 14.10.20 um 16:19 schrieb Rowland penny via samba: > On 14/10/2020 15:07, Markus Jansen via samba wrote: >> Am 14.10.20 um 08:31 schrieb Nico Kadel-Garcia via samba: >>> On Tue, Oct 13, 2020 at 10:30 AM Rowland penny via samba >>> <samba at lists.samba.org> wrote: >>>> On 13/10/2020 15:01, Markus Jansen via samba wrote: >>>>> Thank you

Hi Roger, I get: Apr 27 20:50:05 unifi upsmon[1022]: UPS ups on batteryApr 27 20:50:05 unifi upssched[2688]: Timer daemon startedApr 27 20:50:06 unifi upssched[2688]: New timer: onbatt (20 seconds)Apr 27 20:50:26 unifi upssched[2688]: Event: onbattApr 27 20:50:26 unifi upssched[2688]: exec_cmd(/sbin/upssched-cmd.sh onbatt) returned 126Apr 27 20:50:41 unifi upssched[2688]: Timer queue empty,

Hello, I'm using nut with my MG Ellipse on serial port. No problem since one year. Two days ago, I wanted to add a phone alert through my asterisk box when power is down. Since then, upssched doesn't make his job anymore. here is the "syslog" I get when the power cord is unplugged : > > May 9 11:39:34 serveur upsmon[6411]: UPS ellipse@localhost on battery > May 9

Roger, I did and it didnt work. Hence why I was trying to run just the shell script manually. I am not sure if this works though with the timer defined in it? Cheers, James Date: Mon, 27 Apr 2015 15:03:44 +0200 From: roger at rogerprice.org To: nut-upsuser at lists.alioth.debian.org Subject: Re: [Nut-upsuser] upssched setup On Mon, 27 Apr 2015, James Hammond wrote: > I am unable to get

Hi, I am unable to get upssched working correctly as my UPS calls low battery too late and there is no way to change it. I am running Nut 2.7.3 on Ubuntu 14.04 I have made this script, called /sbin/upssched-cmd.sh #!/bin/sh case $1 in onbatt) /sbin/upsmon -c fsd;; *) echo "shutdown implemented";; esac I am trying to run the script manually to break down my issues. All that

On Fri, 9 Jun 2017, Robbie van der Walle wrote: > ... and also still open is the notification on the Mac. If notify-send is available on the Mac, then perhaps this will work: In upsmon.conf on the Mac you need NOTIFYCMD /usr/sbin/upssched (or wherever this goes on a Mac) NOTIFYFLAG ONBATT SYSLOG+EXEC In upssched.conf you need CMDSCRIPT /usr/sbin/upssched-cmd (or wherever this

Hi, I have been running nut successfully for a long time with my Debian 11 server. I upgraded my server to Debian 12 today, which upgraded nut also from 2.7.4-13 to 2.8.0-7. I noticed that after upgrade there was a upssched process running and taking 100% cpu time. I checked if there were any changes to configuration file formats with nut upgrade and only differences I noticed were a terminology

Is there a script to check that the automatic shutdown and logging configuration is set right? I had hoped I set it up right to at least log when it goes and off battery but I guess I missed something. /etc/nut# grep upssched /var/log/syslog Apr 3 12:31:06 gw upssched[12732]: Timer daemon started Apr 3 12:31:06 gw upssched[12732]: New timer: onbatt (30 seconds) Apr 3 12:31:36 gw

On Jan 21, 2014, at 3:16 AM, Rafa? Oleszek wrote: > I would like to mention that MINSUPPLIES manipulation doesn't work. My nut version is : 2.2.2-4 (RHEL 5) What do your configuration files look like? Setting MINSUPPLIES to 2 should work. You can run upsmon with a debug level of 3 or greater, and it will print the current and minimum "power value", which is what determines

An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20120104/34be491b/attachment.html>

So, a while back I got around to ordering replacement batteries for my CyberPower PR3000LCDRTXL2U. When they arrived, I went to swap them in. I was horrified at the flimsiness of CyberPower's battery "trays". I've seen heavier gauge plastic on "blister" packages in the store. I ALSO discovered that the expansion unit had been shipped to me with one of its two

Ok, I am running NUT in dummy mode. I have added a new ups in ups.conf [dummy] driver = dummy-ups port = upsc.dev desc = "dummy ups for testing purposes" upsc.dev has been generated by exporting the Elit configuration. I have added the monitor line in upsmon.conf and the "exec" flags (all the events) MONITOR dummy at artu 1 user pass master SHUTDOWNCMD

Dear list, Can't make upssched notify me on event occured. OS: Debian, 2.6.26-1-amd64 Nut: 2.4.3-1.1squeeze1 UPS: Ippon Smart Winner 3000 connected via COM On event ( plug out the cord from UPS ) upsmon detect's status change to OB and gives WALL and syslog notify, but no script starting. In syslog no errors and no upssched process occured, just upsmon. There're no PIPE and LOCK

Hi, I have problem with upssched on windows. Upssched is not executed. I have 2 scripts, 1 for notification in upsmon and second for scheduling in upssched. Monitoring is working fine, script write to log. I'm using binary windows installer 2.6.5-6 from NUT. Here are my configs: --- nut.conf MODE=netclient --- upsmon.conf MONITOR ups_1000 at 192.168.3.95 1 <user> <password> slave

Hi! Some systems I have take some time to shut down, so I would like them to shut down if the UPS have been on battery for 2 minutes. Internet has told me that SHUTDOWNCMD ?/sbin/shutdown -h +0? in /etc/nut/upsmon.conf will execute when the UPS is both OB (on battery) and LB (Low battery). Like in wiki.ipfire.org - Detailed NUT Configuration<https://wiki.ipfire.org/addons/nut/detailed>

I've not been able to connect to my ups using NUT 2.7.4 or NUT 2.8.0. 2.7.4 was installed as a package, 2.8.O was compiled from source. I've messed with permissons, everything is root:root and has the approprate read/execute permissons. I've tried two differnt UPS(es) APC & CyperPower. I'm running PI OS (Raspbian) on a Raspberry Pi3 model B. The port 3493 is open (UFW). I can

Bonjour je n?arrive pas ? configurer convenablement NUT pour qu?il m?adresse des SMS en cas de coupure de courant. C?est important pour moi car dans ma maison les coupures sont tr?s fr?quentes. Voici ma configuration : ****************************************************************** 1/ dans /etc/nut/upsmon.conf MONITOR eaton at localhost 1 admin motdepasse master MINSUPPLIES 1 SHUTDOWNCMD

Hi, I'm attempting to use the UPS network tools. I'm sure I got the configurations worked out as I get notified when the ups goes on battery and back online. I am having problems with upssched. I have the following in my upssched.conf: CMDSCRIPT /usr/local/ups/sbin/upssched-cmd AT ONBATT * EXECUTE onbatt The problem I have is that is seems like the script in CMDSCRIPT never gets