[nsd-users] How to notify myself if NSD dies unexpectedly?

Paul Wouters paul at nohats.ca
Thu Mar 6 14:19:19 UTC 2014

On Thu, 6 Mar 2014, opendaddy at hushmail.com wrote:

> I run this big site which has been down for days now without my knowledge due to this:
> [1393533384] nsd[1014]: notice: nsd started (NSD 3.2.15), pid 1014
> [1394026594] nsd[1014]: warning: server 1060 died unexpectedly with status 9, restarting
> [1394026594] nsd[1014]: error: fork failed: Cannot allocate memory
> [1394113596] nsd[1014]: warning: signal received, shutting down...
> Restarted NSD manually just now and everything is fine. But does anybody know of ways I can notify myself should this happen again?

nsd4 can be started without forking, so an init systems like systemd can
get restarted by them. With systemd that would be Type=Simple

For nsd3, this is not possible due to its forking and mishandling of pid


More information about the nsd-users mailing list