[nsd-users] NSD 4.0.2 released
wouter at nlnetlabs.nl
Thu Mar 13 11:13:08 UTC 2014
-----BEGIN PGP SIGNED MESSAGE-----
That is certainly a lot of pain over this release, and we are trying
to fix these start-stop issues, and push out 4.0.3 for that. The
memory leak was considered very bad so we tried to push out a fix for
that before other fixes. But the 4.0.2 update caused lots more people
than we imagined to have to stop and start NSD and that caused them to
have the stop-start issues.
There is a snapshot tarball available here:
It contains fixes for the start-stop issues. It will delete nsd.db
for you and create it again (from zonefile and with zone transfers).
The issues should then not reappear, as the database is properly
closed and it checks more carefully before attempting to open the
The fixes are also in the code repository, and you can fetch it there.
If you still have issues, where it fails to start, I would like to
have the nsd.db file (and related config perhaps) that causes it. It
would also be nice to hear if there are users without problems or if
the problems are fixed by these updates, this may make it easier to
determine the situation where the error occurs.
On 03/12/2014 11:03 PM, fwkh7691 at nifty.com wrote:
> If "rm /var/db/nsd/*" and start again, all zones are removed. So
> "rm /var/db/nsd/nsd.db" might be better.
> On Wed, 12 Mar 2014 08:01:47 -0700 darx at sent.com wrote:
>> chiming in.
>> same issue with
>> running 4.0.1 clean shutdown build/install 4.0.2 start 4.0.2 ->
>> fail to launch
>> delete /var/db/nsd/* start 4.0.2 -> ok
>> On Wed, Mar 12, 2014, at 07:47 AM, Erik De Neve wrote:
>>> Same problem here.
>>> Has deleted /var/db/nsd/* and it started again!
>> On Wed, Mar 12, 2014, at 07:49 AM, W.C.A. Wijngaards wrote:
>>> This was supposed to be covered by this bugfix: - - Fix that
>>> NSD will delete and recreate not-clean-closed databases. Are
>>> you starting the new NSD?
>>> The issue was that nsd.db was corrupted by unclean shutdown.
>>> Delete of that file and a restart fixed the issue manually.
>>> This fix made this automatic.
>> _______________________________________________ nsd-users mailing
>> list nsd-users at NLnetLabs.nl
> _______________________________________________ nsd-users mailing
> list nsd-users at NLnetLabs.nl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
More information about the nsd-users