BIND 10 #1903: allow bind10 --data-path to be used for msgq_socket (and others)

BIND 10 Development do-not-reply at isc.org
Fri Apr 20 17:39:57 UTC 2012


#1903: allow bind10 --data-path to be used for msgq_socket (and others)
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  enhancement   |                       Status:  new
            Priority:  low           |                    Milestone:  New
           Component:  Boss of BIND  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 Ran "bind10 -p ~/tmp" fails with:
 {{{

 2012-04-20 17:31:58.426 INFO  [b10-boss.boss] BIND10_STARTING_PROCESS
 starting process b10-msgq
 2012-04-20 17:32:03.468 ERROR [b10-boss.boss]
 BIND10_COMPONENT_START_EXCEPTION component msgq failed to start: Unable to
 connect to c-channel after 5 seconds
 2012-04-20 17:32:03.468 ERROR [b10-boss.boss] BIND10_COMPONENT_FAILED
 component msgq (pid None) failed: unknown condition
 2012-04-20 17:32:03.468 FATAL [b10-boss.boss] BIND10_COMPONENT_UNSATISFIED
 component msgq is required to run and failed
 2012-04-20 17:32:03.468 ERROR [b10-boss.boss]
 BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator plan interrupted, only 1
 of 3 done
 2012-04-20 13:17:05.199 INFO  [b10-boss.boss] BIND10_KILLING_ALL_PROCESSES
 killing all started processes
 2012-04-20 13:17:05.199 INFO  [b10-boss.boss] BIND10_KILL_PROCESS killing
 process Socket creator
 2012-04-20 13:17:05.199 WARN  [b10-boss.boss] BIND10_SOCKCREATOR_KILL
 killing the socket creator
 2012-04-20 13:17:05.199 FATAL [b10-boss.boss] BIND10_STARTUP_ERROR error
 during startup: Unable to start b10-msgq: Component failed during startup

 }}}

 That doesn't tell why.

 Also why is BIND10_SOCKCREATOR_KILL done? (Documentation says "This should
 not happen usually.")

 Run it again with -v:

 {{{
 Traceback (most recent call last):
   File "/usr/local/libexec/bind10-devel/b10-msgq", line 545, in <module>
     setup_result = msgq.setup()
   File "/usr/local/libexec/bind10-devel/b10-msgq", line 194, in setup
     self.setup_listener()
   File "/usr/local/libexec/bind10-devel/b10-msgq", line 180, in
 setup_listener
     raise e
   File "/usr/local/libexec/bind10-devel/b10-msgq", line 173, in
 setup_listener
     self.listen_socket.bind(self.socket_file)
 socket.error: [Errno 13] Permission denied
 }}}

 Now I see the manual page already mentions that --data-path doesn't
 support it yet but may be extended.

 I am opening this ticket as a feature request so it will work for msgq and
 other files.

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


More information about the bind10-tickets mailing list