Unbound stopps suddenly

Started by MiRei, July 17, 2026, 09:11:04 AM

Previous topic - Next topic
Good Morning,

thanks for the new 26.7!
OPNSense is a truly great product; thank you very much for maintaining and
further developing it.

The upgrade to 26.7 went smoothly. After two days of use, I've now noticed
Unbound crashing for the second time, with the following error message:

 (unbound), jid 0, uid 59, was killed: failed to reclaim memory

After that, I can manually restart Unbound, and the system continues to run normally.

Any ideas?

Thanks a lot!




July 29, 2026, 01:03:42 AM #1 Last Edit: July 29, 2026, 01:05:50 AM by fab
Hello!

I'm having a similar problem. unbound suddenly stops and doesn't restart with the following log message:

<6>[86420] pid 4171 (unbound), jid 0, uid 59: exited on signal 11 (no core dump - denied by kern.coredump)
It has already happened a few times after the 26.7 upgrade. I also can start it manually after that has happened.

Is there at least some way, I can make it restart automatically again after exiting?

Best wishes,
-fab-

Not sure if this is related or a different issue, but for me Unbound is crashing after rebooting OPNsense.  It seems to happen with about 50% of reboots.  Unbound starts running for a minute or so and then crashes.  It works after I manually restart the service.  I'm on 26.7.2.

The problem still exists.
I have created a workarround with a little script, which
was running every 15min via cron. The scripts restarts
unbound if necessary and logs the restart in
/root/unbound_restart.log:

my_unbound.sh:

   my_unbound=$(pluginctl -s unbound status)

   if [ "$my_unbound" == "unbound is not running."  ]
   then
     pluginctl -s unbound restart
     echo $(pluginctl -s unbound status)
     echo $(date) >> /root/unbound_restart.log
   fi

This works for me.

I haven't experienced this.   how many DNSBL do you have added?

I have Steven Black and OISD
DEC740 > USW-Pro-8-PoE> U6-Enterprise
Dec670. Retired / backup device

EasyList
EasyPrivacy
Steven Black List
YoYo List

Unbound crashes only after reboot in 50%.
No more issues after restarting unbound.

Today at 01:06:23 PM #6 Last Edit: Today at 01:31:02 PM by DEC740airp414user
so upon reboot.  no traffic is passing. or after a few minutes after the reboot?


I've been running 26.7 for 3-4 days now with no issues,  I figured id test for. you
I have a snapshot of business edition I went back to.  ran for a bit.  then restored back to a 26.7 snap shot.   I am not getting that error message.
I am using dns over tls to nextdns.  and the blocklists above with no tweaks to unbound.  more or less out of box
DEC740 > USW-Pro-8-PoE> U6-Enterprise
Dec670. Retired / backup device

a few minutes after reboot