Hello,I recently noticed high CPU utilization on one of our servers
running htop shows fail2ban as the culprit see screenshot.
I have tried
- Stopping the and restarting the fail2ban servers
- rotating the auth.log file for fail2ban
- deleting the fail2ban sqlite3 database
4.Rebooting the server
Also referenced the following links on the forum
Has anyone else experienced the same issue?
How big is your actual fail2ban.log file? I had a similar situation where the file was CPU. rotated the fail2ban.log and it was instantly down to “normal”
The fail2ban.log is not up to 1mb
For anyone else having this issue,
The issue had to do with the size of access.log file in /var/log/nginx
i rotated the log by running
logrotate -f /etc/logrotate.d/nginx
sudo service fail2ban restart