OPNsense Forum

Archive => 18.1 Legacy Series => Topic started by: elektroinside on April 08, 2018, 10:02:58 pm

Title: Unbound crashed
Post by: elektroinside on April 08, 2018, 10:02:58 pm
I wasn't doing anything spectacular, i was working via a rdp connection when everything went dark, suddenly no more internet (apparently). When logging into the WebGUI, i noticed Unbound wasn't running anymore.

I found these in the logs:

Code: [Select]
Apr  8 21:35:04 gateway configd.py: [23ab9b35-a78b-4362-9cc8-d36317cc3d9d] Reloading filter
Apr  8 21:35:05 gateway configd.py: [d871e2ee-e679-4c7e-8d69-c522201e12b3] generate template OPNsense/Filter
Apr  8 21:35:05 gateway configd.py: generate template container OPNsense/Filter
Apr  8 21:35:05 gateway configd.py: [c640a92f-1db9-4516-b542-a8806bd48fc3] refresh url table aliases
Apr  8 21:35:16 gateway kernel: pid 19657 (unbound), uid 59: exited on signal 11
Apr  8 21:39:29 gateway configd.py: [eb29b026-4b4a-436b-b35a-81b9f13bd71e] updating dyndns WAN2_DHCP

What just happened? Did anybody notice anything similar?
First time i ever noticed this. Restarting Unbound got things working again.
Title: Re: Unbound crashed
Post by: franco on April 09, 2018, 06:28:01 pm
Hi there,

Maybe OOM kill? Check the Unbound log too if this happens again.


Cheers,
Franco
Title: Re: Unbound crashed
Post by: elektroinside on April 09, 2018, 07:34:44 pm
Unlikely, unless something is leaking, crashed and freed up the mem, but you never know.. i did check the Unbound logs, found nothing, but i was in a hurry, so maybe i missed something.

I'll get back to this if it happens again with more details.

Thanks!

Title: Re: Unbound crashed
Post by: franco on April 09, 2018, 08:30:55 pm
Okay, thanks so far. :)
Title: Re: Unbound crashed
Post by: elektroinside on April 17, 2018, 06:22:01 pm
So... crashed again... also while RDP-ing :)

This time, I found this in the logs:

Code: [Select]
Apr 17 19:11:18 gateway unbound: [90027:1] error: could not SSL_new crypto error:14FFF0E4:SSL routines:(UNKNOWN)SSL_internal:ssl ctx has no default ssl version
Apr 17 19:11:18 gateway unbound: [90027:1] info: error sending query to auth server 9.9.9.9 port 853
Apr 17 19:11:18 gateway unbound: [90027:1] error: could not SSL_new crypto error:14FFF0E4:SSL routines:(UNKNOWN)SSL_internal:ssl ctx has no default ssl version
Apr 17 19:11:18 gateway unbound: [90027:1] info: error sending query to auth server 9.9.9.9 port 853
Apr 17 19:11:18 gateway unbound: [90027:1] error: could not SSL_new crypto error:14FFF0E4:SSL routines:(UNKNOWN)SSL_internal:ssl ctx has no default ssl version
Apr 17 19:11:18 gateway unbound: [90027:1] info: error sending query to auth server 9.9.9.9 port 853

And the same error as before in system:
Apr 17 19:11:18 gateway kernel: pid 90027 (unbound), uid 59: exited on signal 11
Title: Re: Unbound crashed
Post by: elektroinside on April 20, 2018, 02:16:56 pm
So am I the only one with this problem?
I disabled IDPS, curious if it will crash again...
Title: Re: Unbound crashed
Post by: Evil_Sense on April 22, 2018, 02:40:32 am
So am I the only one with this problem?
I disabled IDPS, curious if it will crash again...
I have the same issue but related to the DNS-TLS guide (with LibreSSL).

I just checked the errors I had when testing DNS-TLS against 9.9.9.9, they are exactly the same.
Title: Re: Unbound crashed
Post by: elektroinside on April 23, 2018, 01:20:02 pm
Hmm.. ok, so it's not an isolated incident.
Well, I don't know what's next. Maybe opening a bug on Github. I'll do this later today.

Thanks!