[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.
I am seeing the same behavior since upgrading to 26.1.8.
I also appreciated the technical debt comment. Thanks for the laugh.
OT for now:
Quote from: Patrick M. Hausen on May 12, 2026, 05:06:40 PMStealing that! :-)
Quote from: julsssark on May 12, 2026, 08:06:26 PMI also appreciated the technical debt comment. Thanks for the laugh.
Sure, it was that type of response too good not to share. :)
Cheers,
Franco
same issue with the upgrade but work around worked - thank you
Per the release notes there was no change to the nut package. So what are you all even talking about? :P
Quote from: OPNenthu on May 13, 2026, 03:17:59 AMPer the release notes there was no change to the nut package. So what are you all even talking about? :P
With 2.8.5 the NUT widget reports an error.
Listed are the tail ends of ktrace for upsc in 2.8.3 & 2.8.5.
upsc - NUT 2.8.3
QuoteVAR SUA1000I ups.temperature "027.0"
VAR SUA1000I ups.test."
51229 upsc RET read 64/0x40
51229 upsc CALL write(1,33258138185728,18)
51229 upsc GIO fd 1 wrote 18 bytes
"ups.status: OL LB
"
51229 upsc RET write 18/0x12
51229 upsc CALL write(1,33258138185728,23)
51229 upsc GIO fd 1 wrote 23 bytes
"ups.temperature: 027.0
"
51229 upsc RET write 23/0x17
51229 upsc CALL select(4,34899832816,0,0,34899832800)
51229 upsc RET select 1
51229 upsc CALL read(3,33258138055320,64)
51229 upsc GIO fd 3 read 64 bytes
"interval "0"
VAR SUA1000I ups.test.result "NO"
END LIST VAR SUA1"
51229 upsc RET read 64/0x40
51229 upsc CALL write(1,33258138185728,21)
51229 upsc GIO fd 1 wrote 21 bytes
"ups.test.interval: 0
"
51229 upsc RET write 21/0x15
51229 upsc CALL write(1,33258138185728,20)
51229 upsc GIO fd 1 wrote 20 bytes
"ups.test.result: NO
"
51229 upsc RET write 20/0x14
51229 upsc CALL select(4,34899832816,0,0,34899832800)
51229 upsc RET select 1
51229 upsc CALL read(3,33258138055320,64)
51229 upsc GIO fd 3 read 5 bytes
"000I
"
51229 upsc RET read 5
51229 upsc CALL select(4,0,34899833232,0,34899833216)
51229 upsc RET select 1
51229 upsc CALL write(3,34918619370,7)
51229 upsc GIO fd 3 wrote 7 bytes
"LOGOUT
"
51229 upsc RET write 7
51229 upsc CALL shutdown(3,SHUT_RDWR)
51229 upsc RET shutdown 0
51229 upsc CALL close(3)
51229 upsc RET close 0
51229 upsc CALL exit(0)
upsc - NUT 2.8.5
QuoteVAR SUA1000I ups.temperature "027.0"
VAR SUA1000I ups.test."
93660 upsc RET read 64/0x40
93660 upsc CALL write(1,59259719200768,18)
93660 upsc GIO fd 1 wrote 18 bytes
"ups.status: OL LB
"
93660 upsc RET write 18/0x12
93660 upsc CALL write(1,59259719200768,23)
93660 upsc GIO fd 1 wrote 23 bytes
"ups.temperature: 027.0
"
93660 upsc RET write 23/0x17
93660 upsc CALL select(4,34912627584,0,0,34912627568)
93660 upsc RET select 1
93660 upsc CALL read(3,59259719086744,64)
93660 upsc GIO fd 3 read 64 bytes
"interval "0"
VAR SUA1000I ups.test.result "NO"
END LIST VAR SUA1"
93660 upsc RET read 64/0x40
93660 upsc CALL write(1,59259719200768,21)
93660 upsc GIO fd 1 wrote 21 bytes
"ups.test.interval: 0
"
93660 upsc RET write 21/0x15
93660 upsc CALL write(1,59259719200768,20)
93660 upsc GIO fd 1 wrote 20 bytes
"ups.test.result: NO
"
93660 upsc RET write 20/0x14
93660 upsc CALL select(4,34912627584,0,0,34912627568)
93660 upsc RET select 1
93660 upsc CALL read(3,59259719086744,64)
93660 upsc GIO fd 3 read 5 bytes
"000I
"
93660 upsc RET read 5
93660 upsc CALL getpid
93660 upsc RET getpid 93660/0x16ddc
93660 upsc CALL fstatat(AT_FDCWD,2106259,34912628176,0)
93660 upsc NAMI "/proc"
93660 upsc STRU struct stat {dev=5509020405254355969, ino=538, mode=040555, nlink=2, uid=0, gid=0, rdev=0, atime=1769520096, mtime=1769520096, ctime=1770272166.850398000, birthtime=1769520096, size=2, blksize=4096, blocks=1, flags=0x800 }
93660 upsc RET fstatat 0
93660 upsc CALL fstatat(AT_FDCWD,34912628400,34912628176,0x200<AT_SYMLINK_NOFOLLOW>)
93660 upsc NAMI "/proc/93660/exe"
93660 upsc RET fstatat -1 errno 2 No such file or directory
93660 upsc CALL fstatat(AT_FDCWD,34912628400,34912628176,0x200<AT_SYMLINK_NOFOLLOW>)
93660 upsc NAMI "/proc/93660/file"
93660 upsc RET fstatat -1 errno 2 No such file or directory
93660 upsc CALL fstatat(AT_FDCWD,34912628400,34912628176,0)
93660 upsc NAMI "/proc/93660/cmdline"
93660 upsc RET fstatat -1 errno 2 No such file or directory
93660 upsc CALL fstatat(AT_FDCWD,34912628400,34912628176,0)
93660 upsc NAMI "/proc/93660/stat"
93660 upsc RET fstatat -1 errno 2 No such file or directory
93660 upsc CALL getpid
93660 upsc RET getpid 93660/0x16ddc
93660 upsc CALL fstatat(AT_FDCWD,34933438876,34912628176,0)
93660 upsc NAMI "/proc"
93660 upsc STRU struct stat {dev=5509020405254355969, ino=538, mode=040555, nlink=2, uid=0, gid=0, rdev=0, atime=1769520096, mtime=1769520096, ctime=1770272166.850398000, birthtime=1769520096, size=2, blksize=4096, blocks=1, flags=0x800 }
93660 upsc RET fstatat 0
93660 upsc CALL fstatat(AT_FDCWD,34912628400,34912628176,0x200<AT_SYMLINK_NOFOLLOW>)
93660 upsc NAMI "/proc/93660/exe"
93660 upsc RET fstatat -1 errno 2 No such file or directory
93660 upsc CALL fstatat(AT_FDCWD,34912628400,34912628176,0x200<AT_SYMLINK_NOFOLLOW>)
93660 upsc NAMI "/proc/93660/file"
93660 upsc RET fstatat -1 errno 2 No such file or directory
93660 upsc CALL fstatat(AT_FDCWD,34912628400,34912628176,0)
93660 upsc NAMI "/proc/93660/cmdline"
93660 upsc RET fstatat -1 errno 2 No such file or directory
93660 upsc CALL fstatat(AT_FDCWD,34912628400,34912628176,0)
93660 upsc NAMI "/proc/93660/stat"
93660 upsc RET fstatat -1 errno 2 No such file or directory
93660 upsc CALL select(4,0,34912628592,0,34912628576)
93660 upsc RET select 1
93660 upsc CALL write(3,34933446671,7)
93660 upsc GIO fd 3 wrote 7 bytes
"LOGOUT
"
93660 upsc RET write 7
93660 upsc CALL select(4,34912628592,0,0,34912628576)
93660 upsc RET select 1
93660 upsc CALL read(3,34912628784,512)
93660 upsc GIO fd 3 read 11 bytes
"OK Goodbye
"
93660 upsc RET read 11/0xb
93660 upsc CALL shutdown(3,SHUT_RDWR)
93660 upsc RET shutdown 0
93660 upsc CALL close(3)
93660 upsc RET close 0
93660 upsc PSIG SIGSEGV SIG_DFL code=SEGV_MAPERR
Quote from: OPNenthu on May 13, 2026, 03:17:59 AMPer the release notes there was no change to the nut package. So what are you all even talking about? :P
The FreeBSD port/package was updated and now crashes.
Plugin dependency software changes are not documented in release notes.
I can't find anything either upstream or FreeBSD ports at the moment so that means this workaround is required for the time being:
# opnsense-revert -r 26.1.7 nut
Cheers,
Franco
I had to reinstall my opnsense due to some hw failure.
When I now try to revert back to the working nut version, it seems to install the latest again:
opnsense-revert -r 26.1.7 nut
Fetching nut.pkg: .... done
Verifying signature with trusted certificate pkg.opnsense.org.20260120... done
nut-2.8.3: already unlocked
Installing nut-2.8.3...
package nut is already installed, forced install
===> Creating groups
Using existing group 'nut'
Using existing group 'dialer'
===> Creating users
Using existing user 'nut'
Extracting nut-2.8.3: 100%
Any change to get the working version back running? Is the package anywhere for download?
2.8.3 is not the latest version.
My fault. sorry, it's running fine now, just had to restart the service once again.
Working well now.