[Nut-upsuser] What is the meaning of ups.delay.*

[Eyal Lebedinsky]

Q1) Where can I find a clear definition of the following attributes:
	ups.delay.shutdown: 20
	ups.delay.start: 30
If it matters, the UPS is
	device.mfr: EATON
	device.model: Ellipse MAX 1500

See a second question (Q2) at the end of this report.

There was a power failure when I was not present.
	Aug 22 14:10:45 e7 nut-monitor[3158]: UPS ups at ups on battery
	Aug 22 14:33:07 e7 nut-server[3152]: Data for UPS [ups] is stale - check driver
	Aug 22 14:33:12 e7 nut-monitor[3158]: Communications with UPS ups at ups lost
	Aug 22 14:33:32 e7 nut-monitor[3158]: Exiting upsmon program after initiating shutdown
	Aug 22 14:33:27 e7 nut-monitor[3158]: Executing automatic power-fail shutdown
	...
	Aug 22 14:33:45 e7 systemd-journald[556]: Journal stopped

I assume that the server was shut down at this point, until I booted it
	Aug 22 15:25:36 e7 kernel: Command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-7.1.8-200.fc44.x86_64 ...

When shut down the ups reported 38% charge. When it booted the ups reported zero charge.
ups capacity is logged every minute:
	20260822141100 100
	20260822141200 97	wall power lost
	...
	20260822143200 40
	20260822143300 38	machine shuts down
	20260822152600 0	machine booted
	20260822152700 1

What is the relationship between the battery charge and the timing of the shutdown.
Maybe it is related to the UPS not sending data, which triggers the shutdown?

The status of the UPS now (over 3.5h since charging started) is:

$ date ; upsc ups
Sat Aug 22 19:00:00 AEST 2026
battery.charge: 87
battery.charge.low: 20
battery.runtime: 1745
battery.type: PbAc
device.mfr: EATON
device.model: Ellipse MAX 1500
device.serial: ADYL1000H
device.type: ups
driver.debug: 0
driver.flag.allow_killpower: 0
driver.name: usbhid-ups
driver.parameter.interrupt_pipe_no_events_tolerance: -1
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: auto
driver.state: updateinfo
driver.version: 2.8.5
driver.version.data: MGE HID 1.58
driver.version.internal: 0.71
driver.version.usb: libusb-1.0.30 (API: 0x0100010C)
input.sensitivity: low
input.transfer.boost.low: 185
input.transfer.high: 285
input.transfer.low: 150
input.transfer.trim.high: 265
input.voltage.extended: yes
outlet.1.desc: PowerShare Outlet 1
outlet.1.id: 2
outlet.1.status: on
outlet.1.switchable: no
outlet.desc: Main Outlet
outlet.id: 1
outlet.switchable: no
output.frequency.nominal: 50
output.voltage: 230.0
output.voltage.nominal: 230
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.firmware: 5102AH
ups.load: 6
ups.mfr: EATON
ups.model: Ellipse MAX 1500
ups.power.nominal: 1500
ups.productid: ffff
ups.realpower: 72
ups.serial: ADYL1000H
ups.status: OL CHRG
ups.timer.shutdown: -1
ups.timer.start: -1
ups.vendorid: 0463

Q2) Probably related but also maybe expected. During shutdown I see this in the system log:

Aug 22 14:33:36 e7 systemd[1]: Stopping cups.service - CUPS Scheduler...
Aug 22 14:33:36 e7 cupsd[1467]: malloc(): smallbin double linked list corrupted
Aug 22 14:33:36 e7 audit[1467]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=1467 comm="cupsd" exe="/usr/bin/cupsd" sig=6 res=1
Aug 22 14:33:36 e7 systemd-coredump[3739844]: Process 1467 (cupsd) of user 0 terminated abnormally with signal 6/ABRT, processing...
Aug 22 14:33:36 e7 kernel: audit: type=1701 audit(1787373216.957:17617): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=1467 comm="cupsd" exe="/usr/bin/cupsd" sig=6 res=1

I am running
	nut.x86_64 2.8.5-3.fc44 updates
kernel
	7.1.8-200.fc44.x86_64

-- 
Eyal at Home (eyal at eyal.emu.id.au)