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!




Today at 01:03:42 AM #1 Last Edit: Today at 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-