Project

General

Profile

Actions
Copy link

Bug #14788

closed

NtopNG high swap usage

Added by Denis O'Leary over 1 year ago. Updated over 1 year ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
ntop
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
23.05.1
Affected Architecture:
amd64

Description

Issue:
100% SWAP usage on pfSense+ 23.05.1-RELEASE after a number of days of uptime when the package NtopNG 0.8.13_10 is running on the system.

Troubleshooting Done:
Found on the UI of pfSense+ that the SWAP usage was at 100% after a number of days being up. Checking with top -w and running the command "o" checking SWAP usage I can see that ntopng is causing the swap to be high - I disabled the package and swap went down to 8% - This looks to have confirmed an issue with the package on the latest public release of pfSense+

top usage:
[23.05.1-RELEASE][]/root: top -w

last pid: 57647; load averages: 0.68, 0.63, 0.62 up 33+07:21:24 01:09:25
99 processes: 1 running, 90 sleeping, 8 zombie
CPU: 1.5% user, 0.0% nice, 0.3% system, 0.0% interrupt, 98.2% idle
Mem: 1971M Active, 706M Inact, 3081M Laundry, 1016M Wired, 546M Buf, 1093M Free
Swap: 3852M Total, 3852M Used, K Free, 100% Inuse

PID USERNAME    THR PRI NICE   SIZE    RES SWAP STATE    C   TIME    WCPU COMMAND
98924 root         60  20    0    11G  3337M   0B nanslp   0 106.4H   5.46% ntopng
17158 root          1  20    0    92M    35M   0B piperd   0 113:16   0.73% php_pfb
10250 unbound       4  20    0   297M   206M   0B kqread   3   0:35   0.03% unbound

System details:
CPU: Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz
hardware threads
AES-NI CPU Crypto: Yes (active)
IPsec-MB Crypto: Yes (inactive)
QAT Crypto: No

RAM: 8GB

Actions
Copy link
 #1

Updated by Jim Pingle over 1 year ago

  • Project changed from pfSense Plus to pfSense Packages
  • Subject changed from NtopNG high swap usage - pfSense+ 23.05.1-RELEASE to NtopNG high swap usage
  • Category changed from Services to ntop
  • Status changed from New to Not a Bug
  • Release Notes deleted (Default)

(a) Not all swap usage is bad: https://docs.netgate.com/pfsense/en/latest/hardware/memory.html#not-all-swap-usage-is-bad -- Just because it's high doesn't necessarily mean it's a problem unless other processes are failing to run or are being killed because you are out of RAM.

(b) We don't have control over ntopng's memory behavior, that's entirely up to your configuration and how it behaves in ntopng. Any questions you have there should be directed toward ntopng not pfSense.

Actions
Copy link

Also available in: Atom PDF