Hi,
We are running NxFilter 4.6.8.1 on Ubuntu 18.04. For the last three days, the NxFilter process suddenly started consuming 300% CPU during daytime - approx. 07:30 to 18:00.
Here's the weekly VM CPU usage:

And here's the daily usage, where the CPU ramping up can be seen:

Some details of this installation:
NxFilter 4.6.8.1, connected to Active Directory, approx. 500 users and 1000 IPs. Log retention is 1 day, database size is around 11 GB. Using Cloudflare as upstream DNS, no DNS over HTTPS.
Categorization databse is Globlist, classifier is off, default policy is forbid all except the whitelisted domains/keywords.
Here are the thing we tried while trying to find out what's going on:
1. Restarted NxFilter
2. Monitoring UDP/53 traffic on all server interfaces - no flooding or unusual traffic can be seen.
3. Dropped all UDP/53 traffic to the VM for a minute - no change in CPU usage.
4. Switching in log4j.properties from WARN to INFO and then DEBUG to see what's going on - nothing interesting on INFO, too much to filter on DEBUG.
I can provide more info if needed, if logs are requested, please specify at which level.
Thanks in advance!
We are running NxFilter 4.6.8.1 on Ubuntu 18.04. For the last three days, the NxFilter process suddenly started consuming 300% CPU during daytime - approx. 07:30 to 18:00.
Here's the weekly VM CPU usage:
And here's the daily usage, where the CPU ramping up can be seen:
Some details of this installation:
NxFilter 4.6.8.1, connected to Active Directory, approx. 500 users and 1000 IPs. Log retention is 1 day, database size is around 11 GB. Using Cloudflare as upstream DNS, no DNS over HTTPS.
Categorization databse is Globlist, classifier is off, default policy is forbid all except the whitelisted domains/keywords.
Here are the thing we tried while trying to find out what's going on:
1. Restarted NxFilter
2. Monitoring UDP/53 traffic on all server interfaces - no flooding or unusual traffic can be seen.
3. Dropped all UDP/53 traffic to the VM for a minute - no change in CPU usage.
4. Switching in log4j.properties from WARN to INFO and then DEBUG to see what's going on - nothing interesting on INFO, too much to filter on DEBUG.
I can provide more info if needed, if logs are requested, please specify at which level.
Thanks in advance!
Comment