Failed to create BPF map | Failed to load BPF object | Fedora 36 (Server Edition)

Hi,

I have noticed two new logs (the only existing logs) after updating to Fedora 36 (Server Edition), and the logs for F35 have been fixed.

The two systemd logs:

  1. Failed to load BPF object: Operation not permitted
  2. Failed to create BPF map: Operation not permitted

It showed up right after the upgrade from F35 to F36.

Let me know if more information is needed.

Thanks!

1 Like

To get an idea on what is needed please read #start-here if you not done already.

The error you show us says Operation not permitted. To see which operation check in the log sort before what happens.

To get an idea what causes the error please have a look here:

1 Like

Thank you for the information.

My apologies, but I am not exactly sure what I would add after the + for ExecStartPre=+. Would it be ExecStartPre=+/usr/lib/systemd/systemd --user?

I am not an advanced user, so I apologize. I tried digesting that information along with https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecStart= and I am not quite understanding it. Maybe I should just leave it be? I’m not sure how serious it is.

I added some information from the log below in case it helps:

systemd
Failed to create BPF map: Operation not permitted
CODE_FILE src/core/bpf-lsm.c
CODE_FUNC prepare_restrict_fs_bpf
CODE_LINE 76
ERRNO 1
PRIORITY 3
SYSLOG_FACILITY 3
SYSLOG_IDENTIFIER systemd
_AUDIT_SESSION 2
_CAP_EFFECTIVE 0
_CMDLINE /usr/lib/systemd/systemd --user
_COMM systemd
_EXE /usr/lib/systemd/systemd
_SELINUX_CONTEXT unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
_SOURCE_REALTIME_TIMESTAMP 1653025103470111
_SYSTEMD_CGROUP /user.slice/user-1000.slice/user@1000.service/init.scope
_SYSTEMD_SLICE user-1000.slice
_SYSTEMD_UNIT user@1000.service
_SYSTEMD_USER_SLICE -.slice
_SYSTEMD_USER_UNIT init.scope
_TRANSPORT journal
__CURSOR s=6b06d4a0c6164fe488d978eab364477f;i=2033f;b=d801a3874e554298b721daf9b237ecc6;m=fc4774;t=5df6ae618de3f;x=8d1f985c80fd33c

Thanks!

The question in the link I posted you, was that the user can start the command in the terminal while be logged in as his user.

But starting the same command while booting not works because the system not has sufficient rights. It can be that a script who gets executed while booting in a users space (–user) makes problems.

If the @server group should help you they also need a minimum of information.

Unfortunately from the information you gave her I can’t see if this is a script who is needed to run after the update/upgrade or if it is caused by a config option you or admin added to configure the system.

I wonder if the above is the actual cause?

yes could be … but i think there is an user right issue too.

CODE_FILE src/core/bpf-lsm.c
CODE_FUNC prepare_restrict_fs_bpf
CODE_LINE 76

.c is it not a c library? maybe update a plugin etc.

It’s a bug, have a look at, 2084955 – libbpf failed to load object

2 Likes