evilsocket / opensnitch

OpenSnitch is a GNU/Linux interactive application firewall inspired by Little Snitch.
GNU General Public License v3.0
10.92k stars 510 forks source link

GetInfo() path can't be read #1114

Closed atomGit closed 7 months ago

atomGit commented 7 months ago

check the FAQ and Known Problems: done opensnitchd -check-requirements: all systems go

Describe the bug if i start/restart the daemon i'm seeing this, once, in the log...

[2024-04-03 00:09:17]  ERR  GetInfo() path can't be read

Include the following information:

To Reproduce $ sudo systemctl restart opensnitchd

Post error logs:

[2024-04-03 00:09:17]  IMP  Start writing logs to /var/log/opensnitchd.log
[2024-04-03 00:09:17]  ERR  GetInfo() path can't be read
[2024-04-03 00:09:18]  IMP  UI connected, dispathing queued alerts: 0

Additional context there's this, but the version reported for opensnitch-ebpf-module is temporarily inaccurate (it actually matches opensnitch version)

$ pacman -Qs opensnitch
local/opensnitch 1.6.4-1
    A GNU/Linux application firewall
local/opensnitch-ebpf-module 1.6.5-2
    eBPF process monitor module for opensnitch

PS: i'm liking what i'm seeing with this project and appreciate the work of the devs and contribs - thank you all

gustavo-iniguez-goya commented 7 months ago

Hi @atomGit ,

Change the log level to DEBUG and post the previous logs, there should be a connection attempt just a couple of lines before this log. Also see if the monitor method in use is "ebpf" , it should appear in the logs as Process monitor method ...

Anyway, this error would be better to be reported as Debug. Usually it's not an error, but a limitation in some scenarios, specially when "proc" is used as monitor method.

atomGit commented 7 months ago

the error vanished for some reason

gustavo-iniguez-goya commented 6 months ago

I was about to fix this issue and I've realized that your daemon version was 1.6.2, and this is fixed on 1.6.5 :face_with_spiral_eyes:

thank you for reporting it anyway!