# Initialization issues during scap\_init **URL:** \ **Category:** Sysdig OSS\ **Created:** [November 5, 2025, 1:36pm UTC](https://community.sysdig.com/t/initialization-issues-during-scap-init/706 "2025-11-05T13:36:35Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![apteryx](https://avatars.discourse-cdn.com/v4/letter/a/c4cdca/32.png) [@apteryx](https://community.sysdig.com/u/apteryx)\ **Post date:** [November 5, 2025, 1:36pm UTC](https://community.sysdig.com/t/initialization-issues-during-scap-init/706/1 "2025-11-05T13:36:35Z")
Hi! I’m using `sysdig` via the Guix package, and since recently, it stopped working, printing: ``` $ sudo sysdig --modern-bpf Initialization issues during scap\_init $ uname -r 6.16.12 ``` Has someone encountered this problem? Any idea of how to fix it? I had commented on this bug, where someone else (on Fedora) seemed affected as well: [Failed to install Sysdig in Fedora 42 · Issue #2165 · draios/sysdig · GitHub](https://github.com/draios/sysdig/issues/2165) Thank you! I look forward being able to use this useful tool again. ---
**Author:** ![Maddie](https://sea1.discourse-cdn.com/sysdig/user_avatar/community.sysdig.com/maddie/32/118_2.png) [@Maddie](https://community.sysdig.com/u/Maddie)\ **Post date:** [November 6, 2025, 12:41am UTC](https://community.sysdig.com/t/initialization-issues-during-scap-init/706/2 "2025-11-06T00:41:33Z")
> [@apteryx](#): > > Initialization issues during scap\_init Thank you for the “`uname -r`” , can I request a “`uname -a`” ? I see as well your comment [https://github.com/draios/sysdig/issues/2165](https://github.com/draios/sysdig/issues/2165) Might be an issue with that specific kernel version. Can you try using a different version and see if the results are the same? 2 other ideas: - do you get the same issue with `--universal-bpf` ? - `modern-bpf` uses less kernel space memory and more user space memory. Try provisioning additional resources on the sysdig-agent daemonset `kubectl edit daemonset -n sysdig-agent sysdig-agent` Those are some initial ideas for troubleshooting. I would love to see more from the agent logs as well! looking forward to your reply! ---
**Author:** ![apteryx](https://avatars.discourse-cdn.com/v4/letter/a/c4cdca/32.png) [@apteryx](https://community.sysdig.com/u/apteryx)\ **Post date:** [November 6, 2025, 8:19am UTC](https://community.sysdig.com/t/initialization-issues-during-scap-init/706/3 "2025-11-06T08:19:12Z")
Thanks for your reply! `uname -a` returns `Linux terra 6.16.12 #1 SMP PREEMPT_DYNAMIC 1 x86_64 GNU/Linux` currently. The oldest kernel I have around is 6.14.11 from last June. Next time I reboot I’ll select it and try! Am I supposed to run `sudo sysdig –universal-bpf` to try that option? It prints `sysdig: unrecognized option ‘–universal-bpf’`, at least with my version, which is`sysdig version 0.40.1`. Thanks for the ideas! Meanwhile I tried to build a newer falcosecurity-libs package to use with `sysdig`, but anything newer than 0.20.0 is not compatible even with the latest commit of `sysdig`(that’s been reported here: [Fails to build on 6.13 · Issue #2151 · draios/sysdig · GitHub](https://github.com/draios/sysdig/issues/2151#issuecomment-3495772049) ), so I’m at a loss :-). Oh, by the way, I do not use Kubernetes or the sysdig-agent; I run `sysdig` directly on my workstation. ---
**Author:** ![Iacopo](https://avatars.discourse-cdn.com/v4/letter/i/c89c15/32.png) [@Iacopo](https://community.sysdig.com/u/Iacopo)\ **Post date:** [November 6, 2025, 9:25pm UTC](https://community.sysdig.com/t/initialization-issues-during-scap-init/706/4 "2025-11-06T21:25:55Z")
Hey @apteryx , I think you’re hitting a bpf verifier issue that was fixed [_ **here** _](https://github.com/falcosecurity/libs/pull/2150), could you please provide the output of the following command? ```auto sudo sysdig --modern-bpf --log-level trace ``` ---
**Author:** ![Iacopo](https://avatars.discourse-cdn.com/v4/letter/i/c89c15/32.png) [@Iacopo](https://community.sysdig.com/u/Iacopo)\ **Post date:** [November 7, 2025, 3:58pm UTC](https://community.sysdig.com/t/initialization-issues-during-scap-init/706/5 "2025-11-07T15:58:21Z")
FYI Probably I pointed out the right problem, but the wrong fix, it should be the following: > > > \*\*What type of PR is this?\*\* > > /kind bug > > \*\*Any specific area of the project …related to this PR?\*\* > > /area driver-bpf > /area driver-modern-bpf > > \*\*Does this PR require a change in the driver versions?\*\* > > \*\*What this PR does / why we need it\*\*: > > Linux 6.15-rc1 changed a field name in https://github.com/torvalds/linux/commit/633488947ef66b194377411322dc9e12aab79b65#diff-778d4f53e80041bbe5133320016dbc6603495e37f800d264765ac0ff012d279e > Properly update our bpf probe to build once again. Also, fixed modern ebpf probe to run on that kernel. > > Holding until 6.15-rc6/7 as always. > > \*\*Which issue(s) this PR fixes\*\*: > > Fixes # > > \*\*Special notes for your reviewer\*\*: > > \*\*Does this PR introduce a user-facing change?\*\*: > > > > \`\`\`release-note > fix(driver): fixed build of old bpf probe against linux 6.15-rc1. > \`\`\` ---
**Author:** ![apteryx](https://avatars.discourse-cdn.com/v4/letter/a/c4cdca/32.png) [@apteryx](https://community.sysdig.com/u/apteryx)\ **Post date:** [November 9, 2025, 2:40pm UTC](https://community.sysdig.com/t/initialization-issues-during-scap-init/706/6 "2025-11-09T14:40:51Z")
Hey! That was it! I applied [this patch](https://patch-diff.githubusercontent.com/raw/falcosecurity/libs/pull/2341.patch) [0] to the 0.20.0 `falcosecurity-libs` package in GNU Guix (it applied fine), rebuilt `sysdig` against it, and it now works on my kernel :-). Thanks a lot! I’ll try to follow up on the issue tracker. [0] [https://patch-diff.githubusercontent.com/raw/falcosecurity/libs/pull/2341.patch](https://patch-diff.githubusercontent.com/raw/falcosecurity/libs/pull/2341.patch)