Forum

Unified Communications System

Help us to improve VitalPBX

Processing ...
USD
fail2ban eating cpu...
 

fail2ban eating cpu - 2.1.1  

  RSS

toxicfusion
(@toxicfusion)
Trusted Member
Joined: 6 months ago
Posts: 55
26/12/2018 10:49 pm  

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.


Quote
mrivera
(@ing-joserivera26)
Developer Admin
Joined: 1 year ago
Posts: 1047
02/01/2019 8:19 am  

How did you apply the update, did you make the update from GUI or CLI?, if you did it from CLI, which command did you use?


ReplyQuote
mrivera
(@ing-joserivera26)
Developer Admin
Joined: 1 year ago
Posts: 1047
02/01/2019 9:17 am  

Where do you have installed vitalpbx? in a VPS, Virtual Machine or Bare Metal?


ReplyQuote
toxicfusion
(@toxicfusion)
Trusted Member
Joined: 6 months ago
Posts: 55
03/01/2019 8:45 am  

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 2.1.1.1 had issues.

 

Update was done via yum update -y

 


ReplyQuote
mrivera
(@ing-joserivera26)
Developer Admin
Joined: 1 year ago
Posts: 1047
03/01/2019 10:03 am  

After a full update  (yum update), the next most recommendable step is make a full restart of the machine.


ReplyQuote
Share:
  
Working

Please Login or Register