[bind10-dev] CC_TIMEOUT, AUTH_ZONEMGR_COMMS, CC_LENGTH_NOT_READY

[Jeremy C. Reed]

Check this  out. This is a production system that has crashed a few 
times. (I will send other emails about that.) Any ideas about the 
following?

$ grep "2012-11-17" bind10.log  | egrep -1 "CC_TIMEOUT|AUTH_ZONEMGR_COMMS|CC_LENGTH_NOT_READY"        

2012-11-17 08:36:49.947 ERROR [b10-auth.auth] AUTH_ZONEMGR_ERROR 
received error response from zone manager: "[b10-zonemgr] Notified zone 
(30.172.in-addr.arpa., IN) doesn't belong to zonemgr"
2012-11-17 08:36:56.228 ERROR [b10-auth.cc] CC_TIMEOUT timeout reading 
data from command channel
2012-11-17 08:36:56.432 ERROR [b10-auth.auth] AUTH_ZONEMGR_COMMS error 
communicating with zone manager: Timeout while reading data from cc 
session
2012-11-17 08:37:00.432 ERROR [b10-auth.cc] CC_TIMEOUT timeout reading 
data from command channel
2012-11-17 08:37:00.433 ERROR [b10-auth.auth] AUTH_ZONEMGR_COMMS error 
communicating with zone manager: Timeout while reading data from cc 
session
2012-11-17 08:37:02.942 ERROR [b10-zonemgr.zonemgr] 
ZONEMGR_UNKNOWN_ZONE_NOTIFIED notified zone 10.in-addr.arpa. (class IN) 
is not known to the zone manager
--
2012-11-17 08:37:04.948 ERROR [b10-auth.auth] AUTH_ZONEMGR_ERROR 
received error response from zone manager: "[b10-zonemgr] Notified zone 
(30.172.in-addr.arpa., IN) doesn't belong to zonemgr"
2012-11-17 08:37:07.957 ERROR [b10-auth.cc] CC_TIMEOUT timeout reading 
data from command channel
2012-11-17 08:37:07.958 ERROR [b10-auth.auth] AUTH_ZONEMGR_COMMS error 
communicating with zone manager: Timeout while reading data from cc 
session
2012-11-17 08:37:07.958 ERROR [b10-auth.cc] CC_LENGTH_NOT_READY length 
not ready
2012-11-17 08:37:07.958 ERROR [b10-auth.auth] AUTH_ZONEMGR_COMMS error 
communicating with zone manager: ASIO read: data length is not ready
2012-11-17 08:37:17.943 ERROR [b10-zonemgr.zonemgr] 
ZONEMGR_UNKNOWN_ZONE_NOTIFIED notified zone 10.in-addr.arpa. (class IN) 
is not known to the zone manager


Note that AUTH_ZONEMGR_COMMS description says it is a debug message but 
it is sent at the ERROR level.

Also see http://bind10.isc.org/ticket/1938