similar to: upsmon error: 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

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:

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

Hi, They say one should never argue with people that know more than you, so please bear with me. On 2013/10/24 09:47 PM, hyouko at gmail.com wrote: > The driver is expecting either 'ACK' or no reply at all in case of > success and the command itself echoed back in case of errors. > On the other hand, your UPS replies '(ACK' in case of success and > '(NAK' on

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 Tue, 19 Jun 2018, tech wrote: > Jun 19 16:34:55 REDACTED upsmon[7389]: Can not initialize SSL context > I am lost. Comments and Help welcome. It's only a comment, but, this message comes from NUT program netssl.c status = NSS_NoDB_Init(NULL); if (status != SECSuccess) { upslogx(LOG_ERR, "Can not initialize SSL context"); nss_error("upscli_init /

Hello all. Thx for the log-tip. It was a access right violation on /etc.../letsencrypt/....cert . The folder was own by root:root Had to create a group nutusers including root and my nut users. After that, had to change the chmod for the folder from 755 to 775 Now, running upsc -l Init SSL without certificate database 850PRO Witch is better. But still problématic wuth the init ssl

Hi Jon, your patches are malformed because (presumably) your email client wrapped this lines. Could you please send these as a unified diff ("diff -u"), and send them in attachments, rather than as a copy-and-paste? Thanks, -- Peter Jon Gough wrote: > > Peter, > Here are the files I have worked on. I hope I have diff'd them > correctly. I have not touched the

(please use reply-all - this list does not alter reply-to headers) On Sep 10, 2015, at 6:23 AM, Thomas Aichinger <taich at qpl.at> wrote: > > Hi, > > I am using a ALLNET 91500 UPS with blazer_usb driver > > /usr/lib/ups/driver/blazer_usb -a ups91500 -L > Network UPS Tools - Megatec/Q1 protocol USB driver 0.10 (2.7.1) [...] > I set delay.shutdown to 600 sec but UPS

I have several Best "Fortress LI660", manufactured ~1995, which use bestfortress(8). nut has been monitoring two of them just fine for years via a USB/serial adaptor and homemade TXD/RXD/COMMON cable. I am now trying to properly set up LB shutdown and have a few questions. 1) ups.shutdown.delay is set in the driver: dstate_setinfo("ups.delay.shutdown",

I want to use upsdebugx, upslogx in 'clients/upsclient.c', however this fails with the following error messages (I trimmed the path to the build directory to <path> in order to prevent line wrapping): <path>/clients/upsclient.c:941: undefined reference to `upsdebugx' <path>/clients/upsclient.c:910: undefined reference to `upslogx'

Franco Martelli writes: > 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

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

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

----- Doorgestuurd bericht van dkbrig at gmail.com ----- Datum: Thu, 29 Jan 2009 11:16:06 -0600 Van: Danny <dkbrig at gmail.com> Onderwerp: upscode2.c Aan: adkorte-guest at alioth.debian.org Hi, I apologize if you are not the correct person, but I was wanting to submit a bug report for the upscode2.c driver but could not find a way to do that from the NUT website.

On Feb 27, 2014, at 7:07 AM, jimklimov at cos.ru wrote: > This apparently implies that, unlike some docs say, the snmp-ups driver can send the shutdown signals (is not crippled by design)? ;) We're working on it: http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/docs/man/snmp-ups.html#_shutdown A quick check says that the implementation has been there since v2.6.4, and

The tripplite driver was developed on a machine with a reliable serial connection, and inherited the assumption that the serial line connection would not drop, reorder, or fail character read and writes. This patch adds significantly improved failure mode handling and also does basic checks of data validity. There's also a few minor cleanups/beautification. I've tested this code on my

Hello, all. Some time ago I bought myself a UPS which was advertised as USB-HID. It was a surprise to learn that while it definitely is recognized as USB device, the HID descriptor has no UPS pages at all. The only software it came with was a windows program written in visual basic. Trying to research this topic I found a reference to energizer USB ups driver and learned about variety of

I have added preliminary support for the TrippLite protocol number 2001 into tripplite_usb.c. The attached file is supplied as a patch against today's SVN. This patch adds support for TrippLite SMART550USB and some Omni models. Tested are On Line, On Battery, Battery Good, and Battery Bad indication. Everything else seems to work, but this UPS is attached to a critical system, and I can

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