Your message dated Sun, 13 May 2007 18:05:03 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in BIND 9.3
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: bind9
Version: 1:9.2.4-1
Severity: important
Hello
Tonight our DNS-RBL Bind stopped operation without any log entries. After some
investigation I found some strange
TEMP Files in the Cache directory. I also noticed one journal grew to nearly
2GB.
Restarting bind didn't solve the problem. So I deleted all journals. Problem
fixed.
After some Googleing I found similar reports of other people experiencing a
bind failure when journals grew to 2GB.
Apparently this is fixed in Bind 9.3 where you can specify a max journal size.
Could this fix be applied to debian bind 9.2?
-Benoit-
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.16.11
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages bind9 depends on:
ii adduser 3.63 Add and remove users and groups
ii libc6 2.3.2.ds1-22sarge3 GNU C Library: Shared libraries an
ii libdns16 1:9.2.4-1 DNS Shared Library used by BIND
ii libisc7 1:9.2.4-1 ISC Shared Library used by BIND
ii libisccc0 1:9.2.4-1 Command Channel Library used by BI
ii libisccfg0 1:9.2.4-1 Config File Handling Library used
ii liblwres1 1:9.2.4-1 Lightweight Resolver Library used
ii libssl0.9.7 0.9.7e-3sarge1 SSL shared libraries
ii netbase 4.21 Basic TCP/IP networking system
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:9.3.0-1
Fixed in BIND 9.3, as indicated in the bug report.
--- End Message ---
