similar to: fsd fails to notify slaves

On Apr 21, 2015, at 12:09 PM, dmanye <dmanye at urv.cat> wrote: > Apr 21 17:45:23 jessie641 upsmon[532]: FSD set on UPS smt750i at 10.21.102.241 failed: ERR ACCESS-DENIED > Apr 21 17:45:23 jessie641 upsmon[532]: Executing automatic power-fail shutdown > Apr 21 17:45:23 jessie641 upsmon[532]: Auto logout and shutdown proceeding > > i think the problem may be the first line.

El 16/07/15 a les 14:16, Charles Lepple ha escrit: > On Jul 16, 2015, at 5:09 AM, dmanye <dmanye at urv.cat> wrote: > >> surprisingly, now both computers made the ups reboot !?!?!?!? so i've tried once more and confirmed that while forcing the reboot works, the computer itself does not reboot the ups when the battery is too low. > I think you figured it out: the UPS

El 15/07/15 a les 15:19, Charles Lepple ha escrit: > On Jul 15, 2015, at 8:46 AM, dmanye <dmanye at urv.cat> wrote: > >> El 15/07/15 a les 14:18, Charles Lepple ha escrit: >>> On Jul 15, 2015, at 7:17 AM, dmanye <dmanye at urv.cat> wrote: >>> >>>> i have a computer (with debian 8 jessie installed) that i want to plug to an ups (apc smt 750i) to

El 15/07/15 a les 14:18, Charles Lepple ha escrit: > On Jul 15, 2015, at 7:17 AM, dmanye <dmanye at urv.cat> wrote: > >> i have a computer (with debian 8 jessie installed) that i want to plug to an ups (apc smt 750i) to act in netserver mode. i've installed nut packages and configured it and all seems to work ok except that when the server shutdown itself it ups doesn't

hello, i have a computer (with debian 8 jessie installed) that i want to plug to an ups (apc smt 750i) to act in netserver mode. i've installed nut packages and configured it and all seems to work ok except that when the server shutdown itself it ups doesn't "reboot" the outlets. i've tested the same config (/etc/nut/*) just changing hostnames in another debian jessie

El 18/07/15 a les 17:03, Charles Lepple ha escrit: > On Jul 17, 2015, at 9:42 AM, dmanye <dmanye at urv.cat> wrote: > >> so i reinstalled again... but instead of using four separate partitions for /, /usr, /var and /tmp, put all the stuff under an unique / partition and... it works! why exactly? no idea, because if i'm not wrong, nut sensitive stuff is under /lib, /sbin,

I am looking for a command-line driven audio splicer for .wav files. Any ideas? todd@toolz.com --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent

oddsock wrote: > yep, it's in there...you give it a master server ip and port and the > relay functionality will connect to the master server and relay all > connected mountpoints. cool > yep, Michael added that a bit ago...Shoutcast style streaming titles (or > any streaming titles for that matter) is not supported however. You > will now need to provide a

By the way, I was delighted to find out that I could join .ogg files with cat, i.e. cat {file1.ogg} file2.ogg > outputfile.ogg <p>I successfully used this capability, together with oggenc and sox, to join two .WAV files in the following manner: <p>oggenc -q9 file1.wav ... oggenc -q9 file2.wav --- cat file1.ogg file2.ogg > outfile.ogg ox outfile.ogg outfile.wav I get

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

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 Jul 15, 2015, at 8:46 AM, dmanye <dmanye at urv.cat> wrote: > El 15/07/15 a les 14:18, Charles Lepple ha escrit: >> On Jul 15, 2015, at 7:17 AM, dmanye <dmanye at urv.cat> wrote: >> >>> i have a computer (with debian 8 jessie installed) that i want to plug to an ups (apc smt 750i) to act in netserver mode. i've installed nut packages and configured it

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

[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 to find the exact bit of FSD? I am totally newbie in this topic. > Could you please elaborate the hex editing of FSD bit? I haven't used 'mc' before, but assuming it has a hex editor, you would just

[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: 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

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

"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

hi: my nut server has redundant power and connect to different ups. when one of the ups lost power, the nut server set the ups to "FSD" correctly, so server connect to the ups can shutdown normally. but nut server itself won't shutdown since it has another power source. now the ups get power again and the "FSD" flag should be recovered. but it seems no procedure of

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