similar to: upsrw: "Unexpected response from upsd: ERR READONLY"

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:

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

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

Hello, my Atlantis UPS (model on "subject" line) fails to cycle off the outlet power after a power failure on the mains followed by an automatic shutdown of the computer. The UPS simply remains always on, preventing the computer from restarting. ** Setup: ** Nut version 2.7.2 Nut driver blazer_usb Linux 4.1.1 The config files are pretty default; the peculiar customization is

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 What miss ? Thank you!

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

On 12/06/2013 10:57 PM, Kris Jordan wrote: > [...] > (*) Some UPS's do provide extra options to determine when they will > restore power to load. That would be a nice feature. Anyway, it is a strange thing that I can set the waiting time for power to be restored if main power comes back before offdelay has elapsed, but the UPS ignores this setting if main power comes back after

On Wed, 8 Jan 2020, Gene Heskett wrote: > On Wednesday 08 January 2020 06:44:03 Roger Price wrote: >> I am surprised that there is no ups.delay.start for this UPS. > My new APC Smart-UPS_1500 doesn't have it either. Hello Gene, The NUT 2.7.2 "device dump library" entry for the APC Smart-UPS 1500 at https://networkupstools.org/ddl/APC/Smart-UPS_1500.html shows an entry

Angel Tsankov wrote, On 12/24/2013 1:22 AM: > On 12/06/2013 10:57 PM, Kris Jordan wrote: > > [...] >> (*) Some UPS's do provide extra options to determine when they will >> restore power to load. > > That would be a nice feature. > > Anyway, it is a strange thing that I can set the waiting time for > power to be restored if main power comes back before

Hello, I'm having problems when trying to execute an deep battery test. UPS Model: PowerWalker VI 1000. root at HP-Opreon:/# upscmd PowerWalker at localhost test.battery.start.deep Username (root): admin Password: Unexpected response from upsd: ERR ACCESS-DENIED /etc/hosts.allow: <code> # /etc/hosts.allow: list of hosts that are allowed to access the system. # See

I'm trying to better understand OffDelay and OnDelay: http://networkupstools.org/docs/man/usbhid-ups.html#_extra_arguments My server requires ~3? minutes to shut itself down. Considering this I'm comfortable setting OffDelay to 300 (five minutes). How does this work in conjunction with the UPS hardware? Does NUT immediately send a command to the UPS to wait for 300 seconds and then shut

Hi all. UPS is Eaton 5SC 500i. I tested three solutions: 1. swap "usbhid-ups -a qnapups" with "usbhid-ups -a qnapups -k" Result: server shutdown, but ups does not shut off! 2. run prog with params "upsmon -c fsd" Result: server shutdown, but ups does not shut off! 3. run prog "upscmd -u name -p passwd qnapups shutdown.return" and next

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

On Sunday 08 December 2019 21:48:03 Charles Lepple wrote: > On Dec 7, 2019, at 7:01 PM, Gene Heskett <gheskett at shentel.net> wrote: > > What driver do I now put in /etc/nut/ups.conf? hid-generic doesn't > > seem to want to talk to it, and the original name _(usbhid-ups) > > doesn't work from new mobo. Oh wait, I can't spell. But that didn't > >

Hi, I'm struggling with a peculiar issue with my UPS. After a power outage, the devices powered by it properly shut down via nut. Eventually, the UPS also goes down. Power is still out, however, roughly 40 seconds after the UPS shut down, it turns back on and it starts supplying power to the load, thus turning back on the devices attached to it. This is obviously not something I want. In

Hello list, just a quick email to report that the following UPS was supported (mostly) out of the box: Model: PowerWalker VI 850 LCD Driver: blazer_usb upsc Output (please note I have manually populated the high and low voltages): battery.charge: 100 battery.voltage: 13.50 battery.voltage.high: 13.5 battery.voltage.low: 10 battery.voltage.nominal: 12.0 beeper.status: enabled device.type: ups

Are there any plans to allow us to specify UPS variables in ups.conf, eg: [evo_s_3000] driver = usbhid-ups port = auto desc = "Eaton Evolution S 3000" vendorid = 0463 productid = ffff ups.delay.shutdown = 120 ups.delay.start = 130 The reason I ask is that I'm using FreeBSD & gmirror and need to extend the gracetime

An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200217/b486de30/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: usbhid.zip Type: application/zip Size: 4031 bytes Desc: not available URL:

Hello, I am having trouble getting upsd to start. I am using the Debian NUT packages version 2.0.3 (current in Debian/sid). I am using the newhidups driver with an APC Back-UPS BR 800. The init.d script wasn't functioning, so I backtracked to running upsd manually and I get: foxstar:/etc/nut# upsd -u root Network UPS Tools upsd 2.0.3 Can't connect to UPS [foxstarups] (newhidups-auto):