similar to: ERR ACCESS-DENIED in upsrw

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// //instcmds = ALL// // //[myuser]// //password = mypassword//

2013/12/6 Fabio Cecamore <ceca_89 at hotmail.com>: > Hi all, Hi > I've problem with the management of my AtlantisLand UPS, the UPS don't want > to wake up after the whiteout and I don't have any idea why.. Some (very old) units are known to have problems with small values for ondelay (hence the default 3 minutes value):

2013/12/9 Fabio Cecamore <ceca_89 at hotmail.com>: > and the UPS don't wake up after the whiteout.. 2013/12/6 Fabio Cecamore <ceca_89 at hotmail.com>: > desc = "AtlantisLand Host Power 851+" Is your UPS an 'Atlantis Land Host Power 851' or an 'Atlantis Land One Power 841+'? The first one should be using a slighty modified version of the

Hello, i've a problem, this is my configuration: - Atlantis Land UPS with serial port - a generic RS232 to USB cable adapter (QinHeng Electronics HL-340 USB-Serial adapter for linux). The problem is in the syslog file where i find: [...] Aug 19 09:07:25 ProLiant megatec[1126]: Communications with UPS lost: No status from UPS. Aug 19 09:07:26 ProLiant megatec[1126]: Communications with UPS

Thanks for your reply Hyouko, these are the actual not working parameters: driver.parameter.offdelay: 60 driver.parameter.ondelay: 5 ups.delay.shutdown: 60 ups.delay.start: 300 and the UPS don't wake up after the whiteout.. My UPS is not so old :( Il 09/12/2013 16.04, hyouko at gmail.com ha scritto: > 2013/12/6 Fabio Cecamore <ceca_89 at hotmail.com>: >> Hi all, > Hi

Thanks for suggetions and keep me indumb about making of Debian packages:D I will try this package "nut_2.2.0-2_i386.deb" One little questionm, shoud I use newmge-shut driver? - my ups is quite old - more then 3 years, connected through serial cable. >> PS: Arjen de Korte suspected something was wrong around my "heater" load, >> for now I have used two 150W lamps

Hello, I encountered a problem with my APC Smart-UPS 750, connected via USB, using newhidups. Without any reason, nut/upsmon shut down my PC: >>> Oct 13 12:57:08 echo kernel: usb 2-9.1.1: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 8 ret -71 Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost on battery Oct 13 12:57:12 echo upsmon[5060]: UPS smart750@localhost

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:

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 Jun 29, 2013, at 9:45 AM, Mike. wrote: > On 6/29/2013 at 9:14 AM Mike. 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

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"

On 6/29/2013 at 9:59 AM Charles Lepple wrote: |On Jun 29, 2013, at 9:45 AM, Mike. wrote: | |> On 6/29/2013 at 9:14 AM Mike. 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" |>

l?rdagen den 29 juni 2013 11.28.14 skrev Mike.: 8<------------------snip--------------------- Hi Mike, > > Thanks for the quick reply. > > I checked the log file (which, admittedly, I should have done before I > posted about the problem :) ). > > Here's the command and the corresponding log message: > > # upsrw -u au -p ap -s outlet.1.delay.shutdown=12

Hi all, after a change of UPS (to Atlantis Host Power 851) I began to use the new driver blazer_usb and compared to old one (blazer used with serial connection) I noted more CPU use and errors in dmesg: [...] [256712.584370] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8 ret -110 [256789.640795] usb 4-5: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt 33 rq 9 len 8

On 6/29/2013 at 9:14 AM Mike. 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

I went to the link to test the power off if the battery gets to low. Here is what I got on the command line. root at odroid-u2:/etc/nut# /usr/local/ups/bin/upsdrvctl -t shutdown -bash: /usr/local/ups/bin/upsdrvctl: No such file or directory root at odroid-u2:/etc/nut# find / -name upsdrvctl /sbin/upsdrvctl ^C root at odroid-u2:/etc/nut# /sbin/upsdrvctl -t shutdown Network UPS Tools - UPS driver

Hi all, (Keeping this in a separate email from my first one so as to not make it horribly complex) I've connected my Belkin F6C120auUNV UPS to my Debian 7.7.0 host via USB, and found that the usbhid-ups driver will not start unless I use the option '-u root', even when starting this driver as root: root at monitor:/lib/nut# cat /etc/nut/ups.conf [greything] driver =

l?rdagen den 29 juni 2013 15.22.44 skrev Mike.: 8<-------------snip----------------- Sorry for the delay. > Here is the console output of bcmxcp with -DDD specified: > > > [snip] > 13.721204 Auto delay on: 2 > > 13.721243 send_command: (4 bytes) => ab 01 35 1f > 13.821127 send_command: (4 bytes) => ab 01 33 21 > 13.920982

Hi, I'm trying to get a sweex ups working with nut on debian sarge. This one: http://www.sweex.com/producten.php?lang=1&%20sectie=&item=59&artikel=95 It's shipped with UPSmart and according to the compatibility list it should work with the genericups upstype=7 driver. But it doesn't. I get: mybox:/etc/nut# /etc/init.d/nut start Starting Network UPS Tools: (upsdrvctl