similar to: Exclude COMMBAD status as a shutdown event?

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

On Sep 3, 2014, at 9:38 AM, Heiko L. <HL at fh-lausitz.de> wrote: > Howto force shutdown if nut-snmp Communications lost? > > My 1. suggestion was option DEADTIME, but seem to be information only. (s. below) DEADTIME expiration is a critical condition if the UPS is on battery when comms are lost, otherwise you are correct, it is only informative. What about a NOTIFYCMD script

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

hello, i've got a problem with the notifycmd here is a part of my upsmon.conf : NOTIFYCMD /usr/local/ups/bin/nut_notify NOTIFYMSG ONLINE "UPS %s is getting line power" NOTIFYMSG ONBATT "UPS %s is on battery" NOTIFYMSG REPLBATT "The UPS %s battery is bad and needs to be replaced" NOTIFYMSG LOWBATT "UPS %s is being shutdown by the master" NOTIFYMSG FSD

Hallo, I have one ups with snmp and any ups without snmp. Shutdown works while network online. But some batteries are empty, so that the communication break early. Howto force shutdown if nut-snmp Communications lost? My 1. suggestion was option DEADTIME, but seem to be information only. (s. below) Any suggestions? The last way would be a ugly cronjob (like: ping || shutdown). regards Heiko

Hi, I’ve posted my question on Superuser.com but not had any replies in 2 weeks, so I guess no-one there knows anything about NUT. https://superuser.com/questions/1441153/how-to-shutdown-macos-mac-osx-from-network-ups-tools-client-nut <https://superuser.com/questions/1441153/how-to-shutdown-macos-mac-osx-from-network-ups-tools-client-nut> I’m looking for help in shutting down my iMac on

Hello guys Yesterday i started do configure my Mustek Powermust650 with nut using the megatec_usb driver. Everything works fine except for the mailing when something happens. My upsmon looks like this: MONITOR powermust650 at localhost 1 local controller master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD /root/upsmailer POLLFREQ 10 POLLFREQALERT 5 HOSTSYNC 15

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 Is it possible to limit the frequency of specific notifications? In 2.7.4 it seems to be possible only for REPLBATT via RBWARNTIME, but that's it. My specific problem is that the UPS got disconnected and before I got hold of the server to turn the upsmon off my mailbox got flooded with hundreds of messages. It probably doesn't make sense for all notification types, but for

Hi, I have a Liebert UPS which I have connected to a FreeNAS Box. I had all sorts of issues making FreeNAS (FreeBSD based) talk to the UPS over USB. My solution seemed to be to buy a Raspberry Pi then connect it to the UPS (works fine), then make my NAS read the UPS status from the Pi over a TCP/IP connection. Convoluted I know, but it works well...for about a month, then it just loses

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 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've setup nas4free (latest version 11.0.0.4, which has NUT 2.7.4) in a VM and configured it via webinterface to my APC UPS and set "shutdown mode" to "UPS goes on battery" with a timer of 30s. Then I started runtime calibration on the UPS and after 30s nas4free has shut down! I think this is not the correct behavior, since the status was "OB CAL". The system

Hello NUT Team! I continue playing with NUT for Windows and USBHID-UPS driver I've got from Frederic to fix "Data Stale" problem. It seems there is something wrong when Network UPS Tools service is starting with disconnected USB cable. UPSMON is writing "Data Stale" to output and continue do it infinitely, even the cable is connected back. Here is a short log: Network

On Thu, 8 Jun 2017, Robbie van der Walle wrote: > After the first test and the NAS is restarted I had to change the > setting battery.charge.low again to 80? Does the NAS DSM reset battery.charge.low to 10 or is it internal to the UPS? You will have to experiment by disconnecting the UPS control lead from the NAS and connecting it (if possible) to the Mac. After setting to 80 and a

Ah! So I can detect the source UPS in the upssched.conf and pass it as a distinct event to the shell script. That sounds like an excellent approach. Thanks! GMH From: O'Shaughnessy, Mike [mailto:Mike.OShaughnessy at gd-ms.com] Sent: Tuesday, October 31, 2017 12:46 PM To: Garrett Michael Hayes <Garrett at VerbalImaging.com>; nut-upsuser at lists.alioth.debian.org Subject: RE: Email

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 folks, I'm having an issue with getting nut-server to start at boot on a freshly installed Fedora 40 desktop. Seems once the machine is up, I can manually start with systemctl start nut-server and everythings fine. dnf info nut Last metadata expiration check: 2:08:11 ago on Sat 27 Jul 2024 03:48:13 PM EDT. Installed Packages Name : nut Version : 2.8.2 Release : 1.fc40

On Feb 9, 2015, at 6:48 AM, PERE (yahoo.es) <pererivers at yahoo.es> wrote: > 0.028188 Can't set USB configuration: could not set config 1: Device or resource busy > 0.029246 detached kernel driver from USB device... > 0.030559 USB device [0001:0000] opened > 0.866216 read: (8 bytes) => 03 00 00 00 00 00 00 00 > 0.866413 reply[0] = 0x03

On Feb 25, 2014, at 1:13 AM, Kris Jordan wrote: > 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