Unsure what is going on here.
I've done logrotate -f /etc/logrotate.conf thinking log files being chewed up causing fail2ban to consume CPU.
i have 3 instances (different installs) where fail2ban is eating 60-90% CPU constantly. Other installs I have do not have this issue. They are cloud available. Cloud installs. Never had this issue before
I've had to kill httpd to help with CPU. also have skewed the ssh port.
There any known bug? As on 2.1.1 release I did have an initial issue with NTP / time/date configuration. Had to re-config it via timedatectl, as configuring it via the vitalPBX admin settings didnt seem to work.
starting to get annoyed that fail2ban is consuming so much CPU and causing drop calls.
VPS is a cloud instance, with a cloud provider.
Appears things are nominal as of now. I skewed ssh port, dropped traffic to port 22 via firewall rule, and logrotated.. etc. Appears to of been a big attack.
Although, 2.1.-06 release installs were fine? Only the 18.104.22.168 had issues.
Update was done via yum update -y