similar to: upsmon error: Unable to call shutdown command

On Sun, 1 Dec 2013, Roberto Martelli wrote: > In my "upsmon.conf" I've setted this option for shutdown command: > SHUTDOWNCMD "/usr/sbin/pm-hibernate" > but when I pull the plug on my ups in way to test if this command works, > I obtain this error (in /var/log/syslog): > Dec 1 13:39:03 ubux upsmon[4561]: parent: Unable to call shutdown command: >

> If you call "/usr/sbin/pm-hibernate" from the command line, does it > execute correctly? > > Roger Obviously. Also thi command doesn't works with upsmon (but works from command line): /usr/sbin/hibernate

Il 02/12/2013 14:44, Charles Lepple ha scritto: > On Dec 1, 2013, at 8:46 AM, Roberto Martelli wrote: > >>> If you call "/usr/sbin/pm-hibernate" from the command line, does it >>> execute correctly? >>> >>> Roger >> >> Obviously. > You would be surprised how many times people forget things like #! or the execute bit in their shell

Hi, While using pm-suspend script as the SHUTDOWNCMD, upsmon does not correctly handle its returned values and leaves UPS in the "ups.status: FSD OL CHRG" state forever. This is with upsmon 2.6.5 from official Fedora Project packager. Box running Centos 6.7. Initially, upsmon would not execute pm-suspend at all. Creation of a custom SELinux module or changing to Permissive mode

Roger, I just ran a manual test, killing power and see what happens.  I set the Synology “Time before DiskStation goes into Safe mode” to 5 minutes so I didn’t have to wait like an hour until it powered down.  Here is the log: https://hastebin.com/ovuwilufeb.sql Everything appeared to be normal; the servers powered off and the Synology went into safe mode.  Power was then cut to the Synology

Hi all! All was working fine with all my UPSs and Windows 10 machines, NUT will notify events to NOTIFYCMD (which point to a .bat script to show messages) and finally will shutdown the system via SHUTDOWNCMD, that is another .bat file that simply uses shutdown.exe to hibernate the system. Today I upgraded all my machines to the latest Creators Update, and now NOTIFYCMD works as I can see

Is nobody using pm-suspend or pm-hibernate with upsmon? Or any other shutdown command besides the default one? Thanks, Jan On 22.4.2016 4:43, holomek at seznam.cz wrote: > Hi, > > While using pm-suspend script as the SHUTDOWNCMD, upsmon does not > correctly handle its returned values and leaves UPS in the > "ups.status: FSD OL CHRG" state forever. > > This is

On Fri, 7 Aug 2020, Todd Benivegna wrote: > APC Back-UPS NS 650M1 UPS ---USB---> Synology NAS (DS416 - Master?) > ---Ethernet---> Netgear Managed Switch w/ uplink to router <---Ethernet--- > Servers (Ubuntu 20.04 - Plex, Pulsar, Proton - All three set as slaves) I'm guessing that the UPS supplies only the NAS, not the 3 Ubuntu machines. Do they have their own UPS's?

Bonjour Openbsd 6.6 - NUT 2.7.4 from source - Eaton Ellipse Pro Installation OK upsc OK upsmon -c fsd OK (shutdown effective) I suppose mistake in upsmon config : # upsmon.conf MONITOR ellipse at localhost 1 upsmon pass master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -p -h now 'Sylvebarbe killed'" POLLFREQ 60 POLLFREQALERT 60 HOSTSYNC 120 DEADTIME 180 POWERDOWNFLAG

[please keep the list CC'd - use "Reply All".] On Sep 14, 2015, at 10:29 PM, d tbsky <tbskyd at gmail.com> wrote: > > 2015-09-14 20:28 GMT+08:00 Charles Lepple <clepple at gmail.com>: >> "upsmon -c fsd" sets the FSD flag on all of the UPSes attached to upsd. > > my nut version is 2.7.3. as I said, "upsmon -c fsd" not only set

Thank you for this. I appreciate your detective work as it saved my day to get it working! For anyone else finding this post you also need to set the SHUTDOWNCMD line in upsmon.conf to: SHUTDOWNCMD "shutdown /s /f /t 10" to force shutdown after 10 seconds using windows commands. The software ships with the linux shutdown configured which is clearly inappropriate. I couldnt find this

hi: my testing server has two power supply and attach to two ups. one of the ups is connect to the server with usb. my upsmon.conf like below: # for two ups MONITOR ftups at localhost 1 monmaster nutmaster master MONITOR ftups at 10.1.1.2 1 monslave nutslave slave MINSUPPLIES 1 # for early shutdown NOTIFYFLAG ONBATT EXEC+WALL+SYSLOG NOTIFYFLAG ONLINE EXEC+WALL+SYSLOG NOTIFYCMD

Hi everybody, I'm the author of a small C++11 program called XDGSearch. The source code is hosted on Github, for a quick overview you can visit this link https://github.com/frank67/XDGSearch/blob/master/README.md I'm writing to the mailing list because I'd like to make the database build process splitted in more thread. Is it possible? If you are a C++ programmer you can take a look at

upsmon.conf on server:  https://pastebin.com/z4CrUTxb nut.conf on server:  https://pastebin.com/540ShZH7 Permissions for /etc/nut:  https://hastebin.com/qecolodapi.diff On the Synology (I didn’t edit any of these files): ups.conf:  https://hastebin.com/dedereqizi.shell upsd.conf:  https://hastebin.com/pupeseweda.css upsd.users:  https://hastebin.com/ocenamecex.cs I don’t think I am able to run

Hi, this does sound like a useful idea - although for the principle of least surprise and for variation in deployments, I'd rather have it as a (non-default state of a) configuration toggle that can be set via `upsmon.conf`: whether this particular client exits after processing FSD or not. The onus for the rest would be on general systems integration - e.g. ensure that init scripts `K*`ill the

Hi to all, i install nut and it's work perfectly but when i start upsmon i recive the message: POWERDOWNFLAG (/etc/killpower) does not contain the upsmon magic string My upmon.conf contain: MONITOR myups@theseo 1 orion91 carlos81 master SHUTDOWNCMD "/sbin/shutdown -h +0" HOSTSYNC 15 POWERDOWNFLAG /etc/killpower FINALDELAY 5 My killpower scrit in /etc/killpower

On 14/09/2018 at 09:30, Jean-Francois Dockes wrote: > Hi, > > You may be interested by how Recoll does it: > > https://www.lesbonscomptes.com/recoll/idxthreads/threadingRecoll.html > > A few things in the document are slightly obsolete (esp. the last > paragraph: recollindex now does use vfork()), but it's overall quite close > to how the current indexer works.

those mails list are from last century but i give it a try ! created : https://github.com/networkupstools/nut/issues/563 Hello all, Trying to run an EATON 850pro via USB on a Debian Stretch Stable. I have letsencrypt certificate installed and working. When trying to manage the EATON device, i got: upsmon Can not initialize SSL context When 850pro is connected via USB, i can: lsusb Bus 009

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

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