Why is fail2ban flushlogs using 100% of my Linode's CPU?

Linode Staff

I checked with htop, and fail2ban flushlogs is using 100% of my Linode's CPU. Why could that be?

1 Reply

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.


Please enter an answer

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct