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 525
    • Issues 525
    • 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
  • #264

Closed
Open
Created May 16, 2018 by Ray Bellis@rayDeveloper

BIND 9.12.1 process hang

Summary

BIND 9.12.1 hung, and stopped responding to queries, but didn't die.

Steps to reproduce

unknown

What is the current bug behavior?

The BIND process stopped responding to queries. A kill -9 was required to stop the process - a normal "kill" didn't work.

Unfortunately I had already stopped it before @wpk suggested getting a core dump.

What is the expected correct behavior?

BIND doesn't hang :p

Relevant configuration files

Trivial validating resolver configuration, on the ISC open resolver.

options {
        max-cache-size 200M;
        allow-query-cache { any; };
        allow-recursion { any; };
        max-udp-size 1024;
        edns-udp-size 1024;
        dnssec-enable yes;
        dnssec-validation auto;
};

Relevant logs and/or screenshots

14-May-2018 05:17:19.138   validating ./SOA: got insecure response; parent indicates it should be secure
14-May-2018 05:17:19.162 shutting down
14-May-2018 05:17:19.162 stopping statistics channel on 127.0.0.1#9004
14-May-2018 05:17:19.162 stopping command channel on 127.0.0.1#8004
14-May-2018 05:17:19.237 no longer listening on 127.0.0.1#5004

Possible fixes

No idea.

Assignee
Assign to
Time tracking