similar to: upssched does not start the script when timer triggers

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,

Hi *, is anybody using a bluetooth headset with some success?? If yes, which stuff is used (usb dongle and BT headset)? (I would like to : 1. be able to receive calls, if possible to answer acalls with the headset. 2. be able to place call, but this seem lot more difficult.) Laurent

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

hello, at first I'm sorry my english isn't perfect but I tried to be clear I work with mandriva 2007 and with nut 2.0.1 installed with urpmi my UPS is a MGE Evolution 2200 connected with RS232 in my ups.conf I try to use mge-utalk driver and also mge-shut both seem to work I don't really known which I add to use It's the first point. As I saw on web site, I add maxage 25 in

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

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*

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

Hi, the last commit to upssched.c (Merge Coverity branch, r3555) broke upssched with commands that have a second argument. If a command with a second argument is used, "enc" in line 697 is not an empty buffer and snprintfcat() just appends some stuff, i.e. the following command CANCEL onbatt online becomes onlineCANCEL "onbatt" "online" and is then sent to 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

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

Ah! So I can detect the source UPS in the upssched.conf and pass it as a distinct event to the shell script. That sounds like an excellent approach. Thanks! GMH From: O'Shaughnessy, Mike [mailto:Mike.OShaughnessy at gd-ms.com] Sent: Tuesday, October 31, 2017 12:46 PM To: Garrett Michael Hayes <Garrett at VerbalImaging.com>; nut-upsuser at lists.alioth.debian.org Subject: RE: Email

Hi all, I've not been able to find the answer to my timer problem in the faq or the archives. (or google) Basically, I can't get timers to fire. They fire ignoring the timer value, as if the timer was set to 0. I'm using the OpenFiler distribution, patched to the latest and greatest. upsmon 2.2.2 When I pull the power plug, I see the text "Im In Battery" instantly, instead

I would like to add a sentence to the man page for upssched.conf. After the sentence "Note that any AT that matches both the notifytype and the upsname for the current event will be used." I propose adding the sentence "If more than one AT matches the notifytype and upsname, the AT declarations are executed in the order in which they appear in upssched.conf. This is the

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 everybody, i'm trying to use the UPSNAME environment variable within the script launched by upssched, and although it is correctly written and thus read by my script, it doesn't get updated when multiple UPSes are configured. To be more precise i'm monitoring 2 UPSes and using AT *EVENT* * *OPERATION* *handle *to manage events in upssched.conf. Am i wrong somewhere? I'm

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

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