Bug #15756
open
NTOPNG db sits in ramdisk on pfsense, filling it up and crashing pfsense
0%
Description
Environment:
OS name: PFSENSE
OS version: 2.7.2-RELEASE
Architecture: amd64
ntopng version/revision: ntopng Community v.5.6.240304 rev.0 (FreeBSD 14.0)
What happened:
by default, ntopng puts it's db files in /var/db/ntopng
when ramdisk is enabled in pfsense, the files are now sitting on the ramdisk and it can be quickly filled up, resulting in various services in pfsense crashing.
How did you reproduce it?
ntopng on pfsense \w ramdisk enabled.
Debug Information:
/var/db: du -sh * | sort -hr | head
317M ntopng
12M rrd
8.1M pkg
748K captiveportaldn.rules
560K cpelements
i think ntopng is using redis ( .rdb ) which loads to the memory, so i think this shouldn't be in ramdisk.
changing the default location from:
/var/db/ntopng
to:
/var/db/pkg/ntopng
should do the trick.
i found this commit is where the problem begins:
https://www.freshports.org/commit.php?category=net&port=ntopng&files=yes&message_id=201812222105.wBML51Ma094362@repo.freebsd.org
you can see the data dir used to sit on the hdd.
---
posted the issue here as well:
https://github.com/ntop/ntopng/issues/8735
Updated by Danilo Zrenjanin about 2 months ago
- Status changed from New to Confirmed
I was able to replicate the observed behavior.
Tested against:
pfSense Plust 24.03, ntopng version 5.6.0
Please be aware that if the entire /var directory is stored in RAM when the ramdisk feature is enabled on pfSense, relocating the ntopng data to a subdirectory within /var, such as /var/db/pkg/ntopng, will not resolve the issue, as it will still reside in RAM.