Archive > 20.7 Legacy Series
Unbound service routinely stopping/crashing following 20.7.7 update
Szeraax:
I have been experiencing Unbound freezing every 3-7 days roughly since I applied the 20.7.7 update earlier this year. I am currently on 21.7.1. I have not done any pkg revert or additions for unbound.
My unbound config includes several domain overrides and host overrides, but nothing else really.
Today it died again and looking at my system log, I see several hundred lines of getswapspace(\d+): failed like so:
--- Code: ---2021-08-30T18:34:21 kernel swap_pager_getswapspace(31): failed
2021-08-30T18:34:21 kernel swap_pager_getswapspace(9): failed
2021-08-30T18:34:21 kernel swap_pager_getswapspace(18): failed
2021-08-30T18:34:21 kernel swap_pager_getswapspace(24): failed
2021-08-30T18:34:21 kernel swap_pager_getswapspace(32): failed
2021-08-30T18:34:21 kernel swap_pager_getswapspace(24): failed
2021-08-30T18:34:21 kernel swap_pager_getswapspace(32): failed
2021-08-30T18:34:21 kernel swap_pager_getswapspace(16): failed
2021-08-30T18:34:21 kernel swap_pager_getswapspace(32): failed
2021-08-30T18:34:21 kernel swap_pager_getswapspace(32): failed
2021-08-30T18:34:20 kernel pid 35220 (php-cgi), jid 0, uid 0, was killed: out of swap space
2021-08-30T18:34:15 kernel swap_pager_getswapspace(20): failed
2021-08-30T18:34:15 kernel swap_pager_getswapspace(4): failed
2021-08-30T18:34:15 kernel swap_pager_getswapspace(18): failed
2021-08-30T18:34:15 kernel swap_pager_getswapspace(20): failed
2021-08-30T18:34:15 kernel swap_pager_getswapspace(22): failed
2021-08-30T18:34:15 kernel swap_pager_getswapspace(25): failed
2021-08-30T18:34:15 kernel swap_pager_getswapspace(4): failed
--- End code ---
I'm running OpnSense in a HyperV vm with dynamic ram set, though, I never see it changing from the 1024 that is set on initial boot in VM manager:
I ended up doing the monit restart solution rather than revert pkg so at least my internet will get back online quick after DNS dies. Hope this info helps someone else in the future.
franco:
Memory ballooning (?) probably won't work in FreeBSD 12.1 yet. As far as crashes go these are almost always related to DoH and probably a particular DoH provider? Make sure to post your setup in your "me too's" as this gives hints as to what to do: maybe don't use that provider or DoH in general or find a DoH alternative like dnscrypt-proxy.
Cheers,
Franco
Szeraax:
Oh interesting. I didnt think that would be relevant since i dont have that plugin installed even. Just dnssec support enabled and only dns server is 1.1.1.3 (cloudflare family node).
Here are my plugins:
(Note: several of these installed plugins say misconfigured because they were installed before I did the Configuration import from my previously OpnSense router. They all seem to work fine though)
It would make sense if FreeBSD doesn't know how to handle dynamic ram for it to use up all space instead of accepting the host requests to increase its RAM dynamically.
Seems like these started happening after I installed sensei when trying to see if that could help me figure out why Unbound kept crashing. Maybe I'll uninstall it and see if those out of swap errors go away.
Mks:
--- Quote from: LouieLouie on January 12, 2021, 04:17:05 am ---
--- Quote from: dcol on January 07, 2021, 06:52:05 pm ---Would be nice if someone could post a Monit How-To for core services like unbound. and restart the service.
--- End quote ---
(See attachment) Here you go.
--- End quote ---
Thanks, but what is the correct "Service Test Setting" to apply?
br
franco:
Oh in that case you are right and Unbound may just go out of memory during normal operation... no crashes or problems, just too few resources globally.
I would set it to 2 GB without Sensei and 4 GB with Sensei at least.
Cheers,
Franco
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version