Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BR]: fail2ban.service: Main process exited, code=exited, status=255/n/a #3462

Closed
hoochanlon opened this issue Feb 20, 2023 · 3 comments
Closed

Comments

@hoochanlon
Copy link

reinstall not useful.

catch2023-02-20 10 25 15

@hoochanlon hoochanlon added the bug label Feb 20, 2023
@sebres
Copy link
Contributor

sebres commented Feb 20, 2023

Our issue template says clearly and explicitly what description exactly you need to provide.
It is impossible to help you without more information.
For instance I see 4 errors in the screenshot (but not the error messages), and since they are from configreader and jailreader, I guess some jail configuration is invalid.
Thus closed unless more info provided.

@sebres sebres closed this as not planned Won't fix, can't repro, duplicate, stale Feb 20, 2023
@hoochanlon
Copy link
Author

hoochanlon commented Feb 20, 2023

Thanks. I found it.

  1. Best to update yum and epel-release
  2. CentOS 7 and above require fail2ban-firewalld and fail2ban-systemd
  3. It is recommended to replace vi /etc/fail2ban/jail.config with vi /etc/fail2ban/jail.local.Keeping the negative effects of the operation localized.
    3.1. Because in doing so, even if the negative effects of improper configuration can be controlled locally, jail.local itself. Also easy to debug.

For example:

funcry

yum install epel-release -y && yum update -y
yum install fail2ban-firewalld fail2ban-systemd -y 
systemctl enable fail2ban.service && systemctl start fail2ban.service

Refer:

@hoochanlon
Copy link
Author

hoochanlon commented Feb 20, 2023

PS: I found "Sorry but the jail 'sshd' does not exist" problem.

catch2023-02-21 00 04 36

Solution:

  1. First,I checked that the sshd running in the system is normal.(systemctl status sshd.service)
  2. This is related to the module name specified in the configuration file

catch2023-02-21 09 55 47

Ref:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants