Skip to content

Sometimes appear eBPF warning messages after reboot. #868

@Tandaran3

Description

@Tandaran3

Describe the bug
About once for ten reboots opensnitch show two warning messages about kernel incompatibility with eBPF. Despite this, opensnitch and gui works fine. If they did not appear immediately after reboot/cold start, then in the future during the high hours work they will not appear.

Include the following information:

  • OpenSnitch 1.6.0rc4/rc5
  • OS: Devuan 4.0
  • Version Chimaera
  • Window Manager: XFCE4
  • Kernel version: Linux devuan 5.10.0-21-amd64 1 SMP Debian 5.10.162-1 (2023-01-21) x86_64 GNU/Linux

To Reproduce
Whean DE fully loaded a few seconds after this, two warning messages appear.

Steps to reproduce the behavior:
Just reboot 10-15 times and messages appear.

Post error logs:
�[2m[2023-02-28 10:40:28]�[0m �[97m�[104m IMP �[0m Start writing logs to /var/log/opensnitchd.log
�[2m[2023-02-28 10:40:28]�[0m �[97m�[41m ERR �[0m
unable to load eBPF module (opensnitch.o). Your kernel version (5.10.0-21-amd64) might not be compatible.
If this error persists, change process monitor method to 'proc'
�[2m[2023-02-28 10:40:28]�[0m �[97m�[41m ERR �[0m [eBPF]:
unable to load eBPF module (opensnitch.o). Your kernel version (5.10.0-21-amd64) might not be compatible.
If this error persists, change process monitor method to 'proc'
�[2m[2023-02-28 10:40:28]�[0m �[97m�[43m WAR �[0m error starting ebpf monitor method:
unable to load eBPF module (opensnitch.o). Your kernel version (5.10.0-21-amd64) might not be compatible.
If this error persists, change process monitor method to 'proc'
�[2m[2023-02-28 10:40:28]�[0m �[97m�[43m WAR �[0m Unable to set new process monitor (ebpf) method from disk:
unable to load eBPF module (opensnitch.o). Your kernel version (5.10.0-21-amd64) might not be compatible.
If this error persists, change process monitor method to 'proc'
�[2m[2023-02-28 10:40:47]�[0m �[97m�[104m IMP �[0m UI connected, dispathing queued alerts: 0
�[2m[2023-02-28 10:40:47]�[0m �[97m�[43m WAR �[0m notification channel closed by the server
�[2m[2023-02-28 10:40:48]�[0m �[97m�[41m ERR �[0m Connection to the UI service lost.
�[2m[2023-02-28 10:40:49]�[0m �[97m�[104m IMP �[0m UI connected, dispathing queued alerts: 0

Screenshots
1

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions