[2355] pid 59276 (upsc), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
[2365] pid 76306 (upsc), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
[2375] pid 96545 (upsc), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
[2383] pid 11941 (upsc), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
[2385] pid 15230 (upsc), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
[2395] pid 32978 (upsc), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
[2403] pid 45958 (upsc), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
[2405] pid 50289 (upsc), jid 0, uid 0: exited on signal 11 (no core dump - bad address)
Interestingly the command does work, it only crashes on exit:
root@opnsense:~ # upsc ups
battery.charge: 100
battery.current: 0.90
battery.date: 07/20/2024
battery.runtime: 1560
battery.runtime.elapsed: 0
battery.voltage: 27.10
battery.voltage.nominal: 24
device.contact: hostmaster@hausen.com
device.description: UPS SNMP Card
[...]
ups.status: OL
ups.temperature: 34
ups.test.date: 05/09/2026
ups.test.result: Ok
Segmentation fault
Kind regards,
Patrick
I guess that's about https://github.com/opnsense/ports/commit/ffa95e659d223da -- we had 2.8.3 in our tree before which would still work?
# opnsense-revert -r 26.1.7 nut
Cheers,
Franco
Da, back to workink.
Ok not sure what to do here, but I'll see if there is an upstream patch. Rolling back the version is iffy.
Cheers,
Franco
Quote"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT
Stealing that! :-)
Did a quick trace of 2.8.5 and it appears to use /proc, whereas 2.8.3 doesn't. I don't know if this has anything to do with it.