Opened 8 years ago

Closed 6 years ago

#1903 closed enhancement (wontfix)

allow bind10 --data-path to be used for msgq_socket (and others)

Reported by: jreed Owned by:
Priority: low Milestone: Remaining BIND10 tickets
Component: ~Boss of BIND (obsolete) Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 5 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

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.

Subtickets

Change History (5)

comment:1 Changed 8 years ago by jreed

And for the xfrout socket file.

comment:2 Changed 8 years ago by vorner

I believe these sockets should live under /tmp. After all, many sockets live there. And /tmp should be readable for anybody.

comment:3 Changed 8 years ago by shane

  • Milestone New Tasks deleted

comment:4 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:5 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check http://bundy-dns.de.

Closing ticket.

Note: See TracTickets for help on using tickets.