similar to: upssched not execute triggers - Fedora 20 and nut 2.7.2

Hi, I want to test the events off my UPS. I define In upsmon.conf: RUN_AS_USER root NOTIFYCMD /sbin/upssched NOTIFYMSG ONLINE "UPS %s on line power" NOTIFYMSG ONBATT "UPS %s on battery" NOTIFYMSG LOWBATT "UPS %s battery is low" # NOTIFYMSG FSD "UPS %s: forced shutdown in progress" NOTIFYMSG COMMOK "Communications with UPS %s established"

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

There's supposedly another way with a custom upsmon.conf: NOTIFYMSG type message upsmon comes with a set of stock messages for various events. You can change them if you like. NOTIFYMSG ONLINE "UPS %s is getting line power" NOTIFYMSG ONBATT "Someone pulled the plug on %s" Note that %s is replaced with the identifier of the UPS in question. The message must be one

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,

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

Hi, I cant seem to get my upssched to get called by upsmon. Upsmon -c fsd just shuts down without the message I set or the one in upssched-cmd /etc/ups/upsmon.conf: MONITOR ups6 at localhost 1 <user> <pass> master MONITOR ups8 at localhost 1 <user> <pass> master SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /usr/sbin/upssched NOTIFYMSG

Where syslog output ends up is an OS specific question and depends upon the configuration of the system logger in use. On most systems the logging information will be found in /var/log. On most Linux systems, the default system log is /var/log/messages. Denny > On Sep 20, 2018, at 13:30, Ito-Cole, Kaeny (Student) <Kaeny.Ito-Cole.stu at gtri.gatech.edu> wrote: > > First

Ah yes sorry I forgot to specify I am on CentOS 7 and the newest NUT for that is 2.7.2 On 9/21/18, 9:04 AM, "Denny Page" <denny at cococafe.com> wrote: Where syslog output ends up is an OS specific question and depends upon the configuration of the system logger in use. On most systems the logging information will be found in /var/log. On most Linux systems, the

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

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

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

On Fri, 9 Jun 2017, Robbie van der Walle wrote: > # NOTIFYMSG - change messages sent by upsmon when certain events occur > # > # You can change the default messages to something else if you like. > # > # NOTIFYMSG <notify type> "message" > # > # NOTIFYMSG ONLINE "UPS %s on line power" > # NOTIFYMSG ONBATT "UPS %s on battery" > #

On Tue, 27 Oct 2015, George Anchev wrote: > Yes, that was the power off test. However the upssched-cmd script gave > absolutely no signs of activity. Even it's logger lines don't show up in > journalctl. No any permission error messages - nothing. Only the 2 > messages from upsmon - on battery and then on line power. > > Here is the nut-report: >

Charles, This is how I have the upsmon.conf set up. ?The only time I get a message is if the?NUT Monitor gui is running. ?I open LXterminal, pull the wall plug, and I get no messagesin the terminal. ?MONITOR Asium_p700 at localhost 1 upsmon jsamcr master?MINSUPPLIES 1?SHUTDOWNCMD "/sbin/shutdown -h +0"?NOTIFYCMD /sbin/upssched?POLLFREQ 5?POLLFREQALERT 5?HOSTSYNC 15?DEADTIME

hello, i've got a problem with the notifycmd here is a part of my upsmon.conf : NOTIFYCMD /usr/local/ups/bin/nut_notify NOTIFYMSG ONLINE "UPS %s is getting line power" NOTIFYMSG ONBATT "UPS %s is on battery" NOTIFYMSG REPLBATT "The UPS %s battery is bad and needs to be replaced" NOTIFYMSG LOWBATT "UPS %s is being shutdown by the master" NOTIFYMSG FSD

Hello guys Yesterday i started do configure my Mustek Powermust650 with nut using the megatec_usb driver. Everything works fine except for the mailing when something happens. My upsmon looks like this: MONITOR powermust650 at localhost 1 local controller master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /root/upsmailer POLLFREQ 10 POLLFREQALERT 5 HOSTSYNC 15

UPSmon.py --------- I have been experimenting with a Python3 re-implementation of upsmon, upssched and upssched-cmd. This is currently in use on openSUSE and Debian boxes. It provides a much richer "language" for UPS management. For example, the key part of the well known "warn on [OB], shutdown on [LB]" approach is written as # Warnings when on-battery, wait for low

Hello, I set up a FreeBSD 8.2 system with nut 2.6.1 and a Powerware 5115 connected by RS-232. I expected this setup to shut down before running out of battery power, but I either missed some important configuration or something else went wrong: The syslog says: Jan 9 05:03:42 b1 upsmon[67752]: UPS upsb1 at localhost on battery Jan 9 05:04:42 b1 upsmon[67752]: UPS upsb1 at localhost on line

MASTER SYSTEM nut.conf MODE=netserver ups.conf [TOPAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309002707" desc = "TOPAPC" [MIDAPC] driver = usbhid-ups port = auto pollonly serial = "IS1309001233" desc = "MIDAPC" [BOTAPC] driver = usbhid-ups port = auto