-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
FYI: this puzzle is solved.
Matthijs
- -------- Original Message --------
Subject: RE: [nsd-users] problem using nsd
Date: Wed, 16 Jan 2008 18:36:38 +0200
From: Paul Roand <paul.roland at cc.btn.ro>
Reply-To: <paul.roland at cc.btn.ro>
Organization: Business Technology Network
To: 'Matthijs Mekking' <matthijs at nlnetlabs.nl>
References: <000101c8575d$c01eacf0$405c06d0$%roland at cc.btn.ro>
<478DC6B5.6060306 at nlnetlabs.nl>
Dear Matthijs Mekking,
I found the problem, it was an cronded process buy another admin set to kill
nsd for some reasons ( he didn't knew I migrated to NSD ) and I wasn't
aware
of it and did not even had the idea to look in there.
I am very sorry for wasting your time with this and I want you to know that
I am very glad I had this response so fast so I'm proud I migrated to NSD
from that buggy named and slow_thing djbdns.
now everything works fine, thank you again.
- -----Original Message-----
From: Matthijs Mekking [mailto:matthijs at nlnetlabs.nl]
Sent: Wednesday, January 16, 2008 10:56 AM
To: paul.roland at cc.btn.ro
Subject: Re: [nsd-users] problem using nsd
Hello Paul,
It looks to me that nsd tried to write to a child process that somehow
has been terminated before. nsd receives a SIGPIPE signal and it's
reaction to that is to shutdown.
Do you know how long nsd runs before this problem occurs? Can you send
me your configuration file and complete log file, so I can look into this?
Regards,
Matthijs Mekking
matthijs at nlnetlabs.nl
Foundation NLnet Labs
Paul Roand wrote:> Hello I have this problem since a week or so:
>
> The nsd daemon crashes unexpectedly and the nsd log files shows this:
>
> [1200299533] nsd[3736]: info: XSTATS 1200299533 1200298484 RR=0 RNXD=0
> RFwdR=0 RDupR=0 RFail=0 RFErr=0 RErr=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=0
> SAns=40 SFwdQ=0 SDupQ=0 SErr=0 RQ=37 RIQ=0 RFwdQ=0 RDupQ=0 RTCP=0 SFwdR=0
> SFail=30 SFErr=0 SNaAns=0 SNXD=0 RUQ=0 RURQ=0 RUXFR=0 RUUpd=1
> [1200299533] nsd[3731]: error: problems sending command 5 to server 3734:
> Broken pipe
> [1200299533] nsd[3731]: error: problems sending command 5 to server 3735:
> Broken pipe
> [1200299533] nsd[3731]: error: problems sending command 5 to server 3736:
> Broken pipe
> [1200299533] nsd[3731]: error: problems sending command 5 to server 3737:
> Broken pipe
> [1200299533] nsd[3731]: error: problems sending command 5 to server 3738:
> Broken pipe
> [1200299533] nsd[3731]: error: problems sending command 5 to server 3739:
> Broken pipe
> [1200299533] nsd[3731]: error: problems sending command 5 to server 3740:
> Broken pipe
> [1200299533] nsd[3731]: error: problems sending command 5 to server 3741:
> Broken pipe
> [1200299533] nsd[3731]: error: problems sending command 5 to server 3742:
> Broken pipe
> [1200299533] nsd[3731]: error: problems sending command 5 to server 3743:
> Broken pipe
> [1200299533] nsd[3731]: warning: signal received, shutting down...
>
> [1200386455] nsd[4767]: error: failed reading from tcp: Connection reset
by> peer
> [1200386455] nsd[4769]: error: failed reading from tcp: Connection reset
by> peer
>
> I would appreciate any help or suggestion. Thank you
>
> _______________________________________________
> nsd-users mailing list
> nsd-users at NLnetLabs.nl
> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHjvEjIXqNzxRs6egRAgUwAJ4/vKwkxcOPO7TGibabzc2qLJxUIQCeJiTk
0oZjKYrUIzFwBS0HLu+vumg=fXV9
-----END PGP SIGNATURE-----