Maintained by: NLnet Labs

[Unbound-users] Unbound v1.0.2 stopping - DNSSEC enabled

Griffiths, Chris
Wed Oct 8 13:22:54 CEST 2008


I am running the update anchors script on a daily cron which does not correlate to the unbound stop messages.

I will go back to my compile box and verify the libevent version.

Thanks

Chris Griffiths
Comcast Cable Communications, Inc.
National Engineering and Technical Operations
215-286-3992 - Desk
215-776-6416 - Cell

----- Original Message -----
From: W.C.A. Wijngaards <wouter at nlnetlabs.nl>
To: Griffiths, Chris
Cc: unbound-users at unbound.net <unbound-users at unbound.net>
Sent: Wed Oct 08 03:50:44 2008
Subject: Re: [Unbound-users] Unbound v1.0.2 stopping - DNSSEC enabled

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Chris,

This message appears when unbound is told to stop.  Unbound is making a
clean exit. So, it acts as if it has received SIGTERM. Something is
calling /etc/rc.d/unbound stop, or sending kill signals to unbound.

There is one other possibility, which only happens when you compile with
old versions of libevent (fixed in libevent 1.3c).  In those cases, also
SIGHUP causes unbound to stop.

Are you running trust anchor update scripts every few hours that do a
rc.d/unbound reload (which sends SIGHUP) on a machine with old libevent?

Best regards,
   Wouter

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkjsZlQACgkQkDLqNwOhpPgzLQCeK0pq+0rg8ol9aKlstEemSiJW
FecAoLYjdvGju7Ylpxsn/q+Ed7Ude09B
=Vhlw
-----END PGP SIGNATURE-----