Opened 7 years ago

Closed 5 years ago

#2554 closed defect (wontfix)

ConfigManager not responding

Reported by: jreed Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: configuration Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: Medium
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 5 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


I thought there was ticket already about this, but search won't find it.

I did the following:

> config add Logging/loggers[0]/output_options
> config set Logging/loggers[0]/output_options[0]/destination file
> config set Logging/loggers[0]/output_options[0]/output /home/reed/work/isc/bind10/log/bind10.log
> config show Logging/loggers[0]/output_options
Logging/loggers[0]/output_options[0]/destination        "file"  string  (modified)
Logging/loggers[0]/output_options[0]/output     "/home/reed/work/isc/bind10/log/bind10.log"     string  (modified)
Logging/loggers[0]/output_options[0]/flush      true    boolean (default)
Logging/loggers[0]/output_options[0]/maxsize    0       integer (default)
Logging/loggers[0]/output_options[0]/maxver     0       integer (default)
> config set Logging/loggers[0]/output_options[0]/maxsize 1048576
> config set Logging/loggers[0]/output_options[0]/maxver 25     
> config commit
Error: Module 'ConfigManager' not responding
Configuration not committed

The process was not hanging though. And it did not crash and restart. I exited bindctl and ran it again and then did the above again with a "config commit" after each step and it worked.


Change History (3)

comment:1 Changed 7 years ago by jwright

  • Defect Severity changed from N/A to Medium
  • Milestone changed from New Tasks to Next-Sprint-Proposed

comment:2 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:3 Changed 5 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

Closing ticket.

Note: See TracTickets for help on using tickets.