[nsd-users] NSD as slave leaves a child process behind

[Matthijs Mekking]

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

Hi Ville,

It could be that the shutdown signal was successfully send to the xfrd
process, but that it is quite busy at the moment.

I have done some testing with 10.000 zones of 7 RRs a zone. It sometimes
takes a couple of seconds before the xfrd process really terminated. But
eventually, the xfrd process should shut down. This might happen after
the nsdc stop command returned 0.

Best regards,

Matthijs

Ville Mattila wrote:
> Hi,
> 
> On Tue, 15 Sep 2009, Ville Mattila wrote:
> 
>> On Tue, 15 Sep 2009, Matthijs Mekking wrote:
> 
>>> Of course, if you run nsdc stop, no processes should be kept alive. Is
>>> this the case?
>>
>> Yes.  'nsdc stop' leaves xfrd process running and returns ok.
>>
>>> What does nsdc stop output?
>>
>> Nothing really:
>>
>> % sudo /usr/sbin/nsdc -c
>> /v/net/ns-secondary.funet.fi/etc/nsd/nsd-isar.conf stop
>> % echo $?
>> 0
> 
> We've now worked around this problem by modifying the nsd init script
> to NOT run 'nsdc patch' before 'nsdc stop' in restarts.  No problems
> in xfrd shutdown for 3+ weeks and 50+ restarts.
> 
> So it seems running 'nsdc patch' (which can take several seconds in our
> environment) could prevent nsd/xfrd process termination by 'nsdc stop'.
> Can you confirm this?  What can we do to help finding a real resolution
> to this?
> 
> Regards,

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

iQEcBAEBAgAGBQJK3YfBAAoJEA8yVCPsQCW55MYIANrmCPpJZpclFheL2hVtIkwr
bIv0W7jz8uB+3/JMHLvDE+mvL0q3goNV4tdTKI3xAsRtouVitNlObmZRP28HlR9/
G+kDqjq5JFMZGtA5adQdjC8RZC/M/0BeVWtbJHQJKw7lJekTUMO5vi3H1SgzZwye
4vV9EWH7DsC772EXelBTrDSkyLopyiNa22XGn+QqG3XCtjUwq2wfhUr12v69FVaE
+gv4yfEttEwCtl7CYHKaPG6c8PL4rqZYQakO4Dr7Nv7aSppTbUu/3Uxbs7OMKksJ
yOEJ39DzcCq0oP6+1sqoBExXJa3xNY7kSpS5nSHI/nI1z1O0txFbnM+DbSXPVcs=
=Hv2M
-----END PGP SIGNATURE-----