prometheus / prometheus/node_exporter
the /sys/devices/system/cpu/isolated file is null ,Node-exporter fails to start
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13.8k
- Forks
- 2.7k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 8
Description
sfs|overlay|proc|procfs|pstore|rpc_pipefs|securityfs|selinuxfs|squashfs|sysfs|tracefs)$
panic: Couldn't create metrics handler: couldn't create collector: Unable to get isolated cpus: strconv.Atoi: parsing " (null)": invalid syntax
goroutine 1 [running]:
main.newHandler(0x1, 0x28, {0xcef880, 0xc00004a4c0})
/app/node_exporter.go:69 +0x2ab
main.main()
/app/node_exporter.go:201 +0x128d
the /sys/devices/system/cpu/isolated file is null
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 at node_exporter.go:69, where handler creation fails while collecting isolated CPUs, and inspect how /sys/devices/system/cpu/isolated is read and parsed. Reproduce the failure with the reported “(null)” value and verify that node_exporter starts successfully while preserving isolated-CPU metrics for valid input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, linux
- Domain
- observability, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100