similar to: upssched. Again.

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

ut 10. 3. 2020 o 16:34 Roger Price <roger at rogerprice.org> napísal(a): > > 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

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

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...

On 9/16/08 3:35 PM, "Arjen de Korte" <nut+users at de-korte.org> wrote: > Citeren tarbeite <tarbeite at fit.edu>: > >> Running opensuse 11 with two ups that can be seen via web interface and post >> messages on the console. > > Please post the contents of /etc/ups/upssched.conf here. Also make > sure that the directory mentioned in PIPEFN and

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

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

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

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>

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

On Tue, 21 Mar 2017, Arnaud Quette wrote: > Hi Roger, > > reviving this discussion, since we have a Github ticket for 2.7.5: > https://github.com/networkupstools/nut/issues/293 ... > I've made some additions to clarify things on the timer, and complete the script: > https://github.com/networkupstools/nut/compare/upssched-doc?expand=1 Hi Arnaud, Your change to the

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,

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

I've recently moved from installing NUT from source to installing NUT from the FreeBSD package (FreeBSD 9.1). One would think that I might have learned not to change anything, but I made the change. And here is my tale of woe..... My first question is: is it possible to simulate a "UPS is on battery" state? Some background: UPS comm port is connected to and monitored by

Now I have this in /etc/nut/upsmon.conf (my QNAP NAS wants admin and 123456 or not working) RUN_AS_USER root MONITOR qnapups at localhost 1 admin 123456 master MONITOR qnapups at 192.168.222.252 3493 admin 123456 slave MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+EXEC

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

I have only RS-232 on the box (meanwhile, it was manufactured on march of 2011) Here is my configs: nut.conf: * * MODE = netserver ups.conf: * * [KIN1500] driver = powercom port = notUsed desc = "Powercom KING PRO KIN-1500AP RM" upsd.conf: * * LISTEN 192.168.1.2 3493 upsd.users: * * [monuser] password = xxxxxxxx upsmon master

ok, this function really worked? i have a linux Fedora 20 system, i install from rpm in version 2.6.2 and i this function not execute. Then i delete the rpm packet and all configuration files and compile latest stable 2.7.2 version with usb driver. ok, i first load ups driver: * /usr/local/ups/sbin/upsdrvctl -u root start* next i started */usr/local/ups/sbin/upsd* and next*