similar to: upsmon+snmp-ups does not shut down system

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 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 I have this in /etc/nut/upsmon.conf (my QNAP NAS wants admin and 123456 or not working) RUN_AS_USER root MONITOR qnapups at localhost 1 admin 123456 master MONITOR qnapups at 192.168.222.252 3493 admin 123456 slave MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+EXEC

Hello all, I'm having problems with what I'm told should be a straightforward issue. The message in /var/log/daemon is: <quote> Feb 13 10:37:57 lupin upsmon[31324]: Master privileges unavailable on UPS [lupin1500AVR@localhost]

Hi, I'm using debian sarge on my server and connected a MGE-ups ellipse via the serial port. I searched the internet for the answer, but can't find it. My config files: <upsd.users> [admin] password = pwd allowfrom = 127.0.0.1/32 actions = set instcmds = all [upsmon] password = pwd allowfrom = 127.0.0.1/32 10.0.0.224/32 upsmon master [upsslave] password

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

Hello All, I'm trying to establish a MASTER SLAVE configuration of UPS using NUT Driver. I'm able to shutdown the master after UPS is on BATTERY ( POWER BLACKOUT) .However I'm trying to shutdown the other SLAVE MACHINES BEFORE MASTER. But at the remote side ( Slaves ) shutdown after UPS blackout does not happen. My configuration in Master are /usr/etc/upsd.users

Hi! Some systems I have take some time to shut down, so I would like them to shut down if the UPS have been on battery for 2 minutes. Internet has told me that SHUTDOWNCMD ?/sbin/shutdown -h +0? in /etc/nut/upsmon.conf will execute when the UPS is both OB (on battery) and LB (Low battery). Like in wiki.ipfire.org - Detailed NUT Configuration<https://wiki.ipfire.org/addons/nut/detailed>

Hi, I have been running nut successfully for a long time with my Debian 11 server. I upgraded my server to Debian 12 today, which upgraded nut also from 2.7.4-13 to 2.8.0-7. I noticed that after upgrade there was a upssched process running and taking 100% cpu time. I checked if there were any changes to configuration file formats with nut upgrade and only differences I noticed were a terminology

If there is a next Windows release, perhaps the default NOTIFYFLAG's should be adjusted? NOTIFYFLAG ONLINE SYSLOG NOTIFYFLAG ONBATT SYSLOG NOTIFYFLAG LOWBATT SYSLOG NOTIFYFLAG FSD SYSLOG NOTIFYFLAG COMMOK SYSLOG NOTIFYFLAG COMMBAD SYSLOG NOTIFYFLAG SHUTDOWN SYSLOG NOTIFYFLAG REPLBATT SYSLOG NOTIFYFLAG NOCOMM SYSLOG NOTIFYFLAG NOPARENT SYSLOG The 'wall'

Hello, I set up a FreeBSD 8.2 system with nut 2.6.1 and a Powerware 5115 connected by RS-232. I expected this setup to shut down before running out of battery power, but I either missed some important configuration or something else went wrong: The syslog says: Jan 9 05:03:42 b1 upsmon[67752]: UPS upsb1 at localhost on battery Jan 9 05:04:42 b1 upsmon[67752]: UPS upsb1 at localhost on line

Dear Chales, Thanks for your quick reply. I have Raspberry with last Kernel [Linux pi1 3.18.6+ #753 PREEMPT Sun Feb 8 14:47:22 GMT 2015 armv6l GNU/Linux] If <upsdrvctl>, <upsd> and <upsmon> are stopped <nutdrv_atcl_usb> Works well without any error as "Device or resource busy". If I run <upsc> command never receive any value from my ups <upsc ups at

I've not been able to connect to my ups using NUT 2.7.4 or NUT 2.8.0. 2.7.4 was installed as a package, 2.8.O was compiled from source. I've messed with permissons, everything is root:root and has the approprate read/execute permissons. I've tried two differnt UPS(es) APC & CyperPower. I'm running PI OS (Raspbian) on a Raspberry Pi3 model B. The port 3493 is open (UFW). I can

Hi all, I would like to check two UPS in two different buildings with an ubuntu server. I use SNMP on both UPS. The cgi-page displayed all information as expected, but if I pull the fuse for one UPS in building A, none action occur. I expected that I get a mail "UPS A on Batt" and that after 5 minutes the shotdownscript starts. But no action. I saw that there is no upsmon process

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 Everyone, I recently bought a Tripp-Lite SMART1500LCD for my Linux Mint 19.3 machine, connected via a USB cable. I installed Nut 2.7.4 from the Mint package repository via sudo apt update && sudo apt install nut. Everything works great: NUT issues low battery warning when it reaches the set low battery point and then issues shutdown commands...computer shuts down..then the UPS shuts

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

P.S.2 Today I experienced something weird. As I was working, the system started a shutdown and did shut down, then the UPS got powered off and then back on - an expected behavior for a power fail situation. However there was no power failure! I ran nut-journal to check what happened: Previous complete boot through shutdown Oct 29 10:09:33 i7 upsdrvctl[1966]: Using subdriver: MGE HID

hi i bought a ultra ULT31502 ups someone seem able to run this ups with nut just see Dean thread on: http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=770423&Tab=11&NoMapp=0 i use suse 10.1, i installed nut the ups is connected directely to my computer with an usb cable lsusb return Bus 001 Device 004: ID 0d9f:0001 Powercom Co., Ltd with lsmod, i can see

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