[nsd-users] NSD 4.0.2 released

[W.C.A. Wijngaards]

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

Hi,

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:
http://open.nlnetlabs.nl/~wouter/nsd-4.0.3-20140313.tar.gz
sha1 8ec4648410adfd616375714d74355d73573ec189
sha256 555bc29fe7c19e467d3e5ece35f4b9d2fbee4281a98a6fc7b26a252957fac3fe

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
database again.

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.

Best regards,
   Wouter


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 
>> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users
> 
> 
> 
> 
> _______________________________________________ nsd-users mailing
> list nsd-users at NLnetLabs.nl 
> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTIZLEAAoJEJ9vHC1+BF+NOeoQAKa79KnJV53/gLCKjprI141F
cbjhkVUcV+Shm07Q/VfpMek90ywUz0LriWEO8/zNPAVAJzv6WCZR50jOnrYDrz2l
rEYFy09kgZEpXwXldRrOGXULO90OBzXUaUX+/gwtzIYxCWgnmIRFZAxQnNp87zXh
c6STRcqe4J7niKWugqr7GJekfC/imPy1OX3uny8IwrGVg0AAjHj+dSUQikl1asej
NDO9MKKmcuELrIL2Hf8J8YBe8KKNlT6yrgu5Q9s5wqgIYqw60HjBTp3PDc6oG3M/
Z70SI1TeXMOOmbCEJFaJ0nvLv1Fu9iIMutlQqLP1XkzrlkIsi+dGaDg/q2GvwaNR
5ic5AWAs7M/EdZna0d31s/+8wG7ExvP7CE4cx+oHuRrzv8ze3Yy7vpPj/co+dSGj
cBL4fuWCwe985mAqJc5DPX4Q8ayj6AtTWOnDFtW3f2jOB/tuk4Uv+OqN9+JjQn3D
biqVDOvNMFZ1VrFnpS9/BldimLLWH5AsG/wyK6v/d3zELUyQWr2VmPXuSFQPUHCy
m9N6c17Bu6zRxUAT78CLhzHQplRCYe3L67KI637kaUsCBzmKwQmfyeARaoZgleMM
RC/qQ7iT83s93X8grhimwe3Urvm/ILSCnw+xFf5kIrXfGWf+x29cmTUq5ieX6Qk3
TV0dG4mYngYnSf4Igyt4
=SIi+
-----END PGP SIGNATURE-----