Bug 245114

Summary: dns/unbound: use daemon(8) to recover from crashes
Product: Ports & Packages Reporter: C <cm>
Component: Individual Port(s)Assignee: freebsd-ports-bugs (Nobody) <ports-bugs>
Status: Open ---    
Severity: Affects Only Me CC: jaap, lwhsu, pi
Priority: --- Flags: bugzilla: maintainer-feedback? (jaap)
Version: Latest   
Hardware: Any   
OS: Any   

Description C 2020-03-27 20:00:11 UTC

other rc scripts for services use daemon(8) with "-r" to recover from daemon crashes automatically without requiring admin intervention.

Today our unbound resolver (v1.10) crashed but since unbound does not make use of daemon it stayed down until we started it manually - which is worse than it could be.

Please add daemon to unbound's rc script to recover from crashes automatically.

for an example on how to use daemon:
Comment 1 Li-Wen Hsu freebsd_committer 2020-07-03 17:28:14 UTC
ping for maintainer feedback.
Comment 2 Jaap Akkerhuis 2020-07-06 13:41:35 UTC
(In reply to Li-Wen Hsu from comment #1)
Ah, forgot abut this feature request.

It would actually be more beneficial to find out why unbound-s crashing. I'm not sure whether it is a good idea to blindly restart a crashing process. Let me thonk about this.
Comment 3 C 2020-11-16 11:05:21 UTC
I agree that it is important to find and solve the root cause of the crash but in the moment of the crash the most important thing is to get the service back up again. Using log monitoring we are not "blind" and notice nonetheless that the crash happened and can have a manual look at the crash logs.
Comment 4 C 2021-02-20 13:06:25 UTC
Hi Jaap,

due to recent unbound crashes I was wondering whether you have any update on this?

Comment 5 Jaap Akkerhuis 2021-02-20 14:55:10 UTC
(In reply to C from comment #4)

Nope, I haven't any update nor I had time time to implement this.

However, if you make make an option to the existing version of the rc
script to use daemon(8), I'm happy to add it to the port.