blackbox_exporter cannot start with error 218/CAPABILITIES
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
-
What did you do?
Deploy clusters, blackbox_exporter can't get up.
blackbox_exporter-9115.service: main process exited, code=exited, status=218/CAPABILITIES
-
What did you expect to see?
blackbox_exporter can start normally -
What did you see instead?
blackbox_exporter cannot start normally unless AmbientCapabilities=CAP_NET_RAW is commented out -
What version of TiUP are you using (
tiup --version)?
1.5.6 tiup
Go Version: go1.16.7
Git Ref: v1.5.6
GitHash: 1d1478dbec0d06ef5e909d3323331914538d4cb0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the blackbox_exporter-9115.service definition and the TiUP deployment path that configures AmbientCapabilities=CAP_NET_RAW. Reproduce the status=218/CAPABILITIES failure in the reported cluster setup and compare it with the configuration where that setting is commented out. Done means blackbox_exporter starts normally with the required capability behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100