bind進程經常掛死，求高人指教！
伺服器為DELL6850 配置還算可以 用戶量3000左右
使用的操作系統和bind版本分別是linux AS4.0/BIND9.5.1，伺服器是08年做的一直到今年的4月都沒有出現問題，但之後named進程就經常終止，到現在一天要DOWN好幾次，特在此附上日誌及named.conf請廣大朋友指教！謝謝！
ul 13 17:03:20 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:29 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:29 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:29 dns named: client 10.53.148.110#1028: RFC 1918 response from Internet for 82.148.53.10.in-addr.arpa
Jul 13 17:03:31 dns last message repeated 2 times
Jul 13 17:03:32 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:32 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:32 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:35 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:35 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:35 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:36 dns named: client 10.53.148.110#1028: RFC 1918 response from Internet for 104.148.53.10.in-addr.arpa
Jul 13 17:03:36 dns named: dispatch 0xb7af8008: shutting down due to TCP receive error: 199.19.53.1#53: connection reset
Jul 13 17:03:37 dns named: client 10.53.148.110#1028: RFC 1918 response from Internet for 104.148.53.10.in-addr.arpa
Jul 13 17:03:38 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:38 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:38 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:41 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:41 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:41 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:42 dns named: client 10.53.148.110#1028: RFC 1918 response from Internet for 103.148.53.10.in-addr.arpa
Jul 13 17:03:43 dns named: client 10.53.148.110#1028: RFC 1918 response from Internet for 103.148.53.10.in-addr.arpa
Jul 13 17:03:44 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:44 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:44 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:47 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:03:47 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:04:16 dns named: client 10.53.148.110#1028: RFC 1918 response from Internet for 82.148.53.10.in-addr.arpa
Jul 13 17:04:17 dns named: client 10.53.148.110#1028: RFC 1918 response from Internet for 82.148.53.10.in-addr.arpa
Jul 13 17:04:17 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:04:17 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:04:17 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:04:20 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:04:20 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:04:20 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:04:47 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:04:53 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:04:53 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:04:53 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:04:54 dns named: client 10.53.148.110#1028: RFC 1918 response from Internet for 104.148.53.10.in-addr.arpa
Jul 13 17:04:56 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:04:56 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:04:56 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:04:56 dns named: client 10.53.150.70#4489: RFC 1918 response from Internet for 6.150.53.10.in-addr.arpa
Jul 13 17:04:57 dns named: client 10.53.150.70#4489: RFC 1918 response from Internet for 12.150.53.10.in-addr.arpa
Jul 13 17:04:58 dns named: client 10.53.150.70#4489: RFC 1918 response from Internet for 20.150.53.10.in-addr.arpa
Jul 13 17:04:58 dns named: client 10.53.148.110#1028: RFC 1918 response from Internet for 100.148.53.10.in-addr.arpa
Jul 13 17:04:59 dns named: client 10.53.150.70#4469: RFC 1918 response from Internet for 41.150.53.10.in-addr.arpa
Jul 13 17:04:59 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:02 dns named: client 10.53.150.70#4489: RFC 1918 response from Internet for 12.150.53.10.in-addr.arpa
Jul 13 17:05:03 dns named: client 10.53.150.70#4489: RFC 1918 response from Internet for 20.150.53.10.in-addr.arpa
Jul 13 17:05:04 dns named: client 10.53.148.110#1028: RFC 1918 response from Internet for 82.148.53.10.in-addr.arpa
Jul 13 17:05:05 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:05 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:05 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:05 dns named: client 10.53.150.70#4489: RFC 1918 response from Internet for 43.150.53.10.in-addr.arpa
Jul 13 17:05:06 dns named: client 10.53.150.70#4469: RFC 1918 response from Internet for 44.150.53.10.in-addr.arpa
Jul 13 17:05:07 dns named: client 10.53.150.70#4489: RFC 1918 response from Internet for 6.150.53.10.in-addr.arpa
Jul 13 17:05:07 dns named: client 10.53.150.70#4489: RFC 1918 response from Internet for 12.150.53.10.in-addr.arpa
Jul 13 17:05:08 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:08 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:08 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:08 dns named: client 10.53.150.70#4489: RFC 1918 response from Internet for 20.150.53.10.in-addr.arpa
Jul 13 17:05:08 dns named: client 10.53.150.70#4489: RFC 1918 response from Internet for 41.150.53.10.in-addr.arpa
Jul 13 17:05:10 dns named: client 10.53.148.110#1028: RFC 1918 response from Internet for 82.148.53.10.in-addr.arpa
Jul 13 17:05:11 dns named: client 10.53.150.70#4489: RFC 1918 response from Internet for 43.150.53.10.in-addr.arpa
Jul 13 17:05:11 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:11 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:11 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:12 dns named: client 10.53.150.70#4489: RFC 1918 response from Internet for 44.150.53.10.in-addr.arpa
Jul 13 17:05:12 dns named: client 10.53.150.70#4469: RFC 1918 response from Internet for 6.150.53.10.in-addr.arpa
Jul 13 17:05:12 dns named: client 10.53.150.70#4489: RFC 1918 response from Internet for 46.150.53.10.in-addr.arpa
Jul 13 17:05:13 dns named: client 10.53.150.70#4469: RFC 1918 response from Internet for 52.150.53.10.in-addr.arpa
Jul 13 17:05:13 dns named: client 10.1.116.41#2388: RFC 1918 response from Internet for 198.18.52.10.in-addr.arpa
Jul 13 17:05:13 dns named: client 10.53.150.70#4469: RFC 1918 response from Internet for 20.150.53.10.in-addr.arpa
Jul 13 17:05:13 dns named: client 10.53.150.70#4469: RFC 1918 response from Internet for 12.150.53.10.in-addr.arpa
Jul 13 17:05:14 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:14 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:14 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:14 dns named: client 10.53.148.110#1028: RFC 1918 response from Internet for 100.148.53.10.in-addr.arpa
Jul 13 17:05:15 dns named: client 10.53.150.70#4469: RFC 1918 response from Internet for 43.150.53.10.in-addr.arpa
Jul 13 17:05:17 dns named: client 10.53.150.70#4469: RFC 1918 response from Internet for 44.150.53.10.in-addr.arpa
Jul 13 17:05:17 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:17 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:17 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:17 dns named: client 10.53.142.171#1506: RFC 1918 response from Internet for 2.142.53.10.in-addr.arpa
Jul 13 17:05:17 dns named: client 10.53.150.70#4469: RFC 1918 response from Internet for 6.150.53.10.in-addr.arpa
Jul 13 17:05:17 dns named: client 10.53.150.70#4469: RFC 1918 response from Internet for 46.150.53.10.in-addr.arpa
Jul 13 17:05:18 dns named: client 10.53.142.171#1504: RFC 1918 response from Internet for 3.142.53.10.in-addr.arpa
Jul 13 17:05:18 dns named: client 10.53.142.171#1506: RFC 1918 response from Internet for 2.142.53.10.in-addr.arpa
Jul 13 17:05:19 dns named: client 10.53.150.70#4469: RFC 1918 response from Internet for 20.150.53.10.in-addr.arpa
Jul 13 17:05:19 dns named: client 10.53.150.70#4489: RFC 1918 response from Internet for 12.150.53.10.in-addr.arpa
Jul 13 17:05:19 dns named: client 10.53.142.171#1504: RFC 1918 response from Internet for 3.142.53.10.in-addr.arpa
Jul 13 17:05:19 dns named: client 10.53.150.70#4468: RFC 1918 response from Internet for 52.150.53.10.in-addr.arpa
Jul 13 17:05:19 dns named: client 10.53.142.171#1506: RFC 1918 response from Internet for 2.142.53.10.in-Jul 13 17:05:23 dns named: client 10.52.4.8#36841: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:23 dns named: client 10.52.4.70#32773: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:23 dns named: client 10.52.4.71#35392: RFC 1918 response from Internet for 1.8.52.10.in-addr.arpa
Jul 13 17:05:23 dns named: dispatch.c:3023: REQUIRE(res->item_out == isc_boolean_true) failed
Jul 13 17:05:23 dns named: exiting (due to assertion failure)
Jul 13 17:09:22 dns sshd(pam_unix): session opened for user root by root(uid=0)
Jul 13 17:09:33 dns named: starting BIND 9.5.1b1 -u named -t /var/named/chroot
Jul 13 17:09:33 dns named: loading configuration from '/etc/named.conf'
Jul 13 17:09:33 dns named: /etc/named.conf:110: option 'allow-update' is not allowed in 'slave' zone 'hq.ctc.com'Jul 13 17:09:33 dns named: using default UDP/IPv4 port range:
Jul 13 17:09:33 dns named: using default UDP/IPv6 port range:
Jul 13 17:09:33 dns named: listening on IPv4 interface lo, 127.0.0.1#53
Jul 13 17:09:33 dns named: listening on IPv4 interface eth0, 10.52.4.40#53
Jul 13 17:09:33 dns named: default max-cache-size (33554432) applies
Jul 13 17:09:33 dns named: automatic empty zone: 127.IN-ADDR.ARPA
Jul 13 17:09:33 dns named: automatic empty zone: 254.169.IN-ADDR.ARPA
Jul 13 17:09:33 dns named: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Jul 13 17:09:33 dns named: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Jul 13 17:09:33 dns named: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jul 13 17:09:33 dns named: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jul 13 17:09:33 dns named: automatic empty zone: D.F.IP6.ARPA
Jul 13 17:09:33 dns named: automatic empty zone: 8.E.F.IP6.ARPA
Jul 13 17:09:33 dns named: automatic empty zone: 9.E.F.IP6.ARPA
Jul 13 17:09:33 dns named: automatic empty zone: A.E.F.IP6.ARPA
Jul 13 17:09:33 dns named: automatic empty zone: B.E.F.IP6.ARPA
Jul 13 17:09:33 dns named: default max-cache-size (33554432) applies: view _bind
Jul 13 17:09:33 dns named: command channel listening on 127.0.0.1#953
Jul 13 17:09:33 dns named: zone 0.in-addr.arpa/IN: NS 'localhost.0.in-addr.arpa' has no address records (A or AAAA)
Jul 13 17:09:33 dns named: zone 0.in-addr.arpa/IN: loaded serial 42
Jul 13 17:09:33 dns named: zone 1.52.10.in-addr.arpa/IN: loaded serial 1997022700
Jul 13 17:09:33 dns named: zone 3.52.10.in-addr.arpa/IN: loaded serial 1997022700
Jul 13 17:09:33 dns named: zone 4.52.10.in-addr.arpa/IN: loaded serial 1997022700
Jul 13 17:09:33 dns named: zone 52.52.10.in-addr.arpa/IN: loaded serial 1997022700
Jul 13 17:09:33 dns named: zone 0.0.127.in-addr.arpa/IN: loaded serial 1997022700
Jul 13 17:09:33 dns named: zone 132.in-addr.arpa/IN: loaded serial 1997022700
Jul 13 17:09:33 dns named: zone 135.in-addr.arpa/IN: loaded serial 1997022700
Jul 13 17:09:33 dns named: zone 255.in-addr.arpa/IN: NS 'localhost.255.in-addr.arpa' has no address records (A or AAAA)
Jul 13 17:09:33 dns named: zone 255.in-addr.arpa/IN: loaded serial 42
Jul 13 17:09:33 dns named: zone 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: loaded serial 1997
------------------------------------------------------------------------------------------------------------------------------------------------------
name.conf
// named.conf for Red Hat caching-nameserver
//
options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
forwarders { 202.100.64.68; };
allow-query { any; };
// allow-query-cache { none; };
pid-file "/var/run/named/named.pid";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};
//
// a caching only nameserver config
//
controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
//
// ***********************************
// Deny the AAAA record type (ipv6)
// Modify by gaozd 2009.05.20
// ***********************************
//
logging {
category default { log_syslog; };
channel log_syslog { syslog; };
category dnssec { null; };
category lame-servers { null; };
category edns-disabled { null; };
};
zone "." IN {
type hint;
file "named.ca";
};
zone "localdomain" IN {
type master;
file "localdomain.zone";
allow-update { none; };
};
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};
zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" IN {
type master;
file "named.ip6.local";
allow-update { none; };
};
zone "255.in-addr.arpa" IN {
type master;
file "named.broadcast";
allow-update { none; };
};
zone "0.in-addr.arpa" IN {
type master;
file "named.zero";
allow-update { none; };
};
include "/etc/rndc.key";
// ********************************
// modify by Gaozhidong 2008.01.10
// local config
// *******************************
zone "avscs.local" IN {
type master;
file "avscs.local.zone";
allow-update { none; };
};
zone "gs.ctc.com" IN {
type master;
file "gs.ctc.com.zone";
allow-update { none; };
};
zone "hq.ctc.com" IN {
type slave;
masters { 10.52.4.117; 10.3.255.22; 10.3.255.23; };
file "slaves/hq.ctc.com.zone";
allow-update { none; };
};
zone "gansutelecom.com" IN {
type master;
file "gansutelecom.com.zone";
allow-update { none; };
};
zone "gsdx.com" IN {
type master;
file "gsdx.com.zone";
allow-update { none; };
};
zone "4.52.10.in-addr.arpa" IN {
type master;
file "named.10.52.4";
allow-update { none; };
};
zone "3.52.10.in-addr.arpa" IN {
type master;
file "named.10.52.3";
allow-update { none; };
};
zone "52.52.10.in-addr.arpa" IN {
type master;
file "named.10.52.52";
allow-update { none; };
};
zone "132.in-addr.arpa" IN {
type master;
file "named.132";
allow-update { none; };
};
zone "135.in-addr.arpa" IN {
type master;
file "named.135";
allow-update { none; };
};
zone "1.52.10.in-addr.arpa" IN {
type master;
file "named.10.52.1";
allow-update { none; };
[ 本帖最後由 flcy0513 於 2009-7-20 18:39 編輯 ]
《解決方案》
https://www.isc.org/node/315
但導致named進程死掉的原因不會是這個。先檢查伺服器硬體。
Jul 13 17:05:23 dns named: dispatch.c:3023: REQUIRE(res->item_out == isc_boolean_true) failed
《解決方案》
問題在與你的bind版本BIND 9.5.1b1，這個版本的bind不穩定，在某些情況下就會死掉，換正式版本就可以了。
《解決方案》
Jul 19 08:46:30 dns named: dispatch 0xb78e1008: shutting down due to TCP receive error: 199.19.56.1#53: connection reset
Jul 19 08:46:30 dns named: dispatch 0xb7cd2008: shutting down due to TCP receive error: 199.19.56.1#53: connection reset
這個報錯日誌中很多，這個是表示什麼？？
《解決方案》
為了查看方便我將報錯加紅，:em45:
[ 本帖最後由 flcy0513 於 2009-7-20 18:41 編輯 ]
《解決方案》
回復 #2 llzqq 的帖子
硬體的話可能問題出在哪
現在哪個版本穩定，升級時需要注意什麼，因為是生產系統比較重要，謝謝朋友們！
[ 本帖最後由 flcy0513 於 2009-7-21 08:49 編輯 ]
《解決方案》
原帖由 flcy0513 於 2009-7-21 08:46 發表 http://bbs2.chinaunix.net/images/common/back.gif
硬體的話可能問題出在哪
現在哪個版本穩定，升級時需要注意什麼，因為是生產系統比較重要，謝謝朋友們！
先升級到目前穩定版（BIND 9.5.1-P2），觀察一段時間如還是有問題重點檢查伺服器內存問題。
《解決方案》
裝ubuntu 8.04.3 LTS吧
裝redhat你能升級么？
《解決方案》
我要是你的話，備份數據，格式化，重裝rhel4.7，如果方便，停機，開蓋 換換風扇，吹吹灰啥的。
保證能好！
該幹活時就要干，不能懶惰:em26:
[ 本帖最後由 aleng 於 2009-7-28 15:46 編輯 ]
《解決方案》
原帖由 llzqq 於 2009-7-22 07:48 發表 http://bbs3.chinaunix.net/images/common/back.gif
先升級到目前穩定版（BIND 9.5.1-P2），觀察一段時間如還是有問題重點檢查伺服器內存問題。
請問大師如何來檢查內存?
TCP reset和內存有何關係？要靠猜嗎？
這個連接是一種情況http://isc.sans.org/diary.html?storyid=1538&isc=90f7e0cf745ef88d67ec 如果一些DNS伺服器宕掉，當此伺服器發請求的時候就會收到信息，這個IP地址有可能是壞的DNS伺服器地址，有可能是unknow IP。
何況在收到這些錯誤信息的前後，你會發現機器仍然在工作。
