similar to: Getting Error Using upscmd

On Wed, 14 Oct 2015, Davide Baldini wrote: > upsdrvctl shutdown > ... > instcmd(shutdown.return, [NULL]) > instcmd: FAILED > Shutdown failed! > Driver failed to start (exit status=1) > > This time /var/log/syslog doesn't register anything about the UPS after > issuing the command above. Instead, It logged some errors after a > upscmd -u admin -p mypass

On Monday 22 June 2020 09:50:50 Larry Fahnoe wrote: > On Mon, Jun 22, 2020 at 8:27 AM Gene Heskett <gheskett at shentel.net> wrote: > > > On Jun 22, 2020, at 8:52 AM, Gene Heskett wrote: > > > > pi at rpi4:~ $ upscmd myups *test.battery.start.quick* > > > > Username (pi): > > > > Password: > > > > Unexpected response from upsd:

On Monday 22 June 2020 08:19:15 Charles Lepple wrote: > > On Jun 18, 2020, at 12:39 PM, Mike Dillinger wrote: > > > > ups.test.result: No test initiated > > I’d recommend a battery test. Starting the test via the front panel > should be sufficient, or you might be able to do it with upscmd. from man pi at rpi4:~ $ upscmd -l myups Instant commands supported on UPS

On Monday 22 June 2020 15:26:23 Larry Fahnoe wrote: > On Mon, Jun 22, 2020 at 12:26 PM Gene Heskett <gheskett at shentel.net> wrote: > > So I just edited /etc/nut/upsd.users to add both the commands it > > claims to have but get this response to either: > > > > pi at rpi4:~ $ upscmd myups test.battery.start.quick > > Username (pi): pi > > Password:

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

On Monday 22 June 2020 09:18:29 Charles Lepple wrote: > On Jun 22, 2020, at 8:52 AM, Gene Heskett wrote: > > pi at rpi4:~ $ upscmd myups test.battery.start.quick > > Username (pi): > > Password: > > Unexpected response from upsd: ERR ACCESS-DENIED > > > > Looking at /etc/nut/uspd.users, I (me, pi) should be able to do > > that. ??? > > Hi Gene,

On Wed, 14 Oct 2015, Davide Baldini wrote: > the full output of upsc ${myups} is at https://pastebin.mozilla.org/8849188 ; > in particular: > > ups.delay.shutdown: 30 > ups.delay.start: 180 > > However, the UPS does not shut down, not immediately nor well after the > timeout of the command: upscmd -u admin -p mypass myups shutdown.return 360 What does "ps aux |

I didn't want to sign up for the nut-devs list or create a git account just to provide this information, so I hope posting this info here is OK... I just bought a Cyber Power Systems EC750G UPS for use as a spare. Here are some info for it: ========================= upsc output: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime:

On 12/8/2016 10:37 PM, Charles Lepple wrote: > On Dec 8, 2016, at 1:34 PM, Mike wrote: >> >> I didn't want to sign up for the nut-devs list or create a git account >> just to provide this information, so I hope posting this info here is OK... > > Not a problem. (Both lists go into the same mailbox on my end.) The important part is the "HCL" subject so I

I compile nut with the voltronic-driver on my computer then I've copy the driver "/lib/nut/voltronic_ser" on the server. I can now shutdown the ups using "upscmd -u admin myups shutdown.return". My first question is, is it really ok to only take the driver whithout taking the whole package? I'm using upssched to shutdown server after 15mn on battery, the

I'm pretty sure, I've install pkg-config, but I will check it monday after my holliday. This is my test steps: - Shutting down nut-client (upsmon) - Only nut-server (driver + upsd) is running - upsmon.conf have been revert to normal shutdown, no upssched - upsc myups return ups stats then: upsmon -K -DDDDD, here is the output: kill: No such process UPS: myups at

Jim Klimov <jimklimov+nut at gmail.com> > > I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :) Hi: I got another ups for testing. so I test the new commit for both APC SRT3000XL and SMT2200RM2U. the results below: 1. I get the new attribute "ups.test.result" for

Jim Klimov <jimklimov+nut at gmail.com> > > I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :) Hi: I got another ups for testing. so I test the new commit for both APC SRT3000XL and SMT2200RM2U. the results below: 1. I get the new attribute "ups.test.result" for

I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :) Thanks in advance, Jim Klimov On Wed, Nov 22, 2023 at 3:20?PM Jim Klimov <jimklimov+nut at gmail.com> wrote: > Great! Thanks for the info, and hope the driver author can address the > nits (forwarding now...) > > Jim

I believe some fixes were applied to the branch since your report (most visibly, about battery time settings), are you in position to test how it behaves now? :) Thanks in advance, Jim Klimov On Wed, Nov 22, 2023 at 3:20?PM Jim Klimov <jimklimov+nut at gmail.com> wrote: > Great! Thanks for the info, and hope the driver author can address the > nits (forwarding now...) > > Jim

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

I?m wondering if what I have done is good : # get the source from github on my computer # autogen.sh # name=nut # ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man --libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name --with-statepath=/var/run/nut --with-altpidpath=/var/run/nut --with-drvpath=/lib/nut --with-pidpath=/var/run/$name

On Jul 31, 2013, at 9:07 AM, James HORLEY wrote: > I?m wondering if what I have done is good : > # get the source from github on my computer > # autogen.sh > # name=nut > # ./configure --prefix=/ --sysconfdir=/etc/$name --mandir=/usr/share/man > --libdir=/usr/lib --includedir=/usr/include --datadir=/usr/share/$name > --with-statepath=/var/run/nut

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

The nut ups daemons seem to be communicating with the UPS but upscmd gives me no joy. Running commands do nothing and produce no output. Using the web interface returns an authentication failure and that is the only clue I have. I believe I have everything setup correctly but it's not working. Can someone review this and give me clues as to what I should research next?