similar to: procedure of recover FSD

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

[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

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 attaching debug logs. Hopefully it helps to fix this issue. Thank you. 2015-03-17 22:43 GMT+00:00 hyouko at gmail.com <hyouko at gmail.com>: > 2015-03-17 0:24 GMT+01:00 Charles Lepple <clepple at gmail.com>: > > On Mar 16, 2015, at 12:26 PM, cinowell <cinowell at gmail.com> wrote: > > > >> I've done all the steps. However FSD indication

2012/2/28 Arnaud Quette <aquette.dev at gmail.com>: > Hi Charles > > 2012/2/28 Charles Lepple <clepple at gmail.com>: >> On Feb 28, 2012, at 3:44 AM, Arnaud Quette wrote: >> >>> Hi Billy, >>> >>> switching back this thread to -upsdev >>> >>> 2012/2/27 William R. Elliot <bill at wreassoc.com>: >>>> I

Hi I'm having a problem with the bcmxcp_usb driver FSD command: everything seems to work apart from: upsmon -c fsd Environment: Ubuntu 7.04, nut 2.0.5-1, nut-usb 2.0.5-1, Powerware 3105 UPS. upsd appears to send the FSD command to the UPS, upsmon then runs my NOTIFYCMD (which halts my PC) but the UPS just doesn't turn off. Here are the /var/log/daemon.log entries: Jul 24 23:13:16

In the current recovery procedure, recovering node recovers orphans from the slot it is holding and the slots that dead nodes were holding. Other online nodes recover orphans from their slots. But orphans in offline slots are left un-recovered. This patch queues recovery_completion for offline slots. Signed-off-by: Srinivas Eeda <srinivas.eeda at oracle.com> --- fs/ocfs2/journal.c | 21

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

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

On Mar 16, 2015, at 12:26 PM, cinowell <cinowell at gmail.com> wrote: > I've done all the steps. However FSD indication did NOT disappear. So it seems UPS always send the FSD flag. I know this sounds kind of ridiculous, but you could use a hex editor to change 'FSD' to 'OFF' in blazer_usb (it only seems to occur once), which would restore the behavior of

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

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

"ups.status: ALARM OL OFF" Great! This was so easy than I expected. UPS back to life again. Thank you. 2015-03-22 14:22 GMT+02:00 Charles Lepple <clepple at gmail.com>: > [please keep the list cc'd - thanks] > > On Mar 22, 2015, at 6:20 AM, cinowell <cinowell at gmail.com> wrote: > > > I may use the 'mc' in terminal. But I am not sure how

hello, i have an apc smt750i with 3 debian computers connected to it. i want one of them act as a master to notify the other two in case the battery is about to exhaust. upsmon in the slaves gets notified when the system changes from main to battery and viceversa. the problem i have is that the slaves are not notified and shutdown because of losing the connection to the master, but not for

2015-03-17 0:24 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 16, 2015, at 12:26 PM, cinowell <cinowell at gmail.com> wrote: > >> I've done all the steps. However FSD indication did NOT disappear. So it seems UPS always send the FSD flag. One thing more. Can you launch the driver with a debug level of 3 and then report back the log (gzipped) of the same

Hi, I have recently installed NUT 2.7.3.1 on a freshly installed Ubuntu 16.04 LTS (64-bit) system, connected via USB cable to APC Smart-UPS 1500 (SMT model). I am trying to make this configuration work for automatic shutdown/restart but it seems that it completely ignores /etc/killpower presence. I know the APC SMT models are problematic but it looks like I could not even make the simplest

Still looking for a Recover data Mac (http://www.umacos.com/data-recovery-mac.html) which supports storage media like ,usb flash drives, external hard drives, memory cards. Be compatible with portable device:mp3/mp4 player. And supports Mac OS X 10.3 or later. I highly recommend you this one to . Recover data Mac is the best data recovery software on the market for recovering data from a

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

During recovery, a node recovers orphans in it's slot and the dead node(s). But if the dead nodes were holding orphans in offline slots, they will be left unrecovered. If the dead node is the last one to die and is holding orphans in other slots and is the first one to mount, then it only recovers it's own slot, which leaves orphans in offline slots. This patch queues complete_recovery

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 would be on general systems integration - e.g. ensure that init scripts `K*`ill the