On 25-Aug-2010, Florian Weimer wrote:
Do you use a stateful packet filter (such as Netfilter connection
tracking), either on the host or in front of it?
The host running BIND doesn't run any packet filter. There is a
stateful packet filter on a dedicated gateway router for the network,
which is
package bind9
found 561997 1:9.7.1.dfsg.P2-2
thanks
[keeping the conversation recorded in the bug report]
On 23-Aug-2010, Florian Weimer wrote:
* Ben Finney:
I am upgrading Squeeze again now and will report the behaviour
under the current version.
The problem has occurred again, twice now,
* Ben Finney:
Do you know how many UDP flows BIND has generated when this happened?
I've seen similar things as the result of firewall state table
overflow.
I'm not familiar with the term “UDP flows”. I have now installed the
‘flowscan’, ‘flow-tools’, and ‘rrdtool’ packages; can you tell
package bind9
unarchive 561997
reopen 561997
found 561997 1:9.7.0.dfsg.P1-1
thanks
On 10-Apr-2010, Ben Finney wrote:
I installed version ‘1:9.7.0.dfsg.P1-1’ of bind9 from Squeeze, and
left it running for approximately 70 hours. The problem has not
recurred in that time.
The problem has
package bind9
fixed 561997 1:9.7.0.dfsg.P1-1
thanks
I installed version ‘1:9.7.0.dfsg.P1-1’ of bind9 from Squeeze, and
left it running for approximately 70 hours. The problem has not
recurred in that time.
This is enough to demonstrate to me that the problem has been
addressed, so I am closing
package bind9
found 561997 1:9.6.1.dfsg.P3-1
thanks
On 22-Dec-2009, Ben Finney wrote:
The only way I've found to restore service is to ‘sudo killall -KILL
named’ and restart the server, which of course doesn't give much
opportunity to find out what's wrong.
I installed version
On 22-Dec-2009, Ben Finney wrote:
The only way I've found to restore service is to ‘sudo killall -KILL
named’ and restart the server, which of course doesn't give much
opportunity to find out what's wrong.
I have been trying to narrow down what might be a proximate cause
for the bug; but so
On 22-Dec-2009, Ben Finney wrote:
The only way I've found to restore service is to ‘sudo killall -KILL
named’ and restart the server, which of course doesn't give much
opportunity to find out what's wrong.
I have been trying to narrow down what might be a proximate cause
for the bug; but so
On Tue, Jan 5, 2010 at 09:44, Ben Finney ben+deb...@benfinney.id.au wrote:
On 22-Dec-2009, Ben Finney wrote:
The only way I've found to restore service is to ‘sudo killall -KILL
named’ and restart the server, which of course doesn't give much
opportunity to find out what's wrong.
I have been
On 05-Jan-2010, Ondřej Surý wrote:
have you tried writing to bind-users? Your question would probably
hit much wider audience.
Yes, I have sent a bug report, but it never appeared on the list.
Discussing it directly in Debian BTS would only make sense if this
behaviour doesn't happen in
Package: bind9
Version: 1:9.6.1.dfsg.P2-1
Severity: normal
For several months I've been having BIND's ‘named’ process hang
intermittently.
I'm running Debian Squeeze, with the ‘bind9’ package version currently
at 1:9.6.1.dfsg.P2-1 though the same behaviour has persisted for a
number of versions.
11 matches
Mail list logo
