similar to: Formalize use of the FSD flag (was: NUT driver update process...)

Hi Billy, switching back this thread to -upsdev 2012/2/27 William R. Elliot <bill at wreassoc.com>: > I have been able to set the 'FSD' from the driver and it is picked up by > upsmon.? That gives me the functionality that I was asked to put in the > driver.? If that is against the rules then I'll make an adjustment when the > allowed method is defined.? :-) yup,

Hello, I have some questions about netxml-ups driver. My UPS: Eaton PW9130 1500VA-T with Network Management Card. OS: Fedora 24 NUT 2.7.4 (from fedoraproject repo) Driver: netxml-ups. Results of upsc: ambient.humidity.high: 90 ambient.humidity.low: 5 ambient.temperature.high: 40 ambient.temperature.low: 5 battery.charge: 100 battery.charge.low: 20 battery.charge.restart: 0 battery.runtime: 69012

I have the latest version of the Windows port of NUT installed on my Windows?7?machine. The UPS is connected via serial cable to the Windows machine. I also have my Synology NAS (which uses NUT) connected over the local network as a slave to the Windows NUT master. The Synology slave is configured to immediately go into "safe mode" whenever an FSD or OB+LB indication is received from the

I have pfsense set as the NUT master and my Synology NAS as a slave client. I tried recreating a shutdown sequence by issuing a /usr/local/sbin/upsmon -c fsd command in pfsense (so as to preserve battery lifetime while testing all these) but the weird thing is that my Syno doesn't seem to get a hold of the FSD event. My pfsense master and UPS shuts down properly though. As soon as I issue the

Hello, I am a new user of NUT and trying to wrap my ahead around a couple of things. I installed NUT 2.7.4-13 from package on RasPi 4, running Raspbian Linux 11 (bullseye). I have Cyberpower SL700U connected to it. For testing I set battery.charge.low to 90, so I wouldn't have to wait a long time. See all relevant config below. First of all, what seems to happen is that UPS gets to the low

On Tue, 29 Sep 2020, João Luis Meloni Assirati wrote: > The UPS I am developing a driver to is able to report several flags for > critical hardware conditions, like overheat, overload, inverter failure, > output short etc. What should be the correct policy of operation when such a > condition occurs? I think that the an UPS in such a condition is not reliable > and therefore a

[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

Hi! I'm trying to setup a small mobile server rack with key switch to power on/off the whole system. Used USP is an APC Smart-UPS 1500 SMT1500RMI2U with extra AP9613 IO card [1] to get the key switch "connected" to the UPS. The IO card has several inputs which can trigger actions like power on and "gracefully" shutdown. On key switch OFF this SMT ups model changes ups

Roger, here is my output of ps -elf |grep upssched root at nutpi:~# ps -elf |grep upssched 0 S root 1242 1191 0 80 0 - 1834 pipe_w 05:23 pts/0 00:00:00 grep upssched No timer, just the grep of upssched.. On Mon, Jan 27, 2020 at 4:27 AM <nut-upsuser-request at alioth-lists.debian.net> wrote: > Send Nut-upsuser mailing list submissions to >

Hello. I sometimes encountered batteries that were ok, but at times one of the cells would develop a random short/open, therefore reducing the real capacity even if voltage reading was ok. In the absence of a battery load tester i would suggest running multiple tests with a load (car headlight bulb or similar) on the battery outside the ups. This is to eliminate the suspicion of a software or UPS

OK, so yesterday evening I done a real test cutting of the power to the UPS. And it went good... the UPS supported my server for 28:50 minutes (i.e. the expected runtime with this load), before forcing shutdown. The batteries could still hold as charge was 30 % with about 15 minutes run time. And the UPS did hold for another full 10 minutes before powering off. These are the relevant lines

On January 11, 2020 1:18:27 PM GMT+02:00, "Georgi D. Sotirov" <gdsotirov at gmail.com> wrote: >Hello, > >I'm experiencing a strange early shutdown behavior with the following >system: > > * */OS/*: Slackware Linux 14.2 x86_64 > * */NUT/*: 2.7.4 (from my own package > <https://sotirov-bg.net/slackpack/pack.cgi?id=4083>) > * */UPS/*: MGE

On 1/25/20 10:53 AM, Georgi D. Sotirov wrote: > OK, so yesterday evening I done a real test cutting of the power to > the UPS. And it went good... the UPS supported my server for 28:50 > minutes (i.e. the expected runtime with this load), before forcing > shutdown. The batteries could still hold as charge was 30 % with about > 15 minutes run time. And the UPS did hold for

fredag 27 oktober 2023 20:07:58 CET skrev Jim Klimov: > Hi, this does sound like a useful idea - although for the principle of > least surprise and for variation in deployments, I'd rather have it as a > (non-default state of a) configuration toggle that can be set via > `upsmon.conf`: whether this particular client exits after processing FSD or > not. The onus for the rest

I found something interesting that I think may apply here. Check this out... https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave *I have the latest version of the Windows port of NUT (A UPS management package) installed on my Windows 7 machine. The UPS I am using is a very old APC BK650M which is controlled and sends its status via a special serial cable to the

Sorry, I guess it is */usr/syno/bin/synoups* On Fri, Aug 14, 2020 at 2:27 PM Todd Benivegna <todd at benivegna.com> wrote: > I found something interesting that I think may apply here. Check this > out... > > > > https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave > > *I have the latest version of the Windows port of NUT (A UPS

On Mar 13, 2015, at 6:30 PM, cinowell <cinowell at gmail.com> wrote: > Hello, > > I had running OpenMediaVault server with NUT 2.4.3 megatec_usb driver. After the OMV upgrade, NUT also upgraded to 2.6.4. I realised that megatec_usb removed in this version. So I have configured to use blazer_usb driver. However NUT behaves incorrectly after switching blazer_usb. System is being

On Fri, 14 Aug 2020, Todd Benivegna wrote: > https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave  > > I have the latest version of the Windows port of NUT (A UPS management package) installed on my Windows 7 machine. The UPS I am using is a > very old APC BK650M which is controlled and sends its status via a special serial cable to the Windows

Hello, I'm experiencing a strange early shutdown behavior with the following system: * */OS/*: Slackware Linux 14.2 x86_64 * */NUT/*: 2.7.4 (from my own package <https://sotirov-bg.net/slackpack/pack.cgi?id=4083>) * */UPS/*: MGE Ellipse PRO 1600 <powerquality.eaton.com/Products-services/Backup-Power-UPS/Ellipse-PRO.aspx> (bought in September 2017) */Problem

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