Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Nex VII

#1
Update from my side: the test kernel (26.7.6-hyperv) is installed on the Hyper-V Gen2 VM (host Xeon E-2236, 4 vCPU, 8 GB).

- Booted 2026-10-09 17:23 CEST, uptime now 2h02m.
- No "exited on signal" entries in System > Log Files > General since boot. With the stock 26.7.6 kernel, unbound was exiting on signal 11 every 6-12 minutes and syslog-ng twice.
- No log entries above Warning since boot; all services running.

Thanks for the quick fix, Franco!
#2
Thanks Franco.

Host: Intel Xeon E-2236, Hyper-V Gen 2 VM with 4 vCPUs and 8 GB static RAM.

What I did:
- opnsense-revert -r 26.7.5 opnsense
- opnsense-update -bk -r 26.7.4
- reboot at 20:58

Current versions: core 26.7.5, base 26.7.4, kernel 26.7.4.

Result: since the reboot (about 1 hour so far) there have been no "exited on signal" entries at all. Before, on 26.7.6, unbound crashed repeatedly, the last time at 20:41.

I'll keep monitoring and will report back here if any crash happens again.

Cheers
#3
Hi,
after upgrading from 26.7.5 to 26.7.6 today, unbound keeps crashing with signal 11, roughly every 6-15 minutes, both at startup and at runtime.

Environment:
- OPNsense 26.7.6 (amd64), VM on Hyper-V
- unbound 1.26.1, unchanged since 18/09 and stable until today
- Unbound with DNSSEC, prefetch, serve-expired, aggressive NSEC, forwarding (DoT); DHCP lease registration off; DNSBL off

Observed (kernel log):
- unbound: 14x "exited on signal 11" since the upgrade, e.g. 19:29, 19:35, 19:41, 19:53, 19:59, 20:10, 20:18
- syslog-ng: 2x signal 11 right after boot
- python3.13: 2x signal 6 (abort)
- No "exited on signal" entries at all in the logs of the previous 4 weeks (since 10/09)
- Unbound logs nothing before dying: the last lines are normal resolution activity. A reboot doesn't help.

Since several unrelated binaries started segfaulting right after the update, this looks like a regression in base/libs rather than in unbound itself. Is anyone else seeing this on 26.7.6? I can enable kern.coredump and provide a backtrace if useful.

Thanks