BIND 10 #894: bind10 kills msgq because doesn't know socket

BIND 10 Development do-not-reply at isc.org
Tue May 3 17:14:52 UTC 2011


#894: bind10 kills msgq because doesn't know socket
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  major         |                    Milestone:  New
           Component:  Boss of BIND  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:
Estimated Difficulty:  0             |  Medium
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 Everytime I try today's master on n10 (FreeBSD 8.1-RELEASE), it quickly
 fails with:

 {{{
 bind10 20110223 (BIND 10 20110322)
 [bind10] Checking for already running b10-msgq
 [bind10] Starting b10-msgq
 [bind10] Started b10-msgq (PID 16525)
 [bind10] killing started processes:
 [bind10] - b10-msgq
 [bind10] Error on startup: Unable to start b10-msgq: Unable to connect to
 c-channel after 5 seconds
 }}}

 I added some debugging output and saw the self.msgq_socket_file is None.

 And then I also see:

 {{{
 Traceback (most recent call last):
   File "/usr/local/lib/python3.1/site-packages/isc/cc/session.py", line
 55, in __init__
     self._socket.connect(self.socket_file)
 socket.error: [Errno 2] No such file or directory
 }}}


 When I specifically define to same socket (since sockstat of msgq showed
 me) on command line, it works: --msgq-socket-file
 /var/users/jreed/opt/bind10/var/bind10-devel/msgq_socket

 So by default it is None and so does not set in environment; and since not
 in environment, isc/cc/session.py does:

 {{{
 self.socket_file = bind10_config.BIND10_MSGQ_SOCKET_FILE
 }}}

 I am not sure how that is set. Also I see comment:
 {{{
         # Extract the parameters associated with Bob.  This can only be
         # done after the CC Session is started.
         self.read_bind10_config()
 }}}
 So maybe it is not even set.

 Any ideas?  I don't understand why it works elsewhere. At least for now, I
 can use my workaround.

-- 
Ticket URL: <http://bind10.isc.org/ticket/894>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list