BIND 10 #3369: auth asio error messages at shutdown CC_ASYNC_READ_FAILED , AUTH_SERVER_FAILED, CC_WRITE_ERROR
BIND 10 Development
do-not-reply at isc.org
Thu Mar 6 19:49:50 UTC 2014
#3369: auth asio error messages at shutdown CC_ASYNC_READ_FAILED ,
AUTH_SERVER_FAILED, CC_WRITE_ERROR
----------------------------------------+----------------------------------
Reporter: jreed | Owner:
Type: defect | Status: new
Priority: medium | Milestone: New Tasks
Component: b10-auth | Keywords:
CVSS Scoring: | Sensitive: 0
Defect Severity: N/A | Sub-Project: DNS
Feature Depending on Ticket: | Estimated Difficulty: 0
Add Hours to Ticket: 0 | Total Hours: 0
Internal?: 0 |
----------------------------------------+----------------------------------
I am seeing errors like the following when shutting down when using
multiple auth servers.
{{{
2014-03-05 13:36:14.734 ERROR [b10-auth.cc/26975] CC_ASYNC_READ_FAILED
asynchronous read failed (error code = 104)
2014-03-05 13:36:14.735 FATAL [b10-auth.auth/26975] AUTH_SERVER_FAILED
server failed: asynchronous read failed
2014-03-05 13:36:14.735 FATAL [b10-auth.cc/26975] CC_WRITE_ERROR error
writing data to command channel (Broken pipe)
terminate called after throwing an instance of 'isc::cc::SessionError'
what(): ASIO write failed: Broken pipe
}}}
Here is a longer different example:
{{{
2014-03-05 14:05:45.769 INFO [b10-init.init/27845] BIND10_RECEIVED_SIGNAL
recei
ved signal SIGTERM
2014-03-05 14:05:45.769 INFO [b10-init.init/27845] BIND10_SHUTDOWN
stopping the
server
2014-03-05 14:05:45.770 INFO [b10-init.init/27845]
BIND10_CONFIGURATOR_STOP bin
d10 component configurator is shutting down
2014-03-05 14:05:45.770 INFO [b10-init.init/27845] BIND10_COMPONENT_STOP
compon
ent Socket creator is being stopped
2014-03-05 14:05:45.770 INFO [b10-init.init/27845]
BIND10_SOCKCREATOR_TERMINATE
terminating socket creator
2014-03-05 14:05:45.770 INFO [b10-init.init/27845] BIND10_COMPONENT_STOP
compon
ent msgq is being stopped
2014-03-05 14:05:45.770 INFO [b10-init.init/27845] BIND10_COMPONENT_STOP
compon
ent b10-auth is being stopped
2014-03-05 14:05:45.770 INFO [b10-init.init/27845] BIND10_STOP_PROCESS
asking b
10-auth to shut down
2014-03-05 14:05:45.771 INFO [b10-init.init/27845] BIND10_COMPONENT_STOP
compon
ent cfgmgr is being stopped
2014-03-05 14:05:45.771 INFO [b10-init.init/27845] BIND10_STOP_PROCESS
asking c
fgmgr to shut down
2014-03-05 14:05:45.771 INFO [b10-init.init/27845] BIND10_COMPONENT_STOP
component b10-auth-3 is being stopped
2014-03-05 14:05:45.771 INFO [b10-init.init/27845] BIND10_STOP_PROCESS
asking b10-auth-3 to shut down
2014-03-05 14:05:45.771 INFO [b10-auth.auth/27855] AUTH_SERVER_EXITING
exiting
2014-03-05 14:05:45.771 INFO [b10-init.init/27845] BIND10_COMPONENT_STOP
component b10-auth-2 is being stopped
2014-03-05 14:05:45.771 INFO [b10-init.init/27845] BIND10_STOP_PROCESS
asking b10-auth-2 to shut down
2014-03-05 14:05:45.771 INFO [b10-init.init/27845] BIND10_COMPONENT_STOP
component b10-auth-4 is being stopped
2014-03-05 14:05:45.772 INFO [b10-auth.auth/27855]
AUTH_DATASRC_CLIENTS_BUILDER_STOPPED data source builder thread stopped
2014-03-05 14:05:45.772 INFO [b10-init.init/27845] BIND10_STOP_PROCESS
asking b10-auth-4 to shut down
2014-03-05 14:05:45.772 INFO [b10-cfgmgr.cfgmgr/27853]
CFGMGR_STOPPED_BY_COMMAND received shutdown command, shutting down
2014-03-05 14:05:45.772 INFO [b10-auth.auth/27856] AUTH_SERVER_EXITING
exiting
2014-03-05 14:05:45.773 INFO [b10-auth.auth/27856]
AUTH_DATASRC_CLIENTS_BUILDER_STOPPED data source builder thread stopped
2014-03-05 14:05:45.774 ERROR [b10-auth.cc/27857] CC_ASYNC_READ_FAILED
asynchronous read failed (error code = 104)
2014-03-05 14:05:45.774 ERROR [b10-auth.cc/27858] CC_ASYNC_READ_FAILED
asynchronous read failed (error code = 104)
2014-03-05 14:05:45.775 FATAL [b10-auth.auth/27857] AUTH_SERVER_FAILED
server failed: asynchronous read failed
2014-03-05 14:05:45.775 FATAL [b10-auth.auth/27858] AUTH_SERVER_FAILED
server failed: asynchronous read failed
2014-03-05 14:05:45.775 FATAL [b10-auth.cc/27857] CC_WRITE_ERROR error
writing data to command channel (Broken pipe)
terminate called after isc:: [b10-auth.cc/27858] CC_WRITE_ERROR error
writing data to command channel (Broken pipe)
what(): ASIO write failed: Broken pipe
terminate called after throwing an instance of 'isc::cc::SessionError'
what(): ASIO write failed: Broken pipe
2014-03-05 14:05:46.773 INFO [b10-init.init/27845] BIND10_PROCESS_ENDED
process 27850 of Socket creator ended with status 0
2014-03-05 14:05:46.792 INFO [b10-init.init/27845] BIND10_PROCESS_ENDED
process 27851 of msgq ended with status 0
2014-03-05 14:05:46.793 INFO [b10-init.init/27845] BIND10_PROCESS_ENDED
process 27853 of cfgmgr ended with status 0
2014-03-05 14:05:46.793 INFO [b10-init.init/27845] BIND10_PROCESS_ENDED
process 27855 of b10-auth ended with status 0
2014-03-05 14:05:46.793 INFO [b10-init.init/27845] BIND10_PROCESS_ENDED
process 27856 of b10-auth-3 ended with status 0
2014-03-05 14:05:46.793 INFO [b10-init.init/27845] BIND10_PROCESS_ENDED
process 27857 of b10-auth-2 ended with status 6
2014-03-05 14:05:46.793 INFO [b10-init.init/27845] BIND10_PROCESS_ENDED
process
2014-03-05 14:05:46.793 INFO [b10-init.init/27845] BIND10_PROCESS_ENDED
process 27858 of b10-auth-4 ended with status 6
2014-03-05 14:05:46.793 INFO [b10-init.init/27845]
BIND10_SHUTDOWN_COMPLETE all processes ended, shutdown complete
}}}
I saw this with the bind10-1.2.0beta1-release.
--
Ticket URL: <http://bind10.isc.org/ticket/3369>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list