[1392206237] nsd[22985]: error: failed writing to tcp: Connection reset by peer/Broken pipe

Hi all,

I have problem that drives me crazy,

When our NSD servers are running aft her a while I keep getting these messages in my nsd.log

[1392206139] nsd[22985]: error: failed writing to tcp: Connection reset by peer

[1392206218] nsd[22985]: error: failed writing to tcp: Connection reset by peer

[1392206218] nsd[22985]: error: failed writing to tcp: Connection reset by peer

[1392206218] nsd[22985]: error: failed writing to tcp: Broken pipe

[1392206237] nsd[22985]: error: failed writing to tcp: Connection reset by peer

[1392206237] nsd[22985]: error: failed writing to tcp: Connection reset by peer

[1392206237] nsd[22985]: error: failed writing to tcp: Connection reset by peer

[1392206323] nsd[22985]: error: failed writing to tcp: Connection reset by peer

[1392206323] nsd[22985]: error: failed writing to tcp: Connection reset by peer

[1392206323] nsd[22985]: error: failed writing to tcp: Connection reset by peer

What could be the problem ?

Anybody an idea ?

With kind regards,

Bas van den Dikkenberg

Forgot to mention,

I am running NSD version 3.2.17.

The problem I see the most on our hidden master server

With kind regards,

Bas van den Dikkenberg

Hoi Bas,

Forgot to mention,

I am running NSD version 3.2.17.

These broken pipe and connection reset are normal and harmless (to
your server). It prints this because of high(-ish) verbosity. You
can ignore them, don't go crazy over them. I thought NSD4 had made
them print at higher verbosity setting so as to less annoy the operator.

The problem I see the most on our hidden master server

This will probably be zone transfers that are started because of the
SOA retry or expire timer, but then the zone was not changed and the
zone transfer is aborted and the tcp channel is closed.

Best regards,
   Wouter

Thanks for the info :smiley: