Maintained by: NLnet Labs

[Unbound-users] Unbound periodically stops responding

Alexander Clouter
Wed Apr 6 09:38:29 CEST 2011


W.C.A. Wijngaards <wouter at nlnetlabs.nl> wrote:
> 
> So, it is somehow unique to that machine.  Can you see in 'top' what
> unbound is doing?  (is it using cpu, 100% in a busy loop?, it is not
> responding to unbound-control, so it must be completely hosed somehow)
>
...the sysadmin in me usually reaches for 'strace' at this point for 
clues.
 
> Another thing you can do is use 'gcore' to make a coredump of the
> 'failed' unbound process.  (and then kill it and start a new unbound for
> your production).  Then you can use 'gdb' and your compiled unbound
> executable to read the core image and produce a stack backtrace what it
> is doing.
>
...and when strace fails me, gdb is "bring out the cannon".
 
Cheers

-- 
Alexander Clouter
.sigmonster says: There is no fool to the old fool.
                  		-- John Heywood