similar to: upsmon SHUTDOWNCMD not working

Bonjour serveur : Fujitsu TX1310 M1 - OpenBSD 6.6 UPS : Eaton Ellipse pro 1200 Serveur en fonctionnement normal. Installation classique sur le serveur par pkg_add nut-2.7.4p5 : quirks-3.16 signed on 2018-10-12T15:26:25Z nut-2.7.4p5: ok The following new rcscripts were installed: /etc/rc.d/nut /etc/rc.d/upsd /etc/rc.d/upsmon See rcctl(8) for details. New and changed readme(s):

Bonjour Openbsd 6.6 - NUT 2.7.4 - EATON Ellipse PRO NUT installed using pkg_add - not working driver : usbhid-ups I have (at last) two problems : 1. ... >> usbhid-ups -a ellipse Network UPS Tools - Generic HID driver 0.41 (2.7.4) USB communication driver 0.33 kill: No such process Using subdriver: MGE HID 1.39 libusb_get_interrupt: Function not implemented ... >> 2. ...

*** solved *** Using http://rogerprice.org/NUT/ConfigExamples.A5.pdf and upsrw, my BSD shutdown at low power of 80% Bye

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

On Sep 11, 2014, at 10:38 AM, Rob Groner <rgroner at RTD.com> wrote: > I?m still getting the onbattery, online, comm good, comm bad, etc system messages. Clearly there is some default behavior going on. How do I keep these system messages from happening? From http://www.networkupstools.org/docs/man/upsmon.conf.html: "NOTIFYFLAG type flag[+flag][+flag]? By default, upsmon sends

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

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 everybody, I installed and configured Nut 2.4.3 on Debian Squeeze, using package. It monitors an MGE Pulsar 1500 UPS in standalone mode. Here are parts of upsmon.conf : SHUTDOWNCMD "/bin/bash /root/extinction.sh >> /var/log/ups/ups.log 2>>&1" NOTIFYCMD "/bin/bash /usr/sbin/alerte.sh" [...] NOTIFYFLAG ONBATT SYSLOG+EXEC At startup, driver, upsd and upsmon

Here are three wishes for the future of upsmon: 1. The NOTIFYMSG texts should allow UTF-8 encoded messages. 2. The flags used in NOTIFYFLAG should be extended to include USER. This flag says that the message is to be sent to the notify daemon, perhaps with the command notify-send -a NUT -t 604800000 -u critical <message> This will allow the users of a workstation to see the

Ok, I am running NUT in dummy mode. I have added a new ups in ups.conf [dummy] driver = dummy-ups port = upsc.dev desc = "dummy ups for testing purposes" upsc.dev has been generated by exporting the Elit configuration. I have added the monitor line in upsmon.conf and the "exec" flags (all the events) MONITOR dummy at artu 1 user pass master SHUTDOWNCMD

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

I've built NUT 2.8.0 from source. When the nut-monitor runs: fopen upsmon.pid fails. I'm running as root, upsmon has root:root permissions as well as the other daemons and .conf files. I've tried configuring with and without --prefixpath --prefixaltpath. Is there something I am missing? Please see attached. Dan -------------- next part -------------- An HTML attachment was

Bonjour, Actuellement en 4ème année en ecole d'ingénieur, nous avons a developper une application de streaming capable de gérer le format Flac. Pour cela, nous avons repris les sources de Icecast et du streamer Ices. Mais devant la difficulté de la manipulation de la librairie Flac en tant que tel, nous avons choisi d'utiliser la technologie Ogg pour transporter le flux audio flac.

Windows 7 Pro x64 NUT 2.6.5-4 upsmon, when there is a problem, spams the event log every 5 seconds. Poll interval is 5 seconds also. I have witnessed the below messages filling up the event log. upsmon - UPS [ups at localhost]: connect failed: Connection failure: Unknown error. upsmon - Poll UPS [ups at localhost] failed - Data stale. I've already reported earlier how I've been

On Sat, 1 Apr 2017, Stuart Gathman wrote: > On 04/01/2017 03:14 PM, Dan Craciun wrote: >> On my Nagios monitoring system I use check_nut_plus (that in turn >> calls upsc) to monitor the status (ups.status), load (ups.load), >> battery charge (battery.charge) and runtime (battery.runtime). >> >> If these return "unknown", it means upsd is no longer

thank you all for your input. Roger, I'm a nut noob and only marginally understand the implementation (from your other email), but I really like the idea of a heartbeat and design wise it makes a lot of sense. I'll see if I can implement it some time soon. thank you, Spike On Sat, Apr 1, 2017 at 1:54 PM Roger Price <roger at rogerprice.org> wrote: > On Sat, 1 Apr 2017, Stuart

I've followed the config setup docs and also the excellent guide from Roger Price. I'm using openSUSE 13.1 and built NUT 2.7.2 from the sources (latest stable). I'm hooked up to a dummy UPS that basically just cycles from fully charged down to about 20% discharged. I was pleased when I started seeing the messages on my screen indicating the UPS was online or on-battery. Given how

Now that upsstats.cgi works, I've noticed that dummy-ups changes state every 5 minutes between OL and OB (probably when the 300 second timer expires). The UPS state stays online. Also "online" and "onbatt" are broadcast to the console probably via WALL. (The state changes don't seem to be form the ups as upsshed-cmd doesn't run). Upssched-cmd does run when the UPS

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