similar to: upsmon errors with /usr/sbin/pm-suspend as the shutdown command

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

For various reasons - I have been trying to get my Desktops and/or servers to shut-down a fixed time after a power fail - or better still a fixed time - or a low battery whichever comes first. I note in my upsc: *> upsc belkinusb* battery.charge: 100 battery.charge.low: 30 battery.charge.warning: 30 battery.runtime: 120 battery.type: PbAc battery.voltage: 27.3 battery.voltage.nominal: 24

upsmon.conf using NOTIFCMD and NOTIFYFLG is working well, it is calling my script "notify" on requested events (ONBATTERY,LOWBATTERY and ONLINE). Command #upsmon -c fsd -u monmaster myups at localhost gracefully shutdown my box and after several seconds switch off the ups's load. Two problems: - notify script is called and executed as user "nut" (as it used to be

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

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: /usr/sbin/pm-hibernate Instead if I set this 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

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

[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

Hi, we're trying to do something that's perhaps unorthodox, but seemingly should work; but not for me. We've got a Powerware 9315, that we are serially attaching one machine to. We have several classes of systems that we want to have shut down at different times. I've been doing my config testing by attaching the master machine to a Powerware 9120, and yanking the power

I have pfsense set as the NUT master and my Synology NAS as a slave client. I tried recreating a shutdown sequence by issuing a /usr/local/sbin/upsmon -c fsd command in pfsense (so as to preserve battery lifetime while testing all these) but the weird thing is that my Syno doesn't seem to get a hold of the FSD event. My pfsense master and UPS shuts down properly though. As soon as I issue the

Hi, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb

Hi, I try to install the newhidups driver for a MGE Pulsar M2200 connected to a USB port under Linux Red Hat 4 Upd 4. I have compiled and installed the usb driver (make usb && make install-usb). I followed the instructions in /nut-2.0.5/scripts/hotplug-ng/README abour the /etc/udev/rules.d/025_nut-usbups.rules. The ups is recognized by the kernel: Mar 12 14:52:03 serveur1 kernel: usb

On Saturday, 1 September 2018 17:50:13 BST Charles Lepple wrote: > I don’t have the code in front of me at the moment, but my guess is that the > config parser stopped parsing at the “#” character. I suspected a rogue character was being interpreted and used `backticks`, 'single quotes' and then "double quotes", but all failed. I ended up removing the offending #

I've googled and RTFM'ed, but still can't solve this one. I hope you folks can. This affects my entire computer cluster, but let's start simple: I've got a computer running NUT; OS is Scientific Linux 5.5; kernel 2.6.18-274.12.1.el5xen. It connects to an APC SMART-UPS via an APC SmartCard using the snmp-ups driver. It generally works: upsmon will detect if the battery is low

I'm running nut 2.0.1 with an MGE pulsar evolution 3000 with the mge-utalk (serial) driver on NetBSD 3.1 . I had a very strange occurance in my basement datacenter this early AM. the following was logged by upslog: 20080219 023452 100.0 123.0 049.0 [OL CHRG] NA 60.00 20080219 023522 100.0 122.8 049.0 [OL CHRG] NA 60.00 20080219 023552 098.0 123.0 049.0 [OL DISCHRG] NA 60.00 20080219 023622

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 All, I have noticed these messages in my logs: ========================================= Sep 01 13:14:22 osmc upsd[1450]: listening on 127.0.0.1 port 3493 Sep 01 13:14:22 osmc upsd[1450]: listening on ::1 port 3493 Sep 01 13:14:22 osmc upsd[1450]: listening on 127.0.0.1 port 3493 Sep 01 13:14:22 osmc upsd[1450]: listening on ::1 port 3493 Sep 01 13:14:22 osmc upsd[1450]: Connected to UPS

Every time I try and join a Vista system to the domain I get this error in the log: [2010/03/26 15:18:58, 0] smbd/service.c:make_connection(1191) april (192.168.1.194) couldn't find service public Error: modifications require authentication at /usr/sbin//smbldap_tools.pm line 1083. [2010/03/26 15:19:16, 0] passdb/pdb_interface.c:pdb_default_create_user(329) _samr_create_user: Running the

Hi All, I was wondering what people are doing to shutdown their equipment based on the temperature NUT grabs from a UPS? It doesn't appear that upsmon(8) has an appropriate notify event for temperature levels. For the time being, it looks like I'll write a simple perl wrapper around upsc to get ups.temperature, but would love to use something natively from NUT, if possible. Also,

Hello, I've installed Nut (2.0.5) on RedHat a week ago, and upsmon seems to generate false alarms every hour: ... Jun 8 06:10:56 nutevalserver upsmon[2849]: UPS usb-mge-evolution at localhost on line power Jun 8 06:35:46 nutevalserver upsmon[2849]: UPS usb-mge-evolution at localhost on battery Jun 8 06:35:51 nutevalserver upsmon[2849]: UPS usb-mge-evolution at localhost on line power