New XG-7100 crash after unbound configuration



  • I'm trying to troubleshoot another issue, and in the process was making some changes to Unbound. It seems whenever I make a change (ex: toggle DNSSEC support, add/remove an interface) the whole box crashes. I can't log in, not even via SSH. The last thing I see though is a kernel swap_pager: out of swap space error. I have to hard reboot then.

    Memory usually hovers around 85%. The config on this box was copied from an SG-3100. I am using pfBlockerNG with several DNSBL feeds as well as TLD enabled.

    I realize this may not just be DNS related so I can repost if necessary.

    I want to add that I am seeing that the unbound service is restarting often. Logs for the curious;

    Sep 9 12:11:24 	unbound 	36218:0 	debug: duplicate acl address ignored.
    Sep 9 12:11:22 	unbound 	36218:0 	notice: Restart of unbound 1.9.1.
    Sep 9 12:11:22 	unbound 	36218:0 	debug: cache memory msg=66072 rrset=66072 infra=8057 val=66288
    Sep 9 12:11:22 	unbound 	36218:0 	info: mesh has 1 recursion states (1 with reply, 0 detached), 1 waiting replies, 0 recursion replies sent, 0 replies dropped, 0 states jostled out
    Sep 9 12:11:22 	unbound 	36218:0 	info: server stats for thread 3: requestlist max 0 avg 0 exceeded 0 jostled 0
    Sep 9 12:11:22 	unbound 	36218:0 	info: server stats for thread 3: 1 queries, 0 answers from cache, 1 recursions, 0 prefetch, 0 rejected by ip ratelimiting
    Sep 9 12:11:22 	unbound 	36218:0 	debug: cache memory msg=66072 rrset=66072 infra=8057 val=66288
    Sep 9 12:11:22 	unbound 	36218:0 	info: mesh has 1 recursion states (1 with reply, 0 detached), 1 waiting replies, 0 recursion replies sent, 0 replies dropped, 0 states jostled out
    Sep 9 12:11:22 	unbound 	36218:0 	info: server stats for thread 2: requestlist max 0 avg 0 exceeded 0 jostled 0
    Sep 9 12:11:22 	unbound 	36218:0 	info: server stats for thread 2: 1 queries, 0 answers from cache, 1 recursions, 0 prefetch, 0 rejected by ip ratelimiting
    Sep 9 12:11:22 	unbound 	36218:0 	debug: cache memory msg=66072 rrset=66072 infra=8057 val=66288
    Sep 9 12:11:22 	unbound 	36218:0 	info: mesh has 1 recursion states (1 with reply, 0 detached), 2 waiting replies, 0 recursion replies sent, 0 replies dropped, 0 states jostled out
    Sep 9 12:11:22 	unbound 	36218:0 	info: server stats for thread 1: requestlist max 1 avg 0.5 exceeded 0 jostled 0
    Sep 9 12:11:22 	unbound 	36218:0 	info: server stats for thread 1: 2 queries, 0 answers from cache, 2 recursions, 0 prefetch, 0 rejected by ip ratelimiting
    Sep 9 12:11:22 	unbound 	36218:0 	debug: cache memory msg=66072 rrset=66072 infra=8057 val=66288
    Sep 9 12:11:22 	unbound 	36218:0 	info: mesh has 0 recursion states (0 with reply, 0 detached), 0 waiting replies, 0 recursion replies sent, 0 replies dropped, 0 states jostled out
    Sep 9 12:11:22 	unbound 	36218:0 	info: server stats for thread 0: requestlist max 0 avg 0 exceeded 0 jostled 0
    Sep 9 12:11:22 	unbound 	36218:0 	info: server stats for thread 0: 0 queries, 0 answers from cache, 0 recursions, 0 prefetch, 0 rejected by ip ratelimiting
    Sep 9 12:11:22 	unbound 	36218:0 	info: service stopped (unbound 1.9.1).
    

  • Netgate Administrator

    Yeah that's not likely to be Unbound. It's exhausting the RAM and swap space (if you have an SSD) so something is using far more than expected.
    Try running top -aSH at the command line to see what is using it if this is still an issue.

    Steve


Log in to reply