You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wow ! First time I see this error message !
It would worth identifying a way to reproduce this error and open an issue with it so that IΒ can tell you more.
While I get many matching logs SELECT regexp_replace(body_message, '.* failed to retrieve bpf_prog instructions for event=(.*): .*', '\\1', 'g') as event_uuid FROM "kunai" where body_message like '%failed to retrieve bpf_prog instructions for event%
I get error/no matching events SELECT * from "kunai" WHERE info_event_uuid in (SELECT regexp_replace(body_message, '.* failed to retrieve bpf_prog instructions for event=(.*): .*', '\\1', 'g') as event_uuid FROM "kunai" where body_message like '%failed to retrieve bpf_prog instructions for event%')
(json is flattened by my log system/openobserve)
but got it in journald
host is Ubuntu 22.04 LTS (systemd 249.11-0ubuntu3.15)
I don't get those on the Debian12 host (systemd 252.36-1~deb12u1)
Related to https://www.baeldung.com/linux/systemd-switched-root-deserialize but how it changes between distributions and version is undocumented it seems
Wow, this is weird indeed ... The only thing that could explain (purely based on assumptions) would be that some eBPFΒ programs gets loaded before the root switch but we try to access it after the root switch ! I believe that if this error stays marginal (i.e. only happening at that very specific moment where we are in-between two FS) it can be considered as acceptable. What do you think ?
not really marginal but not regular either. above logs query give me for past week ~26000 matches for a range of 100-3000 in an hour mostly on 22.04.
This appears on Debian12 but very little. As this is a test system that will upgrade short-term or be decommissioned, not a real issue. but uncertain on impacts, missed event logs or else
Even though you see this error, you must see a bpf_prog_load event related to it. If you search back in your logs for the event uuid displayed in the error message you should find one. The only thing is that this event will be not contain all the information, in this case the hashing information of the bpf program will be missing, all the other fields will be correct. The error is just there to attract the attention and also give a details about the failure.
π1 reacted with thumbs up emojiπ1 reacted with thumbs down emojiπ1 reacted with laugh emojiπ1 reacted with hooray emojiπ1 reacted with confused emojiβ€οΈ1 reacted with heart emojiπ1 reacted with rocket emojiπ1 reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
how to fix those or related to kernel options?
Beta Was this translation helpful? Give feedback.
All reactions