Maintained by: NLnet Labs

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

W.C.A. Wijngaards
Wed Oct 8 09:50:44 CEST 2008


-----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-----