search for: instcmds

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 |

On 10/14/2015 10:17 AM, Roger Price wrote: > What does "ps aux | grep ups" report? ps aux | grep ups nut 2902 0.0 0.0 20588 1140 ? Ss 00:10 0:02 /lib/nut/nutdrv_qx -a myups nut 2946 0.0 0.0 37632 1428 ? Ss 00:10 0:00 /lib/nut/upsd root 2970 0.0 0.0 37616 1436 ? Ss 00:10 0:00 /lib/nut/upsmon root 2973

.../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, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - L...

On Jun 22, 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

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 scrubb...

...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.qu...

Hi I am considering adding support in the bcmxcp driver for the following commands available in bcmxcp specification : #define PW_UPS_ON .. /* UPS on command. length 1-2 */ #define PW_UPS_ON_TIME .. /* Scheduled UPS on in n minutes. length 3-4 */ #define PW_UPS_ON_AT_TIME .. /* Schedule UPS on at specified date and time. length 7-8 */ #define

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:

Device manufacturer: Fideltronik INIGO Device name: Viper 1200 Device type: UPS Bus type: USB WWW: http://fideltronikinigo.com/viper/viper-1200/ " nut-scanner -U" output: [nutdev1] driver = "blazer_usb" port = "auto" vendorid = "0001" productid = "0000" product = "MEC0003" vendor =

Hi, They say one should never argue with people that know more than you, so please bear with me. On 2013/10/24 09:47 PM, hyouko at gmail.com wrote: > The driver is expecting either 'ACK' or no reply at all in case of > success and the command itself echoed back in case of errors. > On the other hand, your UPS replies '(ACK' in case of success and > '(NAK' on

Hi, There seems to be a problem turning of the inverter on a Mecer online 1000VA UPS. OS: Debian Wheezy Nut: Installed via apt - version 2.6.4-2.3 Debug output from driver. root at proxmox1:~# /lib/nut/blazer_usb -DDDDD -a mecer -k Network UPS Tools - Megatec/Q1 protocol USB driver 0.08 (2.6.4) 0.000000 send_to_all: SETINFO driver.parameter.port "auto" 0.000023

Hello, we have a problem using APC Back-UPS CS 500 (connected via USB, usbhid-ups-apc) and UPS-NUT. We've tried different Versions of UPS-NUT (2.2.1 and 2.2.2), including the latest from SVN (28th November 2008). We've also tried apcupsd, which works fine for our requirements, but we don't want use it. What we need is simple: The UPS should turn off after power loss and shutdown

It seems that the UPS I wrote in my previous mail uses the Megatec protocol, but does not support the S<n>R<m> "Shut Down and Restore" Command. This means that the server will shut down cleanly, but it will not boot automatically when the utility power comes back. There is another shutdown command according to the protocol description, although I do not really understand the

...for UPS to cut power. Will now halt. The PC turns off put UPS stays running until batteries run out. So I can see that the driver issues the command and thinks that it is "handled". Looking at it with higher debug level I can see that the driver reports a "USB no ACK" to these instcmds. Checking the USB with wireshark shows that this text string originated in the UPS, ie it is a text string returned in response to the instcmds. Looking closer at the USB descriptor it presents MEC0003 rather than the MEC0002 that I see all over the fora. So it would appear that there is a new va...

Hi Johan, The driver is expecting either 'ACK' or no reply at all in case of success and the command itself echoed back in case of errors. On the other hand, your UPS replies '(ACK' in case of success and '(NAK' on failure. So.. when the driver first tries to stop pending shutdowns and you get the 'operation not permitted' error, the driver interprets it as a

...er- 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. > > Or as instcmds = ALL, which also doesn't work, ACCESS-DENIED. > > Aha! Found it, very old version of upsmon.conf had gene as operayor, > not pi, but that didn't fix it until it had all been restarted, so a > quick battery test is underway. And it was quick, 15 secs OB. > > So a .deep i...

...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 MINSUPPLI...

...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