Hi Sven,
What is your verbosity level? Since version 3.1.0, NSD should not report
'connection reset by peer' messages, except when your verbosity level
is 2 or higher.
Regards,
Matthijs
NLnet Labs
Sven Juergensen (KielNET) wrote:> Hi list,
>
> after implementing unbound, I went for
> NSD. So far, so good, what irritates
> me though is the following:
>
> [...]
> [1236151517] nsd[29099]: error: tcp read sz: Connection reset by peer
> [1236151517] nsd[29099]: error: tcp read sz: Connection reset by peer
> [1236151517] nsd[29099]: error: tcp read sz: Connection reset by peer
> [1236151517] nsd[29099]: error: Could not tcp connect to 1.2.3.4:
> Connection reset by peer
> [1236151517] nsd[29099]: error: Could not tcp connect to 1.2.3.4:
> Connection reset by peer
> [...]
>
> Sometimes, this mingles in:
> error: xfrd: failed writing tcp Broken pipe
> error: xfrd: failed writing tcp Connection reset by peer
>
> This happens in a master-slave setup on
> the slave when it's started. What am I
> missing here?
>
> Thanks and regards,
>
> Mit freundlichen Gruessen,
>
> i. A. Sven Juergensen
>
_______________________________________________
nsd-users mailing list
nsd-users at NLnetLabs.nl
http://open.nlnetlabs.nl/mailman/listinfo/nsd-users
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 544 bytes
Desc: OpenPGP digital signature
URL:
<http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20090304/dad89f11/attachment.bin>