Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 532
    • Issues 532
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 101
    • Merge requests 101
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #767

Closed
Open
Created Dec 06, 2018 by Cathy Almond@cathyaDeveloper

Update querytrace to become toggle-able on/off while named is running

Description

Querytrace logging is currently only useful when we have a readily reproducible problem that it would help to debug.

Nobody is going to run it just in case of an intermittent problem because the CPU overhead is far too high.

But we do encounter intermittent problems where we need to enable querytrace while named is running, once the problem has occurred, and without restarting named first. Once such example is #11195/#44676 (9.11.0-P2 crashes, memory consumption, odd errors with RPZ).

Would it be possible to frame the querytrace code in such away that it is completely inactive (although compiled in), thus not incurring the CPU overhead, until it is toggled 'active' via RNDC?

Request

As above. (With some appreciation that this is not trivial to implement effectively, as it will need to wrap the code that does the logging inside logic that determines whether or not the output is wanted, so that the work to prepare the output is squelched, as well as the emitted log messages).

Links / references

Support #13776

Bugs #45070

Edited Dec 14, 2018 by Cathy Almond
Assignee
Assign to
Time tracking