similar to: FW: Setup of upssched on opensuse 11 - examined pipefn ad lockfm

Hi all I?m not sure if this is the right place to post but I?m at wits end. So here we go. Running opensuse 11 with two ups that can be seen via web interface and post messages on the console. My issue lies in trying to get the upssched and upsmon to work correctly. Currently I have the exec flags denoted in the upsmon and ?NOTIFYCMD /usr/sbin/upssched? is specified as the NOTIFYCMD flag as

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, 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"

On Mon, 3 Jul 2017, Andrea de Lutti wrote: > MONITOR dummy at artu 1 user pass master > SHUTDOWNCMD "/sbin/shutdown -h +0" > NOTIFYCMD /usr/local/bin/upssched-script Hi, As far as I can see, what you are getting in syslog corresponds correctly to what you have specified. You have specified that upsmon is to call upssched-script _directly_. This means that the argument to

Hello NUT Team! I am testing the early shutdowns in NUT 2.6.5-1 package for Windows (Windows 7 x64). My configuration files: upsmon.conf RUN_AS_USER upsmon MONITOR upsa at 192.168.10.200 1 upsmon pass master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD "upssched.exe" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG

Hi everyone, Here I am with my second attempt to persuade upssched to do things; for some reasons it just won't! Or if it runs, it never runs the script. OK, the story first: 2.0.3 (conveniently comes as RPMs by default on FC6) running on FC6; APC Smart-UPS 750 via serial connection all working fine. Here are the main files: /etc/sysconfig/ups SERVER=yes MODEL=apcsmart DEVICE=/dev/ttyS0

Hi Volker, I forward your request to the user list since I don't currently have much time to process it. quickly testing 2.4.1, I wasn't able to reproduce it. a question: was it working with the exact same context/config with 2.2.2? cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops Network UPS Tools (NUT) Project Leader -

I have a Raspberry PI that I have connected to a Deltec UPS via serial (upscode2 driver). I had an older version of Rasbian running. The nut configuration worked fine but I had mail issues I couldn't resolve when gmail changed how it handled MTAs. Plus it was running an old version of Deb that is no longer supported. It was broken enough I could not upgrade to a never version so I started from

Group: The Background: I maintain the network hardware for a county government building that is un- occupied except for weekday dayshift. The building is located in an older section of town and the electric service has components that are nearing their 100 year lifetime. The building has UPS for all computer and network hardware and an autostart generator that starts when utilitity service

Hello List, Any suggestions to solve the following would be most appreciated. Setup: Active/Passive Two Node Cluster. Two UPSes (APC Smart-UPS 1500 C) with USB communication cables cross connected (ie UPS-webserver1 monitored by webserver2, and vice versa) to allow for stonith/fencing OS OpenSuse Leap 42.2 NUT version 2.7.1-2.41-x86_64 Fencing agent: external/nut Problem: When power fails to a

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

A couple of different issues with the reporting script. First the password masking is not working as intended: I have three different passwords in my ups.users file and only the last one is masked. Here's the first part of the resulting report where I've replaced the unmasked passwords with <PASSWORD-n>. NUT configuration 2019-07-14 16:58:15 UTC ###########

On Mon, 15 May 2017, Dinow Hsieh wrote: > ==> I have tried this command "upsdrvctl shutdown" as below results (However the UPS still sustain the power) > > ??? Network UPS Tools - UPS driver controller 2.7.1 > ??? Network UPS Tools - Generic HID driver 0.38 (2.7.1) > ??? USB communication driver 0.32 > ??? Using subdriver : PowerCOM HID 0.4 > ??? Initiating UPS

Hi, I tried to do the minimum configuration for Nut. When I stop the on-line power i get terminal message that I'm on battery power and when I plug on-line power back in I get a message that I'm back to on-line power. So things are working/communicating. What I want is: if it's been on battery power for over 5 minutes the PC will shutdown. If powers comes on-line again before the 5

Hello, Got this UPS (connected via USB). I've checked on the nut website, driver is usbhid-ups When I "upsdrvctl start", it says : Network UPS Tools - UPS driver controller 2.6.5-Unversioned directory Network UPS Tools - Generic HID driver 0.37 (2.6.5-Unversioned directory) USB communication driver 0.31 No matching HID UPS found Driver failed to start (exit status=1) Here is

Hi, The exec is returning 126 - "Command invoked cannot execute. A permission or command not executable problem.". Are you sure that the script is executable by the user running NUT? Do you have SELinux enabled? Regards, Neil. On 27/04/15 20:55, James Hammond wrote: > Hi Roger, > > I get: > > Apr 27 20:50:05 unifi upsmon[1022]: UPS ups on battery > Apr 27

On Sat, 8 Jun 2019, Joe Gervasio wrote: > ETC/UPSMON.CONF > > NOTIFYFLAG LOWBATT EXEC+SYSLOG+WALL > > ETC/UPSSCHED.CONF > > CMDSCRIPT /opt/local/bin/upssched-cmd > PIPEFN /opt/local/var/db/ups/upssched/upssched.pipe > LOCKFN /opt/local/var/db/ups/upssched/upssched.lock > AT ONBATT ups at xxx.xxx.xxx.xxx EXECUTE on-battery > AT ONLINE ups at

On Tue, 10 Mar 2020, Radoslav Chovan wrote: > 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. > --- upsmon.conf > MONITOR ups_1000 at 192.168.3.95 1 <user>

If you look closer at: > pi at nutpi:~ $ sudo ls -alt /home/nutmon > total 32 > -rw------- 1 nutmon nutmon 172 Jan 26 12:32 .bash_history > drwxrwx--- 2 nutmon nutmon 4096 Jan 26 12:32 upssched there is a d in the first position of the upssched permissions showing this is a directory. This is the directory location for PIPEFN and LOCKFN as defined in

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