At least the "shutdown.return requires a parameter" part *may* be a regression of the new "sdcommands" change in v2.8.3,though I don't think older code passed any. Maybe something got lost in mass-edit changes though.
Can you please double-check with 2.8.2 if its older approach to UPS shutdown behaved better? Jim Klimov On Tue, May 6, 2025, 00:41 Alexey Korobeinikov <[email protected]> wrote: > Hi, my UPS Model Powercom BNT400AP ( made 2017.12 ) on Linux Devuan > Daedalus and NUT v2.8.3 (install from source tarball with "configure > --with-usb --with-user=nut --with-group=nut --with-libusb=1.0 > --with-statepath=/run/nut --with-pidpath=/run/nut" options) didn't > shutdown itself after OS is shuting down by signal of UPS battary is low. > > ... 0.184242 Initiating UPS [UPS] shutdown > 0.184257 [D1] loop_shutdown_commands: call > do_loop_shutdown_commands() with driver-default sdcommands > 0.184267 [D1] Starting > do_loop_shutdown_commands(shudown.default), call depth 1... > 0.184280 [D1] upsdrv_shutdown... > 0.184289 [D1] Starting > do_loop_shutdown_commands(shutdown.return,shutdown.reboot,load.off.delay,shutdown.stayoff), > > call depth 2... > 0.184299 [D1] instcmd(shutdown.return, [NULL]) > 0.184313 [D3] instcmd: using Path > 'UPS.PowerSummary.DelayBeforehutdown' > 0.184321 [D2] instcmd: shutdown.return requires an explicit > parameter > > 0.184331 [D1] instcmd(shutdown.reboot, [NULL]) > 0.184348 [D2] find_nut_info: unknown info type: shutdown.reboot > 0.184358 [D3] instcmd: cmdname 'shutdown.reboot' not found; > checking for alternatives > 0.184371 [D2] instcmd: info element unavailable shutdown.reboot > > 0.184387 [D1] instcmd(load.off.delay, [NULL]) > 0.184398 [D2] find_nut_info: unknown info type: load.off.delay > 0.184407 [D3] instcmd: cmdname 'load.off.delay' not found; > checking for alternatives > 0.184418 [D2] instcmd: info element unavailable load.off.delay > > 0.184428 [D1] instcmd(shutdown.stayoff, [NULL]) > 0.184438 [D3] instcmd: using Path > 'UPS.PowerSummary.DelayBeforehutdown' > 0.184449 [D2] instcmd: shutdown.stayoff requires an explicit > parameter > > 0.184462 [D1] Ending > do_loop_shutdown_commands(shutdown.return,shutdown.reboot,load.off.delay,shutdown.stayoff), > > call > depth 2: return-code 2 > 0.184471 Shutdown failed! > 0.184483 [D1] set_exit_flag: raising exit flag due to signal -1 > 0.184493 [D1] do_loop_shutdown_commands(): command > 'shutdown.default' was handled successfully > 0.184502 [D1] Ending do_loop_shutdown_commands(shutdown.default), > call depth 1: return-code 0 > 0.184512 UPS [UPS]: shutdown request was successful with > 'shutdown.default' > 0.184523 [D1] set_exit_flag: raising exit flag due to > programmatic abort: EXIT_FAILURE > 0.184540 [D1] upsdrv_cleanup... > 0.184899 [D1] upsnotify: failed to notify about state > NOTIFY_STATE_STOPPING: no notification tech defined, will not spam more > about it > 0.184936 [D1] On systems without service units, consider `export > NUT_QUIET_INIT_UPSNOTIFY=true` > > I try to use "powercom_sdcmd_byte_order_fallback" option, with same effect. > > Wat's wrong with my UPS/NUT ? > Thank You! > > -- > Oleksii Korobeinikov > > > > > _______________________________________________ > Nut-upsuser mailing list > [email protected] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser >
_______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
