OPNsense Forum

English Forums => 26.7, 26.10 Series => Topic started by: Nex VII on October 08, 2026, 08:38:22 PM

Title: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: Nex VII on October 08, 2026, 08:38:22 PM
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
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: franco on October 08, 2026, 08:44:48 PM
I have the feeling this is about https://github.com/opnsense/src/issues/297 which was supposed to be solved with 26.7.6, not cause more regressions on previously unaffected installs.

Can you try to confirm by downgrading the kernel?

# opnsense-update -zkr 26.7.4
(reboot)


Cheers,
Franco
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: Nex VII on October 08, 2026, 09:58:33 PM
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
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: mnaim on October 08, 2026, 11:07:51 PM
Same problem on Hyper-V.
Other physical machines are ok, no Unbound crashes.
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: Monviech (Cedrik) on October 09, 2026, 07:00:57 AM
I let AI run over this, take with a grain of salt (could, would...)

Two potential issues in sys/dev/hyperv/vmbus/hyperv_mmu.c:

* In hv_vm_tlb_flush(), (end == 0 || ...) > max_gvas compares a Boolean against max_gvas, making the condition always false and preventing full TLB flushes.
* In hv_flush_tlb_others_ex(), fill_gva_list() receives end, start instead of start, end, potentially invalidating the wrong page.

Both could leave stale TLB entries and explain the crashes.
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: franco on October 09, 2026, 08:22:36 AM
@Nex VII

Can you lock the kernel at 26.7.4 and update the rest back to 26.7.6? It would help narrowing this down before building a kernel that has the relevant commit reverted.


Thanks,
Franco
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: franco on October 09, 2026, 08:31:45 AM
@Monviech, yes both of these appear to be wrong...

https://github.com/opnsense/src/commit/412e76211e74ab
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: Mabub on October 09, 2026, 08:37:49 AM
Hi,

I'm seeing the same thing on Hyper-V, though less frequently than described here.

Environment:

OPNsense 26.7.6-amd64, FreeBSD 15.1-RELEASE-p4, OpenSSL 3.5.9
Virtualized on Hyper-V (host CPU: AMD EPYC 4584PX), VM with 8 GB RAM
Unbound 1.26.1 (since 18/09), Python module with dnsbl_module loaded
[Upgraded to 26.7.6 on: ...]

What I observe:

Today, 2026-10-09 04:15:53, kernel log:
pid 19272 (unbound), jid 0, uid 59: exited on signal 11 (no core dump - denied by kern.coredump)
The VM had rebooted at about 04:10 and Unbound started cleanly at 04:10:55. It crashed roughly 5 minutes later.
The resolver log shows nothing unusual before the crash. The last line is dnsbl_module: successfully opened pipe at 04:11:05, then silence until "Closing logger".
Earlier unclean death on 2026-10-04 at 03:01:31: the resolver log shows "Closing logger" without the usual "service stopped", and no restart afterwards. Unbound was apparently down until I rebooted on 2026-10-09 01:16, so about 5 days without DNS resolution from OPNsense. I can't confirm a signal 11 for that one, since my kernel log excerpt has no matching entry.
I restarted Unbound manually after noticing it was stopped on the dashboard.

I have not downgraded the kernel yet. Reverting to 26.7.5...

Thanks
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: franco on October 09, 2026, 08:42:50 AM
I've built a test kernel with the mentioned commit:

# opnsense-update -zkr 26.7.6-hyperv


Cheers,
Franco
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: mnaim on October 09, 2026, 01:06:15 PM
Updated to 26.7.6 again.
Run opnsense-update -zkr 26.7.6-hyperv

After 5min it seams ok (older kernel already crashed few processes after 5min)
Will keep eye on it little bit longer.
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: franco on October 09, 2026, 01:32:01 PM
Good news!  Thanks for testing.  :)

We may have to move to 26.7.7 early next week to ship this fix for everyone.


Cheers,
Franco
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: CK_beats on October 09, 2026, 01:37:58 PM
That might have happened to me during the update as well.
Here is my post: https://forum.opnsense.org/index.php?topic=53121.0

I managed to spot an error entry in the Unbound logs.
Also in the logs via the console.

Do I understand this correctly: You updated everything to the latest version except Unbound?
Was it locked and left at the previous version?
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: franco on October 09, 2026, 01:41:53 PM
This isn't about Unbound. It's about a Hyper-V patch in 26.7.6 that fixes a boot issue on som AMD architecture but apparently causes these userspace segfaults.  Reverting the kernel to 26.7.4 or trying the hyperv kernel mentioned above should help.... it would help more if you could also confirm the hyperv kernel working.


Cheers,
Franco
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: CK_beats on October 09, 2026, 02:07:29 PM
Quote from: franco on October 09, 2026, 08:42:50 AMI've built a test kernel with the mentioned commit:

# opnsense-update -zkr 26.7.6-hyperv


I'm now using the kernel you updated!
It's running beautifully!
Many thanks for the quick fix!

Unbound is now remaining stable (for the time being); everything is running as it should!


Is there any way I can help out with logs or anything else?
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: franco on October 09, 2026, 02:15:02 PM
Nope, great, that's all we need to know.


Thanks,
Franco
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: mnaim on October 09, 2026, 05:06:42 PM
Update - fix still holds.

Thanks Franco!
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: franco on October 09, 2026, 06:18:52 PM
Great to hear.  We'll pick this up in a small .7 early next week.


Cheers,
Franco
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: Nex VII on October 09, 2026, 07:29:33 PM
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!
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: franco on October 09, 2026, 07:53:04 PM
Yay, great.  :)
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: drobins1976 on October 10, 2026, 12:52:56 PM
I can confirm a similar problem with OPNsense 26.7.6 on Hyper-V.

My setup is a Windows 11 Hyper-V host with an AMD Ryzen 7 8745HS, and an OPNsense VM with 2 vCPUs and 4 GB RAM. Unbound has DNSSEC and the Python DNS blocklist module enabled.

After updating on 9 October, Unbound repeatedly exited with signal 11. The WAN connection remained up, but DNS requests to the router timed out. Direct internet access by IP still worked.

These are the crash timestamps recorded in the kernel log (BST):

- 09:01:57
- 09:02:03
- 09:39:15
- 09:49:58
- 09:50:15
- 10:40:20
- 10:44:44

The kernel messages were of this form:

    pid 52844 (unbound), jid 0, uid 59: exited on signal 11 (no core dump - denied by kern.coredump)

Restarting Unbound only restored DNS temporarily. Restarting the Windows host also did not stop the crashes; Unbound crashed again after the VM came back up.

I rolled back ONLY the kernel using:

    opnsense-update -kr 26.7.4

The kernel installed successfully, then I rebooted OPNsense. The application and packages remained on 26.7.6. No resolver, blocklist, firewall or VM settings were changed as part of this recovery.

Before rollback:

    FreeBSD 15.1-RELEASE-p4 stable/26.7-n284150-0a7d52ef8757

After rollback:

    FreeBSD 15.1-RELEASE-p3 stable/26.7-n283949-083dc7025377

As of 10 October at 11:27 BST, the VM has been up for approximately 24 hours 34 minutes. Unbound is running, DNS lookups through the router succeed, and HTTPS through the router works. No Unbound signal-11 entries appear in the current system log, although it has rotated, so I cannot claim complete log coverage for the whole period.

One additional point: the normal update offer now includes both opnsense 26.7.6_3 and kernel 26.7.6, which would undo this workaround. I have not installed it.

This seems consistent with the Hyper-V kernel regression discussed here. I have not tested the 26.7.6-hyperv test kernel, and I have no crash backtrace because core dumps were disabled.
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: 3dat on October 12, 2026, 05:40:34 PM
Hi all,
I am very new to OPNsense but already a great fan :)

I think I can confirm a similar issue to 26.7.6_3 on Hyper-V, 2025 Server on DELL R630 with E5-2637v3 CPU
My Syslog-ng is not willing to start. Restart leads to:

Error opening file for reading; filename='/dev/klog', error='Device busy (16)'
Error initializong message pipeline; plugin_name='file', location='usr/local/etc/syslog.ng.conf:18:5'
/usr/local/etc/rc.d/syslog.ng: Warning: failed to start syslog_ng

What I did:
Reinstall syslog_ng

Will try with the hyperv update

Many thanks
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: magnust on October 12, 2026, 06:50:01 PM
On Hyper-V here too, same problem. Just did the "opnsense-update -zkr 26.7.6-hyperv" and hope for the best :-D
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: magnust on October 13, 2026, 08:02:24 AM
Quote from: magnust on October 12, 2026, 06:50:01 PMOn Hyper-V here too, same problem. Just did the "opnsense-update -zkr 26.7.6-hyperv" and hope for the best :-D
Looking good so far
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: Canardo96 on October 13, 2026, 08:23:57 AM
Hi all,

I am troubleshooting recurring Unbound crashes on OPNsense 26.7.6_3 running under Microsoft Hyper-V.

The error is:

pid XXXXX (unbound), jid 0, uid 59: exited on signal 11
(no core dump - sugid process denied by kern.sugid_coredump)

I previously had several stability problems on this OPNsense VM, including Zenarmor/netmap and syslog-ng issues.

To eliminate configuration corruption and other variables, I completely abandoned that VM.

I created a new Hyper-V VM, performed a clean OPNsense installation and manually rebuilt the configuration. No configuration backup from the previous installation was restored.

The good news:
- Zenarmor is now stable
- No previous netmap problems
- syslog-ng is stable
- The firewall itself is operating normally

Unfortunately, Unbound has started crashing with signal 11 again.

Environment:
- OPNsense 26.7.6_3
- FreeBSD 15.1-RELEASE-p4
- Microsoft Hyper-V
- 4 vCPU
- ~12 GB RAM
- hn0/hn1
- Zenarmor 2.7

Has anyone seen recurring Unbound SIGSEGV crashes on OPNsense 26.7.x under Hyper-V?

Since the problem returned on a clean VM without restoring the old configuration, I am especially interested in what debugging information I should collect to determine the cause.

Thanks,
Maxim
Title: Re: 26.7.6: unbound (and syslog-ng) segfault with signal 11 after upgrade (Hyper-V)
Post by: franco on October 13, 2026, 09:03:22 AM
There's a test kernel and 26.7.7 should fix this later today. You don't have to repost an analysis without reading the thread.


Cheers,
Franco