Opened 9 years ago

Closed 8 years ago

#304 closed defect (fixed)

bindctl error after "Boss shutdown"

Reported by: jreed Owned by:
Priority: medium Milestone:
Component: ~bind-ctl (obsolete) Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 0.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


> Boss shutdown
send the command to cmd-ctrld
received reply: {}
> quit
[Errno 111] Connection refused 
Failed to connect with b10-cmdctl module, is it running?

Error message shouldn't be there when exiting, or at least more friendly.

Also see different errno:

> exit
[Errno 61] Connection refused


Change History (5)

comment:1 Changed 9 years ago by jelte

I was wondering, should we make bindctl recognize this specific command and quit automatically?

comment:2 Changed 9 years ago by zhanglikun

or should we add one special command 'exit' or 'quit' to bindctl? currently, the only way to quit from bindctl is the command 'ctrl + c' .

comment:3 Changed 9 years ago by stephen

The issue goes deeper than just the error after "Boss shutdown". It is about whether bindctl should be able to run independently of the rest of the system.

The particular case I'm thinking of is ability to alter parameters without starting the system. At the time of writing, the parameters controlling whether the authoritative or recursive server starts are parameters of Boss; as shipped, the authoritative server will start by default. Unless you edit the .spec files, configuring BIND 10 to run the recursive server requires starting BIND 10 (and so starting auth), running bindctl to change the parameters, stopping BIND 10, then starting BIND 10.

I think it should be possible to run bindctl independently of the rest of the system - it should connect to the message queue process if one is available or create it if not.

comment:4 Changed 8 years ago by vorner

  • Defect Severity set to N/A
  • Sub-Project set to DNS

Closed two duplicates of this, #477 and #637.

comment:5 Changed 8 years ago by shane

  • Resolution set to fixed
  • Status changed from new to closed

Looks a lot cleaner now:

shane@helium:~$ /opt/bind10/bin/bindctl 
["login success "] login as root
> Boss shutdown 
> quit
Failed to send request, the connection is closed

Running bindctl offline, while interesting, is really a separate issue. I've created ticket #1694 for that.


Note: See TracTickets for help on using tickets.