Nut upsuser - Oct 2015 - No power cycle after shutdown on Atlantis Land OnePower A03-S1001

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 myups shutdown.return 360
>
> These logs are reported in my second mail of this thread.
> Oct  6 19:03:07 debianBunker upsmon[3115]: UPS myups at localhost on
>      battery
> Oct  6 19:03:07 debianBunker upsd[2946]: Instant command: admin at
>      127.0.0.1 did shutdown.return with value "360" on myups
> Oct  6 19:03:07 debianBunker nutdrv_qx[2936]: instcmd(shutdown.return,
>      360)
> Oct  6 19:03:07 debianBunker nutdrv_qx[2936]: instcmd: FAILED
Is there any command in the list provided by "upscmd -l myups" which
is
accepted by this UPS?

Do the driver options -q or -D produce any further information about the 
failure?

Roger

On 10/14/2015 12:18 PM, Roger Price wrote:
> Is there any command in the list provided by "upscmd -l myups"
which is accepted
> by this UPS?
None of the command sin the list successfully completes, not even beeper.toggle.
My list:

   # upscmd -l myups
   Instant commands supported on UPS [myups]:

   beeper.toggle - Toggle the UPS beeper
   load.off - Turn off the load immediately
   load.on - Turn on the load immediately
   shutdown.return - Turn off the load and return when power is back
   shutdown.stayoff - Turn off the load and remain off
   shutdown.stop - Stop a shutdown in progress
   test.battery.start - Start a battery test
   test.battery.start.deep - Start a deep battery test
   test.battery.start.quick - Start a quick battery test
   test.battery.stop - Stop the battery test


I added -q and -D to /etc/nut/ups.conf, as:

   [myups]
     driver = nutdrv_qx -D -q
     port = auto

I couldn't find more info on where to append driver parameters, not sure if 
that's the correct way. After that, I restarted nut with:

   # service nut-server restart
   # service nut-client restart

Now, issuing any command, such as

   upscmd -u admin -p mypass myups load.off

returns "OK" on console, but /var/log/syslog logs:

   Oct 14 15:30:52 debianBunker upsd[2976]: Instant command: admin at 127.0.0.1
did
load.off on myups
   Oct 14 15:30:52 debianBunker nutdrv_qx[2951]: instcmd(load.off, [NULL])
   Oct 14 15:30:52 debianBunker nutdrv_qx[2951]: instcmd: FAILED


-- Davide

On Wed, 14 Oct 2015, Davide Baldini wrote:
>> Is there any command in the list provided by "upscmd -l
myups" which is
>> accepted by this UPS?
>
> None of the command sin the list successfully completes, not even 
> beeper.toggle.
It looks as if the problem is more general than turning off the UPS. The 
command mechanism is broken.
> I added -q and -D to /etc/nut/ups.conf, as:
>
>  [myups]
>    driver = nutdrv_qx -D -q
>    port = auto
>
> I couldn't find more info on where to append driver parameters, not
sure if
> that's the correct way. After that, I restarted nut with:
>
>  # service nut-server restart
>  # service nut-client restart
My naive reading of function conf_args in common/upsconf.c is that only 
the form driver = something is seen, any additional parameters are 
ignored.

I'm not sure how to add a debugging option to a "service" call in 
Debian.  Is /etc/init.d/nut-client a Bash/Dash script?  Is it possible to 
add the option to the call of the driver in this script?

Roger