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

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" report?  Does "upsdrvctl
shutdown" have any
effect?  Make sure that your box is not taking power from the UPS when 
you do this.  Load the UPS with a table lamp so that you see any shutdown.

Roger

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  0.0  0.0  45352  1728 ?        S    00:10   0:00
/lib/nut/upsmon
   root     17118  0.0  0.0   2444   680 ?        S    00:42   0:00 
upstart-udev-bridge --daemon
   root     17184  0.0  0.0   2568   484 ?        S    00:42   0:00 
upstart-socket-bridge --daemon
   davide   22002  0.0  0.0  11124   988 pts/0    S+   11:02   0:00 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(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.

-- Davide

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