Why is fail2ban flushlogs using 100% of my Linode's CPU?
Linode Linode Staff
I checked with
htop, and fail2ban flushlogs is using 100% of my Linode's CPU. Why could that be?
tommydavidson Linode Staff
It looks like this issue is related to using compression with fail2ban's log files. I found a post on the
fail2ban GitHub that talks about this, as well as a possible fix.