iovisor / iovisor/bcc

Error in bcc-tool execution

Open
#3,018 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
22.7k
Forks
4.1k
Avg merge
10d 4h
Merged PRs (30d)
3

Description

Hello Team,

I have successfully installed bcc-tools on the CoreOS toolbox. I am getting error when executing tools:

sh-4.4# ./nodestat
Tracing... Output every 1 secs. Hit Ctrl-C to end
sh: modprobe: command not found
Unable to find kernel headers. Try rebuilding kernel with CONFIG_IKHEADERS=m (module)
chdir(/lib/modules/4.18.0-147.8.1.el8_1.x86_64/build): No such file or directory
Traceback (most recent call last):
File "./lib/ustat", line 305, in
Tool().run()
File "./lib/ustat", line 297, in run
self._loop_iter()
File "./lib/ustat", line 246, in _loop_iter
self._attach_probes()
File "./lib/ustat", line 224, in _attach_probes
self.bpf = BPF(text=program)
File "/usr/lib/python3.6/site-packages/bcc/__init__.py", line 347, in __init__
raise Exception("Failed to compile BPF module %s" % (src_file or ""))
Exception: Failed to compile BPF module

Thanks

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the failure by running ./nodestat in the CoreOS toolbox, then inspect ./lib/ustat around _attach_probes and the bcc BPF initialization shown in the traceback. Check the reported modprobe and kernel-header paths first; done means the tool starts and attaches its probes without the displayed compilation errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, python
Domain
observability, operating-systems, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.