ntopng silently exits after consuming all memory about ntopng HOT 6 CLOSED

Upon further analysis the issue seems to be correlated with Network Discovery:
Running in foreground with -v 3 points to ntopng is getting stuck on arp entry from device itself:

22/Dec/2023 16:30:13 [NetworkDiscovery.cpp:273] Received ARP reply from 192.168.100.1
22/Dec/2023 16:30:14 [NetworkDiscovery.cpp:273] Received ARP reply from 192.168.100.1

it repeats this until memory is exhausted ...

If network discovery is disabled - issue of memory exhaustion is not observed.

from ntopng.

@sim4dim I pushed a fix for the notification "encoding" in your first trace,
as of the last trace about the "Received ARP reply from", do you see the same message for the same IP and only that one? Does it print it indefinitely? Who is 192.168.100.1, you said device itself, please clarify. Thank you.

from ntopng.

I am having this message " Received ARP reply from 192.168.100.1" repeating indefinitely. I had misspoke - 192.168.100.1 is cable modem attached to WAN interface not device itself. I have a Virtual IP (192.168.100.100) attached to WAN interface as well.

from ntopng.

In order to figure out what's going on, I added a debug mode to collect some info. Please follow the steps below:

• update ntopng to the latest
• remove -v=3 which is no longer required
• enable debug mode for network discovery

• leave it running for a bit until it starts printing "Received ARP reply from" undefinitely
• download the logs (you can use the gui as below) and provide it to us

from ntopng.

ntopng Community v.6.1.231222 (FreeBSD 13.1) had been running for last 24hr with network discovery enabled with no memory issues and discovery running every 15 min. I will monitor it further.

from ntopng.

Sounds better. I did some change in the last release that changed the way we trigger the discovery, and also the notificaitons. Please keep us posted. Thank you.

from ntopng.