search for: upsscheds

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,

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, Thanks Jim! Here is more system information from the commands you mentioned. Kari root at fricka:~# lsof -p 1716171 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1002/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME upssched 1716171 root cwd DIR 8,2 4096 2 /

Hi, Thanks Jim! Here is more system information from the commands you mentioned. Kari root at fricka:~# lsof -p 1716171 lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1002/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME upssched 1716171 root cwd DIR 8,2 4096 2 /

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

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

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

...ents/upssched.c --- nut-2.7.2/clients/upssched.c.racecondition 2014-02-19 20:31:10.000000000 +0100 +++ nut-2.7.2/clients/upssched.c 2019-03-26 15:30:19.972184228 +0100 @@ -648,8 +648,10 @@ static int check_parent(const char *cmd, /* we didn't get the lock - must be two upsscheds running */ - /* blow this away in case we crashed before */ - unlink(lockfn); + if (tries >= MAX_TRIES-1) { + /* blow this away in case we crashed before */ + unlink(lockfn); + } /* give t...

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

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

So, got some good news: I hear(*) I managed to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT

So, got some good news: I hear(*) I managed to reproduce the problem with current NUT master and an adapted copy of your posted configs and script :D Experimental debugging now sounds possible. (*) PC under the desk wails with all its cooling fans as soon as I started the client which spawned a daemon and itself had exited: $ UPSNAME=heartbeat at localhost NOTIFYTYPE=ONBATT

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

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"

Gents, Thanks, yes definitely a permissions problem. Roger pointed me in the correct direction with the command to add logging for the script. I have the shutdown working now but need to tighten up the permissions. Not too sure where to start with assigning the correct permissions. Cheers, James > Date: Mon, 27 Apr 2015 21:25:45 +0100 > From: neil at dana.org.uk > To: nut-upsuser at

NUT 2.8.01 When I pull the USB cable from the UPS, I get two notifications of the nocomm-timer expired. The first notification is in the proper sequence, the second notification occurs after 'commok' occurs. Seems somehow that upssched-cmd is getting a second nocomm-timer expired delayed. Dan -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Thu, 28 Mar 2024, Dan Grostick via Nut-upsuser wrote: > All three systems have a heartbeat-timer failure approximately 15 minutes > after starting NUT. No subsequent failures. Any ideas on what is happening? I've seen the timers: heartbeat.conf has two 300 sec timers, upssched.cmd looks like what is often called upssched.conf and has a 660 sec timer. So it looks as if the

After launching the command several times, with debug (posted by new code in a new branch for the investigation) confirming that the same daemon handles operations from the new client instances, its strace now has numerous FDs to report after select() - so I guess it is a problem of detecting an exit of the counterpart. 0.000000 [D2] parse_at: is 'heartbeat at localhost' in AT