After upgrade to 2.5.0 unbound crashing randomly
-
I discovered that the unbound process is crashing from time to time after I upgraded to 2.5.0 yesterday.
unbound-checkconf: no errors in /usr/local/etc/unbound/unbound.conf
Feb 20 19:02:36 nixtraut kernel: pid 9903 (unbound), jid 0, uid 59: exited on signal 11 Feb 20 19:02:37 nixtraut dhcpleases[2070]: Could not deliver signal HUP to process 9903: No such process. Feb 20 19:04:32 nixtraut dhcpleases[42865]: Could not deliver signal HUP to process 9903: No such process.
Every log file entrie regarding the
(unbound), jid 0, uid 59: exited on signal 11
comes after the dhcpleases message. Maybe it has something to do with the DHCP Server ? I could not reproduce the crash. after starting the service again, its working some time (hours). I'm on ipv4
Any one else discovered this behavior ?
-
@maars-loonga
This solution seems to be working for me. -
@making_sense_of_pfsense said in After upgrade to 2.5.0 unbound crashing randomly:
@maars-loonga
This solution seems to be working for me.@Making_sense_of_pfSense
Thank you for this hint. Indeed, this solution fixed the issue.
Thank you very much -
I have the same exact issue !! it happened after upgrading pfSense from 2.4.x to 2.5.0
-
try unticking "dhcp registration".
-
@chrcoluk I tried what you suggested and it's being stable for the last 10 hours...
do you think it's a bug?Thanks
-
@deadsoul If it is staying down potentially yes.
DHCP registration will reload unbound every time a dhcp device connects or lease expires, this includes things like phones and consoles so can be quite frequent, generally I recommend to people to disable that option, there is another one for static dhcp which you can keep enabled.
-
@making_sense_of_pfsense
48 hours later. I can confirm this also fixed it for me. Thanks! -
@deadsoul said in After upgrade to 2.5.0 unbound crashing randomly:
@chrcoluk I tried what you suggested and it's being stable for the last 10 hours...
do you think it's a bug?Thanks
No worries.