Nut upsuser - Feb 2021 - Why do ondelay and offdelay parameters break the NUT driver?

Hello everybody!

I use NUT in an environment like this:

1. OS Linux: Debian v.10.7 64 bit.
2. NUT v.2.7.4.
3. Install by Debian packages from repository Debian:
  - nut-client/stable,now 2.7.4-8 amd64
  - nut-server/stable,now 2.7.4-8 amd64
  - nut/stable,now 2.7.4-8 all
4. UPS "POWERCOM KIN-625AP"
Manufacturer : POWERCOM
https://www.upspowercom.com

5. Without "ondelay" and "offdelay" parameters, the NUT
driver works fine:

~# systemctl status nut-driver.service
● nut-driver.service - Network UPS Tools - power device driver controller
   Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor
preset: enabled)
   Active: active (running) since Thu 2021-02-11 17:05:33 EET; 10min ago
  Process: 526 ExecStart=/sbin/upsdrvctl start (code=exited, status=0/SUCCESS)
 Main PID: 557 (powercom)
    Tasks: 1 (limit: 4915)
   Memory: 1008.0K
   CGroup: /system.slice/nut-driver.service
           └─557 /lib/nut/powercom -a myserver

фев 11 17:05:33 myserver systemd[1]: Starting Network UPS Tools - power device
driver controller.
фев 11 17:05:33 myserver upsdrvctl[526]: using 'battery.charge' to set
battery low state
фев 11 17:05:33 myserver upsdrvctl[526]: Network UPS Tools - UPS driver
controller 2.7.4
фев 11 17:05:33 myserver powercom[557]: Startup successful
фев 11 17:05:33 myserver systemd[1]: Started Network UPS Tools - power device
driver controller.

However, if I add these parameters to /etc/nut/ups.conf

then the NUT driver fails:

 systemctl status nut-driver.service 
● nut-driver.service - Network UPS Tools - power device driver controller
   Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor
preset: enabled)
   Active: failed (Result: exit-code) since Thu 2021-02-11 17:23:48 EET; 1min
27s ago
  Process: 531 ExecStart=/sbin/upsdrvctl start (code=exited, status=0/SUCCESS)
  Process: 537 ExecStop=/sbin/upsdrvctl stop (code=exited, status=1/FAILURE)

фев 11 17:23:48 myserver upsdrvctl[531]: Network UPS Tools - PowerCom protocol
UPS driver 0.17 (2.7.4)
фев 11 17:23:48 myserver upsdrvctl[531]: Fatal error: 'ondelay' is not a
valid variable name for this driver.
фев 11 17:23:48 myserver upsdrvctl[531]: Look in the man page or call this
driver with -h for a list of
фев 11 17:23:48 myserver upsdrvctl[531]: valid variable names and flags.
фев 11 17:23:48 myserver upsdrvctl[531]: Network UPS Tools - UPS driver
controller 2.7.4
фев 11 17:23:48 myserver upsdrvctl[537]: Can't open
/var/run/nut/powercom-ttyS0.pid: No such file or directory
фев 11 17:23:48 myserver upsdrvctl[537]: Network UPS Tools - UPS driver
controller 2.7.4
фев 11 17:23:48 myserver systemd[1]: nut-driver.service: Control process exited,
code=exited, status=1/FAILURE
фев 11 17:23:48 myserver systemd[1]: nut-driver.service: Failed with result
'exit-code'.
фев 11 17:23:48 myserver systemd[1]: Failed to start Network UPS Tools - power
device driver controller.

Please tell me how to fix this bug?

Best regards,
-- 
nut-user <shilov at extmail.info>

On Feb 11, 2021, at 10:45 AM, Shilov via Nut-upsuser <nut-upsuser at
alioth-lists.debian.net> wrote:
> 
>           └─557 /lib/nut/powercom -a myserver
> 
...
> фев 11 17:23:48 myserver upsdrvctl[531]: Network UPS Tools - PowerCom
protocol UPS driver 0.17 (2.7.4)
> фев 11 17:23:48 myserver upsdrvctl[531]: Fatal error: 'ondelay' is
not a valid variable name for this driver.
> фев 11 17:23:48 myserver upsdrvctl[531]: Look in the man page or call this
driver with -h for a list of
> фев 11 17:23:48 myserver upsdrvctl[531]: valid variable names and flags.
As the message says, "ondelay" is not a valid option for that
particular driver:

https://networkupstools.org/docs/man/powercom.html

There seems to be a strange syntax for the equivalent of "offdelay" -
search for "shutdownArguments".