search for: upsrw

...r): nutdrv_qx -a ups -DDDDD >> /path/to/my/precious/log 2>&1 And keep it running all the time till the tests are over. - terminal #2 - as root: upsd -D This one too is expected to be kept alive all the time. - terminal #3: # shutdown.stayoff with ups.delay.shutdown set to 30 seconds; upsrw -s ups.delay.shutdown=30 -u <username> -p <password> ups upscmd -u <username> -p <password> ups shutdown.stayoff # shutdown.stayoff with ups.delay.shutdown set to 60 seconds; upsrw -s ups.delay.shutdown=60 -u <username> -p <password> ups upscmd -u <username&g...

...0 >> ?ups.delay.start: 180 > > These timers are in seconds. You will want to verify this, but according to those values, the UPS will shut off its output 30 seconds after the shutdown signal (so you need to make sure that your OS shutdown takes less time than that). > > Does "upsrw -l advice" show anything? $ upsrw -l advice upsrw: invalid option -- 'l' Network UPS Tools upsrw 2.7.2 usage: upsrw [-h] upsrw [-s <variable>] [-u <username>] [-p <password>] <ups> Demo program to set variables within UPS hardware. -h dis...

Greetings Charles; I hope you had a nice Christmas, and will have a happy and prosperous new year in 2016. You mentioned upsrw in a message earlier, so I ran it, and found the shutdown timeout was only 20 seconds. gene at coyote:~$ upsrw myups [input.transfer.high] High voltage transfer point (V) Type: STRING Value: 140 [input.transfer.low] Low voltage transfer point (V) Type: STRING Value: 88 [ups.delay.shutdown] Inte...

Hi all, i've a problem with only a command in all suite: upsrw. root at ProLiant:/etc/nut# upsrw -u monmaster -p p455w0rd -s ups.delay.shutdown=180 ups Unexpected response from upsd: ERR ACCESS-DENIED root at ProLiant:/etc/nut# upsc and upsmon work greatly. This is in my /etc/host.allow: upsd : localhost, LOCAL, 127.0.0.1, [::1] : ALLOW W...

Would you be so kind and provide some examples (commands), please? I would run them today in the evening and report back with the logs. Thank you. Jakub S. On Tue, Mar 10, 2015 at 11:44 PM, hyouko at gmail.com <hyouko at gmail.com> wrote: > mmh.. it looks like someone forgot to hit 'reply all'. > > - relaying the originally attached files (gzipped, minus the two >

...to/my/precious/log 2>&1 > And keep it running all the time till the tests are over. > > - terminal #2 - as root: > upsd -D > This one too is expected to be kept alive all the time. > > - terminal #3: > # shutdown.stayoff with ups.delay.shutdown set to 30 seconds; > upsrw -s ups.delay.shutdown=30 -u <username> -p <password> ups > upscmd -u <username> -p <password> ups shutdown.stayoff > > # shutdown.stayoff with ups.delay.shutdown set to 60 seconds; > upsrw -s ups.delay.shutdown=60 -u <username> -p <password> ups >...

Hi there, my HP R1500 G3 UPS doesn't apply my battery.charge.low value i set via upsrw. Is this a common problem with this model in nut 2.6.4? Any ideas how to force the UPS to accept this value? Regards Jan % upsc hp1500 battery.charge: 100 battery.charge.low: 20 battery.charge.warning: 20 battery.runtime: 23917 battery.temperature: 49.0 battery.type: PbAc battery.voltage: 39.0...

On Dec 29, 2015, at 3:27 PM, Gene Heskett <gheskett at wdtv.com> wrote: > > Greetings Charles; > > I hope you had a nice Christmas, and will have a happy and prosperous new > year in 2016. Hi Gene, Thanks, and same to you! > You mentioned upsrw in a message earlier, so I ran it, and found the > shutdown timeout was only 20 seconds. > ... > So I tried to reset that to 120 seconds, which the battery can do nicely, > and I have a 20kw in the back yard that is up and running, lights back > on in 16 or 17 seconds, so is 98%...

01.12.2014, 16:27, "Charles Lepple" <clepple at gmail.com>: > On Dec 1, 2014, at 9:19 AM, Victor Porton <porton at narod.ru> wrote: >> ?01.12.2014, 14:50, "Charles Lepple" <clepple at gmail.com>: >>> ?Does "upsrw -l advice" show anything? >> ?$ upsrw -l advice >> ?upsrw: invalid option -- 'l' > > I suppose I should read the documentation every once in a while :-) > > "upsrw advice" "upsrw advice" outputs nothing. > I was thinking of "upscmd...

After issuing this command: /upsrw -s ups.delay.shutdown=180 -u admin -p mypassword myups /I obtain this error:/ Unexpected response from upsd: ERR READONLY /After issuing this command:/ upsrw myups /I obtain no output./ /In my /upsd.users/ file I have these settings: /[admin]// //password = mypassword// //actions = SET// //i...

On Dec 1, 2014, at 9:19 AM, Victor Porton <porton at narod.ru> wrote: > 01.12.2014, 14:50, "Charles Lepple" <clepple at gmail.com>: >> Does "upsrw -l advice" show anything? > > $ upsrw -l advice > upsrw: invalid option -- 'l' I suppose I should read the documentation every once in a while :-) "upsrw advice" I was thinking of "upscmd -l advice". -- Charles Lepple clepple at gmail

Can anyone give me insight into upsrw? I have a cyberpower PR2200 UPS (running an experimental version of the powerpanel driver hot off the presses by Arjen (thanks Arjen!!)). When I try to run "upsrw -s xyz=abc" to set any available variable, I get "Set variable failed: Access denied". What user name and pass...

...|> |NUT 2.6.5 on FreeBSD 9.1 |> | |> | |> |Why isn't the variable outlet.1.delay.shutdown set with the following |> |command? |> | |> | |> | |> |# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown" |> |outlet.1.delay.shutdown: -1 |> | |> |# upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125 at localhost |> |Enter new value for outlet.1.delay.shutdown: 10 |> |OK |> | |> |# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown" |> |outlet.1.delay.shutdown: -1 |> | |> | |> | |> | |> |Am I missing som...

...then the ups sent the power loss message to PC. Do you think some others may take effect for the low voltage? Just have the upsc result attached. Then I retried input.transfer.low, default.input.transfer.low, overwrite.input.transfer.low. Looks like it still can not write to those params. $ sudo upsrw -s input.transfer.low=70 -u * -p * ups Unexpected response from upsd: ERR READONLY $ sudo upsrw -s default.input.transfer.low=70 -u * -p * ups Unexpected response from upsd: ERR VAR-NOT-SUPPORTED $ sudo upsrw -s overwrite.input.transfer.low=70 -u * -p * ups Unexpected response from upsd: ERR VAR...

NUT 2.6.5 on FreeBSD 9.1 Why isn't the variable outlet.1.delay.shutdown set with the following command? # upsc PW5125 at localhost | grep "outlet.1.delay.shutdown" outlet.1.delay.shutdown: -1 # upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125 at localhost Enter new value for outlet.1.delay.shutdown: 10 OK # upsc PW5125 at localhost | grep "outlet.1.delay.shutdown" outlet.1.delay.shutdown: -1 Am I missing something obvious?

...d" Result: server shutdown, but ups does not shut off! 3. run prog "upscmd -u name -p passwd qnapups shutdown.return" and next "shutdown". Result: server shutdown, but ups does shut off! UPS immediately ON after power up. I changed the ups in the following way: Set with upsrw: ups.delay.shutdown=60 Set with upsrw: ups.delay.start=90 Set with upsrw: ups.start.auto=no Set with upsrw: ups.start.auto=no Set with upsrw: ups.start.battery=no Set with upsrw: ups.start.reboot=no Please do not know how to write some parameters permanently to UPS? Sorry but I'm over Mailing...

Hello Charles, Thank you so much for your reply. Yes. 40v was too low. In windows, those range started from 76v, 85v, and 96v. Just tried upsrw command to modify input.transfer.low and input.transfer.boost.low. There were some error messages returned. Tried another one battery.charge.low and it returns ok. $ sudo upsrw -s input.transfer.low=70 -u * -p * ups Unexpected response from upsd: ERR READONLY $ sudo upsrw -s input.transfer.boost...

...wrote: > > |NUT 2.6.5 on FreeBSD 9.1 > | > | > |Why isn't the variable outlet.1.delay.shutdown set with the following > |command? > | > | > | > |# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown" > |outlet.1.delay.shutdown: -1 > | > |# upsrw -u au -p ap -s outlet.1.delay.shutdown PW5125 at localhost > |Enter new value for outlet.1.delay.shutdown: 10 > |OK > | > |# upsc PW5125 at localhost | grep "outlet.1.delay.shutdown" > |outlet.1.delay.shutdown: -1 > | > | > | > | > |Am I missing something obv...

On Jun 7, 2017, at 1:14 PM, Roger Price wrote: > > 2. On the NAS, use command > > upsrw -s battery.charge.low=80 -u upsmaster -s sekret UPS Robbie, The "upsrw" command contacts upsd, so it sounds like you should be able to add a user to upsd.users on the NAS, and then run something like this on the Mac: upsrw -s battery.charge.low=80 -u upsmaster -s sekret UPS at synol...

Hey Charles, Latest update. Looks like in ups.conf I setup default.input.transfer.low = 84. After I took that line out, restart upsdrvctl, upsmon, and upsd, the command of sudo upsrw -s input.transfer.low=70 -u * -p * ups return OK. Still need to verify if it works by using voltage regulator and will keep you updated. Thank you for your help Regards Shen On Thu, Jun 5, 2014 at 8:54 AM, Shen Chuan <shen at minutekey.com> wrote: > Hello Charles, > > Thank y...