Simon Bedford wrote:
Laurent Papier wrote:
Le Wed, 31 Mar 2010 20:42:33 +0200
bert hubert <bert.hub...@netherlabs.nl> écrit:
On Tue, Mar 30, 2010 at 03:09:08PM +0100, Simon Bedford wrote:
A quick update - I've traced down an issue that may have been causing this.
Would you be interested in testing this small patch?
I can help test this patch Bert.
It can be found on:
http://wiki.powerdns.com/trac/changeset/1546
or
http://wiki.powerdns.com/trac/changeset/1546?format=diff&new=1546
The 'applying patches' section on this page explains how to apply:
http://wiki.powerdns.com/trac/wiki/HACKING
I hope this solves the issue - it sure sounds like it!
3 days without problem, your patch solves the issue for me.
We created a patched version in the end and rolled to one server back on
the 8th April, no fault seen since and now rolled to the entire platform
as of today, looking good.
Thanks
Simon
_______________________________________________
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
We have now had 2 more failures of the tcp listener on 2 seperate
servers in the last week, a simple reload of the software fixes this.
the thing I have noticed when this occurs is that when telnetting to the
port you can then type in anything and try and escape, etc but the
connection never closes, whereas on a working server the session will
close after a short while of typing and pressing Enter.
The logs do not show anything or give any pointers as to the cause...
Simon
_______________________________________________
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
