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
I am also currently working on building an NfSen container, but it’s not ready for sharing yet. Regarding your case, I see two potential issues:
1.) Can not get semaphore" at libexec/Nfsync.pm line 48 This occurs due to Docker build isolation, its not a problem during runtime (docker run).
2.) setlogsock(): type='unix': path not available at /opt/nfsen/libexec/Log.pm line 50 NfSen requires a syslog daemon, such as rsyslogd or syslog2stdout, to function.
Run nfdump on the nfcapd.YYYYMMDDhhmm files. If they show nothing, then that's why nfsen shows nothing. (Also check the size of the files with ls -l, ones with no flows will be very small)
Run tcpdump inside the container to check if flow data is arriving. Check the port number matches the %sources definition in nfsen.conf.
Your docker compose top doesn't show any nfcapd process, possibly due to truncated output; try running ps inside the container to see what flags it's running with, which again will tell you what port it's listening on.
Hello
I'm trying to run nfdump/nfsen in a container on:
Everything seems to start ok, i'm seeng new nfdump files in the folder, so it feels like it is able to get data from my router,
this is what i see in the container log:
UI is also accessible, but it is empty:
How can i troubleshoot this?
The text was updated successfully, but these errors were encountered: