Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
BIND
BIND
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 635
    • Issues 635
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 121
    • Merge Requests 121
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #969

Closed
Open
Created Apr 02, 2019 by Libor Polčák@ipolcak

Error regarding managed-keys-directory option if not owned by the correct user

I am running bind. I have a directory set for the managed-keys-directory in the options of the named.conf. In 9.11.4 the directory was owned by root, group named, bot with rwx access. Everything worked great. I run named as user named.

When I updated to 9.12.2 or 9.12.3, named exited with status 1. There was no syslog entry, no error message. I finally tracked the problem to the directory set up by managed-keys-directory. After I changed the owner to named, bind starts correctly.

Please, can you provide some syslog notice what is going on, so that other users running into similar issue can fix the permissions immediately?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None