Skip to content

GitLab

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

Closed
Open
Created May 12, 2020 by Michal Nowikowski@godfrydContributor

stork-agent should be able to determine CWD of kea or named processes

@garbled1 reported in #243 (closed):

I keep getting this in my logs:
May 11 05:55:10 pollux stork-agent[29532]: #33 (closed)[33mWARN#033[0m[2020-05-11 05:55:10]          monitor.go:159   cannot get process current working directory: readlink /proc/22855/cwd: permission denied

lrwxrwxrwx 1 bind bind 0 Apr 18 13:32 /proc/22855/cwd -> /var/cache/bind
drwxr-xr-x 9 root root 4096 Oct 12  2019 /var/cache
drwxrwxr-x 2 root bind 4096 May 11 03:19 /var/cache/bind
That is probably apparmor related?

This can be solved by adding:

AmbientCapabilities=CAP_SYS_PTRACE

to service file.

CAP_SYS_PTRACE gives permission to read /proc/<pid>/cwd

Edited May 12, 2020 by Michal Nowikowski
Assignee
Assign to
Time tracking