similar to: windows version upsmon.exe - libgcc_s_dw2-1.dll error

Hi, I just installed NUT-Installer-2.6.5-6.msi on Windows 2012 server, set config as netclient and start windows service. I found service is running but monitoring is not working. After some investigation I discovered that I had to copy libgcc_s_dw2-1.dll from c:\Program Files (x86)\NUT\bin\ to c:\Program Files (x86)\NUT\sbin\ I suppose it is a bug and should be corrected with next windows

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:

[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

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

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

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

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

Hi; I have ran into an issue with the upsmon tool leaking memory over a two month period. It seems to be due to one of my UPS hosts offline. System is a debian stable with the default nut package. Here's the data so far: companyfs1:/var/log# ps aux | grep [n]ut nut 2439 0.0 3.6 380800 18800 ? S Jun05 6:41 /sbin/upsmon >From my logfiles its failing on one of my UPS

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

Greetings, I imagine this question must have been answered previously on the list, but I can't search for the answer because the archives are gone. Executive summary: I am trying to install and configure nut 2.0.1 on Fedora Core. I have a SmartUPS Pro plugged into a USB port. Upsmon is logging "UPS myups@localhost is unavailable" to syslog and via wall when it starts up and

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

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

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

Short description: when upsmon starts it logs this to /var/log/messages: Jul 11 12:35:55 sorcerer upsmon[23902]: Startup successful Jul 11 12:35:55 sorcerer upsmon[23902]: user monuser not found Near as I can tell upsd is running properly. Long description: Centos 5 system (x86_64), built nut 2.2.2 from stable source with ./configure --with-usb --with-user=nut --with-group-nut make

An update - I ran a test by unplugging my UPS and letting it run down. The system shut down as it should. However, the /etc/killpower file was not created, and the UPS did not shut off power as it should from the shutdown scripts. This may be because the command to kill the output of the UPS isn't available, or that by not being able to log in as master prevents this. The permissions on the

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

Using the HOWTO in http://keystoneit.wordpress.com/2006/09/25/network-ups-tools-nut-on-ubuntu/ I installed nut on an Ubuntu Edgy LAMP Server with an Eaton Powerware 5110 attached to it via usb. But nut fails to start properly (see the error message "Starting Network UPS Tools: (upsdrvctl failed) upsd upsmon" below). It then complains about communication with the UPS being lost ("UPS

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 installed the windows binary package 2.6.5-6 on windows 7. Installation went fine but upsmon did not start though I did create a valid conf file. Stopping the service gives an error saying "could not stop upsmon" but no error while starting the service. Manually running upsmon from the sbin folder shows it cant find liblea32.dll, ssleay32.dll and libgcc_s_dw2-1.dll. The former

> On 9 Jun 2019, at 21:19, Roger Price <roger at rogerprice.org> wrote: > Using upssched and a upssched-cmd script to shut down the system is an alternative to using the builtin upsmon SHUTDOWNCMD on status [OB LB]. A upssched-cmd script can provide a managed shutdown well before [OB LB] is reached, but should the UPS reach that status upsmon's SHUTDOWNCMD will take over and