search for: instcmd

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 |

...grep ups > Does "upsdrvctl shutdown" have any effect? upsdrvctl shutdown Network UPS Tools - UPS driver controller 2.7.2 Network UPS Tools - Generic Q* USB/Serial driver 0.06 (2.7.2) USB communication driver 0.32 Using protocol: Megatec 0.01 Initiating UPS shutdown instcmd(shutdown.stop, [NULL]) instcmd: FAILED instcmd(shutdown.stop, [NULL]) instcmd: FAILED instcmd(shutdown.stop, [NULL]) instcmd: FAILED No shutdown pending instcmd(shutdown.return, [NULL]) instcmd: FAILED instcmd(shutdown.return, [NULL]) instcmd: FAILED instcmd(shutdow...

On Monday 22 June 2020 15:36:21 Charles Lepple wrote: > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote: > > So I just edited /etc/nut/upsd.users to add both the commands it > > claims to have but get this response to either: > > In your original example, you had multiple “instcmd =“ lines for one > user- I think the allowed commands all need to be listed on one > instcmd line. They are now # commented, and instcmds = ALL added in a new line. Made zero diff. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury,...

...2, 2020, at 3:36 PM, Charles Lepple wrote: > > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote: >> >> So I just edited /etc/nut/upsd.users to add both the commands it claims >> to have but get this response to either: > > In your original example, you had multiple “instcmd =“ lines for one user- I think the allowed commands all need to be listed on one instcmd line. Ignore this, I misremembered (and didn't read far enough down the URL I sent). Multiple allowed commands are specified with one command per instcmd.

During the last month, I've been integrating a Powerware 5115 into an embedded system by writing a custom NUT daemon. This work has gone quite well and NUT has been very helpful, but it sure would be nice to have some additional instcmds for the 5115. The bcmxcp driver comments mention "manuals for the BCM/XCP". I'm wondering if I could get a copy of those so that I might explore enhancing the bcmxcp drivers to support more instcmds. Thanks, Rich -------------- next part -------------- An HTML attachment was scrub...

...pi at rpi4:~ $ upscmd myups *test.battery.start.quick* > > > > Username (pi): > > > > Password: > > > > Unexpected response from upsd: ERR ACCESS-DENIED > > > > [pi] > > password = xxxxxxxxxxxxx > > instcmds = *test.battery.start* > > instcmds = test.battery.stop > > calibrate.start > > calibrate.stop > > Hi Gene, > > Looks like it might be that you're allowing test.battery.start but > executing test.battery.start.q...

...specified date and time. length 7-8 */ Possibly I would also like to add support for the following, but this might not make sense : #define PW_GO_TO_BYPASS .. /* Transfer load from inverter to bypass. length 1 or 3 */ But I do not currently know what name I should use for the "instcmd" for each of these. For the three "ON" commands, do you think it make sense to add "instcmd" for these ? In the other drivers, I only see "load.on". Is "load.on" a proper instcmd to use ? For example "load.on", "load.on.delayed", &...

While working on the mge-hid subdriver, I wanted to add the 'beeper.mute' command. Unfortunately, the description I intended to use was used already by the 'beeper.off' instcmd: CMDDESC beeper.off "Temporarily mute the UPS beeper" Now of course we could add another instcmd 'beeper.reallyoff', but instead I would prefer to bite the buller and do the following: CMDDESC beeper.off "Disable the UPS beeper" CMDDESC beeper.mute "Temporaril...

...08223 send: Q1 2.008233 command index: 0x03 2.239141 read: (226.2 226.2 226.2 0 50.0 27.7 25.0 00001001 beeper.toggle (Q) - if the beeper emits a beep at the time when command is issued the beep never ends... - the beeper can not be switched off if UPS is on line. 396.231354 instcmd(beeper.toggle, [NULL]) 396.231400 send: Q 396.231414 command index: 0x07 396.250914 read: UPS No Ack 396.250947 instcmd: FAILED load.off (S00R0000) - load are switched off after 30s, - "C" command will not break the shutdown. - nutdrv_qx output: http:...

...9;operation not permitted' error. In any case, this is actually considered to be a success by the code. This is not right. Code as follows: 418 /* 419 * If a command is invalid, it will be echoed back 420 */ 421 if (blazer_command(buf, buf, sizeof(buf)) > 0) { 422 upslogx(LOG_ERR, "instcmd: command [%s] failed", cmdname); 423 return STAT_INSTCMD_FAILED; 424 } 425 426 upslogx(LOG_INFO, "instcmd: command [%s] handled", cmdname); 427 return STAT_INSTCMD_HANDLED; As far as I understand the code line 421 tries to test for a 'comms failure' (e.g. driver disconnecti...

...s 0.031025 send_to_all: SETINFO ups.vendorid "0665" 0.031037 send_to_all: SETINFO ups.productid "5161" 0.031046 Initiating UPS shutdown 0.033050 send: C 1.033388 read: error sending control message: Operation not permitted 1.033404 instcmd: command [shutdown.stop] handled 1.038035 send: S.5R0003 1.109163 read: (ACK 1.109179 instcmd: command [shutdown.return] failed 1.111018 send: C 1.149165 read: (ACK 1.149180 instcmd: command [shutdown.stop] failed 1.151017 send: C 1.197111...

...art - Start testing the UPS panel test.panel.stop - Stop a UPS panel test The last lines of output from 'usbhid-ups -DDDD -a apc -k': Path: UPS.PowerSummary.AudibleAlarmControl, Type: Feature, ReportID: 0x14, Offset: 0, Size: 8, Value: 2.000000 Initiating UPS shutdown upsdrv_shutdown... instcmd(shutdown.return, [NULL]) find_nut_info: unknown info type: shutdown.return instcmd(load.on.delay, 5) find_nut_info: unknown info type: load.on.delay instcmd: info element unavailable load.on.delay instcmd(shutdown.reboot, [NULL]) Can't set Report 19: Broken pipe instcmd: FAILED Shutdown failed!...

...- ProductID: 0000 1.840674 - Manufacturer: unknown 1.840725 - Product: STD UPS MON V1.0 1.840783 - Serial Number: unknown 1.840836 - Bus: 004 1.840894 Trying to match device 1.840964 Device matches 1.842538 Initiating UPS shutdown 1.842607 instcmd(shutdown.stop, [NULL]) 1.842693 send: C 2.359574 received 3 (67) 2.359673 read: 2.359714 instcmd: command [shutdown.stop] failed 2.359763 instcmd(shutdown.stop, [NULL]) 2.359840 send: C 2.872594 received 3 (67) 2.872679 read: 2.872718 i...

...e (AMD64). OS/NUT are all the latest official release (as of last week) with NUT installed from packages. As the usb descriptor presents MEC (and the Fry's electronics) I chose to use the blazer_usb driver. All appears to work well excepting that the UPS does not appear to accept the shutdown instcmd to turn off the ups outputs at the end of the shutdown process. The UPS remains on until the batteries completely drain and it has to turn off to protect itself. Apart from that, reporting, messaging, shutdown process etc all works well. On shutdown I can see instcmd: command [shutdown.stop] han...

...end_to_all: SETINFO ups.vendorid "0665" > 0.031037 send_to_all: SETINFO ups.productid "5161" > 0.031046 Initiating UPS shutdown > 0.033050 send: C > 1.033388 read: error sending control message: Operation not permitted > 1.033404 instcmd: command [shutdown.stop] handled > 1.038035 send: S.5R0003 > 1.109163 read: (ACK > 1.109179 instcmd: command [shutdown.return] failed > 1.111018 send: C > 1.149165 read: (ACK > 1.149180 instcmd: command [shutdown.stop] failed > 1.151...

...ple wrote: > > > On Jun 22, 2020, at 1:26 PM, Gene Heskett wrote: > > >> So I just edited /etc/nut/upsd.users to add both the commands it > > >> claims to have but get this response to either: > > > > > > In your original example, you had multiple “instcmd =“ lines for > > > one user- I think the allowed commands all need to be listed on > > > one instcmd line. > > > > Ignore this, I misremembered (and didn't read far enough down the > > URL I sent). Multiple allowed commands are specified with one > > co...

...ls -la /dev/bus/usb/001/ [cut] crw-rw-r-- 1 root nut 189, 1 2008-09-24 08:41 002 Config files: tux:/home/effem# cat /etc/nut/ups.conf [APC-RS800] driver = usbhid-ups port = auto tux:/home/effem# cat /etc/nut/upsd.users [admin] password = password1 allowfrom = localhost actions = SET instcmds = ALL [nut] password = 1234 allowfrom = localhost upsmon master tux:/home/effem# cat /etc/nut/upsd.conf ACL all 0.0.0.0/0 ACL localhost 127.0.0.1/32 ACCEPT localhost REJECT all tux:/home/effem# cat /etc/nut/upsmon.conf RUN_AS_USER nut MONITOR APC-RS800 at localhost 1 nut 1234 master MINSUPPL...

...should be able to do > > that. ??? > > Hi Gene, > > You have a [pi] section in upsd.users, then? If it's one of the > example users from the man page or comments, you'll need to use that > name with upscmd, or change upsd.users. > > Plus, you'll need "instcmds = all" (or the specific test command) in > the section for that NUT user. > > Ref: https://networkupstools.org/docs/man/upsd.users.html > <https://networkupstools.org/docs/man/upsd.users.html> I think its all there. Heresa snip, edited [pi] password...

On Jul 2, 2013, at 5:16 PM, Kjell Claesson wrote: >> I hope other people can also test this. >> >> Regards >> Alf Hogemark > > Due to some crashes on the disks and lack of time I don't have the git on the > pc now. But maybe some other can commit this. I'd like to ask people to specifically try the bcmxcp branch on GitHub - it includes some changes