-
Notifications
You must be signed in to change notification settings - Fork 673
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory leak ntopng 5.7.230804 since June/July 2023 #7735
Comments
[288859.648241] crond invoked oom-killer: gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 |
@notyourcommy I think the bug is fixed. Overnight new packages will be built: please test them and report. |
5.7.230808 ? Still leaking unfortunately. |
How do you know it's leaking: this is because memory increases or OOM? Can you please share pictures of the memory used and number of flows/hosts? |
Ntop uses all memory then OOM kills it. 20k local hosts, 200k remote hosts, 400k flows |
The number of hosts and flows is steady? I will run a new testing session, hoping to be able to reproduce the issue otherwise I need your help. Stay tuned |
Number of hosts/flows depends on the time of day. I wrote you the "prime time" numbers. (~AVG MAX) |
I have pushed a fix that is included in the build that will be ready at 15:45 CET. Please update at your convenience and report |
Upgrading to 5.7.230809-21278 |
@notyourcommy Any news? |
Unfortunately still leaking - 30GB in ~20 hours. [Pk aug 11 16:54:53 2023] ntopng-S-active invoked oom-killer: gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 |
After debugging the root cause was InfluxDB that was using most of the available memory |
Environment:
What happened:
Since ~June/July 2023 we are observing memory leak (it eats all the ram (32GB) in a day and then OOM kills it)
Ntop/Nprobe config
cat /etc/ntopng/ntopng.conf
-G=/var/run/ntopng.pid
-F="clickhouse;...;ntopng;ntop;midiland"
-i "tcp://127.0.0.1:5556"
-n 3
-x 700000
-X 700000
--ignore-vlans
-v 2
-m
cat /etc/nprobe/nprobe-sflow.conf
-i none
--collector-port 6343
--ntopng "zmq://127.0.0.1:5556"
-–flow-deduplication 15
-n none
-G=/var/run/nprobe-sflow.pid
-T="%IN_SRC_MAC %OUT_DST_MAC %INPUT_SNMP %OUTPUT_SNMP %SRC_VLAN %IPV4_SRC_ADDR %IPV4_DST_ADDR %L4_SRC_PORT %L4_DST_PORT %IPV6_SRC_ADDR %IPV6_DST_ADDR %IP_PROTOCOL_VERSION %PROTOCOL %L7_PROTO %IN_BYTES %IN_PKTS %OUT_BYTES %OUT_PKTS %FIRST_SWITCHED %LAST_SWITCHED %CLIENT_TCP_FLAGS %SERVER_TCP_FLAGS %L7_PROTO_RISK %L7_RISK_SCORE %EXPORTER_IPV4_ADDRESS %DIRECTION%POST_NAT_SRC_IPV4_ADDR %POST_NAT_DST_IPV4_ADDR %POST_NAPT_SRC_TRANSPORT_PORT %POST_NAPT_DST_TRANSPORT_PORT %BGP_PREV_ADJACENT_ASN %BGP_NEXT_ADJACENT_ASN %IPV4_BGP_NEXT_HOP %SRC_AS %DST_AS"
The text was updated successfully, but these errors were encountered: