Opened 10 years ago

Closed 10 years ago

#111 closed defect (invalid)

setting alternative msgq-port fails

Reported by: jreed Owned by: each
Priority: medium Milestone:
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity:
Sub-Project: Feature Depending on Ticket:
Estimated Difficulty: Add Hours to Ticket:
Total Hours: Internal?:


t1:reed$ /home/reed/opt/bind10/sbin/bind10 --m 5399 -v 
BIND 10 v20100310
Checking for already running msgq
Starting msgq using port 5399
Started msgq (PID 11849)
Error on startup: Unable to connect to c-channel after 5 seconds


Change History (5)

comment:1 Changed 10 years ago by jreed

  • Summary changed from setting alternative msgq-port fials to setting alternative msgq-port fails

comment:2 Changed 10 years ago by shane

  • Owner set to mgraff
  • Status changed from new to assigned

Maybe fixed... have a look a.u.b.

comment:3 Changed 10 years ago by shane

  • Owner changed from mgraff to each

Seems possibly related to work that Evan is doing on being able to set alternate IP address as well as port, so assigning to him so he can close this if in fact it works now. (See ticket #167)

comment:4 Changed 10 years ago by jelte

i was working on using domain sockets for msgq on friday and noticed that the ASIO code for c++ clients (lib/cc/ had a hardcoded port number, which most probably causes this :)

(the domain socket file is a bit less hardcoded, though having it completely overridable is still a todo for me, since that requires an api change somewhere, but i want to look at that today, currently it is overridable by an environment variable)

If so, I propose to let this ticket go and focus on mine getting done, reviewed and merged (ticket #183)

comment:5 Changed 10 years ago by shane

  • Resolution set to invalid
  • Status changed from assigned to closed

Okay, closing this because #183 supersedes it.

Note: See TracTickets for help on using tickets.