<div dir="auto">Sorry, I'm commuting now so will be concise :)<div dir="auto"><br></div><div dir="auto">Q1: definitions we aim to uphold are at <a href="https://networkupstools.org/docs/developer-guide.chunked/_variables.html">https://networkupstools.org/docs/developer-guide.chunked/_variables.html</a></div><div dir="auto"><br></div><div dir="auto">Q2: CUPS is Printing Service, see SAMBA. Not NUT :)</div><div dir="auto"><br></div><div dir="auto">Hope this helps,</div><div dir="auto">Jim Klimov</div><div dir="auto"><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Sat, Aug 22, 2026, 11:19 Eyal Lebedinsky via Nut-upsuser <<a href="mailto:nut-upsuser@alioth-lists.debian.net">nut-upsuser@alioth-lists.debian.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Q1) Where can I find a clear definition of the following attributes:<br>
ups.delay.shutdown: 20<br>
ups.delay.start: 30<br>
If it matters, the UPS is<br>
device.mfr: EATON<br>
device.model: Ellipse MAX 1500<br>
<br>
See a second question (Q2) at the end of this report.<br>
<br>
There was a power failure when I was not present.<br>
Aug 22 14:10:45 e7 nut-monitor[3158]: UPS ups@ups on battery<br>
Aug 22 14:33:07 e7 nut-server[3152]: Data for UPS [ups] is stale - check driver<br>
Aug 22 14:33:12 e7 nut-monitor[3158]: Communications with UPS ups@ups lost<br>
Aug 22 14:33:32 e7 nut-monitor[3158]: Exiting upsmon program after initiating shutdown<br>
Aug 22 14:33:27 e7 nut-monitor[3158]: Executing automatic power-fail shutdown<br>
...<br>
Aug 22 14:33:45 e7 systemd-journald[556]: Journal stopped<br>
<br>
I assume that the server was shut down at this point, until I booted it<br>
Aug 22 15:25:36 e7 kernel: Command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-7.1.8-200.fc44.x86_64 ...<br>
<br>
When shut down the ups reported 38% charge. When it booted the ups reported zero charge.<br>
ups capacity is logged every minute:<br>
20260822141100 100<br>
20260822141200 97 wall power lost<br>
...<br>
20260822143200 40<br>
20260822143300 38 machine shuts down<br>
20260822152600 0 machine booted<br>
20260822152700 1<br>
<br>
What is the relationship between the battery charge and the timing of the shutdown.<br>
Maybe it is related to the UPS not sending data, which triggers the shutdown?<br>
<br>
The status of the UPS now (over 3.5h since charging started) is:<br>
<br>
$ date ; upsc ups<br>
Sat Aug 22 19:00:00 AEST 2026<br>
battery.charge: 87<br>
battery.charge.low: 20<br>
battery.runtime: 1745<br>
battery.type: PbAc<br>
device.mfr: EATON<br>
device.model: Ellipse MAX 1500<br>
device.serial: ADYL1000H<br>
device.type: ups<br>
driver.debug: 0<br>
driver.flag.allow_killpower: 0<br>
<a href="http://driver.name" rel="noreferrer noreferrer" target="_blank">driver.name</a>: usbhid-ups<br>
driver.parameter.interrupt_pipe_no_events_tolerance: -1<br>
driver.parameter.pollfreq: 30<br>
driver.parameter.pollinterval: 2<br>
driver.parameter.port: auto<br>
driver.parameter.synchronous: auto<br>
driver.state: updateinfo<br>
driver.version: 2.8.5<br>
driver.version.data: MGE HID 1.58<br>
driver.version.internal: 0.71<br>
driver.version.usb: libusb-1.0.30 (API: 0x0100010C)<br>
input.sensitivity: low<br>
input.transfer.boost.low: 185<br>
input.transfer.high: 285<br>
input.transfer.low: 150<br>
input.transfer.trim.high: 265<br>
input.voltage.extended: yes<br>
outlet.1.desc: PowerShare Outlet 1<br>
<a href="http://outlet.1.id" rel="noreferrer noreferrer" target="_blank">outlet.1.id</a>: 2<br>
outlet.1.status: on<br>
outlet.1.switchable: no<br>
outlet.desc: Main Outlet<br>
<a href="http://outlet.id" rel="noreferrer noreferrer" target="_blank">outlet.id</a>: 1<br>
outlet.switchable: no<br>
output.frequency.nominal: 50<br>
output.voltage: 230.0<br>
output.voltage.nominal: 230<br>
ups.beeper.status: enabled<br>
ups.delay.shutdown: 20<br>
ups.delay.start: 30<br>
ups.firmware: 5102AH<br>
ups.load: 6<br>
ups.mfr: EATON<br>
ups.model: Ellipse MAX 1500<br>
ups.power.nominal: 1500<br>
ups.productid: ffff<br>
ups.realpower: 72<br>
ups.serial: ADYL1000H<br>
ups.status: OL CHRG<br>
ups.timer.shutdown: -1<br>
ups.timer.start: -1<br>
ups.vendorid: 0463<br>
<br>
Q2) Probably related but also maybe expected. During shutdown I see this in the system log:<br>
<br>
Aug 22 14:33:36 e7 systemd[1]: Stopping cups.service - CUPS Scheduler...<br>
Aug 22 14:33:36 e7 cupsd[1467]: malloc(): smallbin double linked list corrupted<br>
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<br>
Aug 22 14:33:36 e7 systemd-coredump[3739844]: Process 1467 (cupsd) of user 0 terminated abnormally with signal 6/ABRT, processing...<br>
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<br>
<br>
I am running<br>
nut.x86_64 2.8.5-3.fc44 updates<br>
kernel<br>
7.1.8-200.fc44.x86_64<br>
<br>
-- <br>
Eyal at Home (<a href="mailto:eyal@eyal.emu.id.au" target="_blank" rel="noreferrer">eyal@eyal.emu.id.au</a>)<br>
<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank" rel="noreferrer">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote></div>