Restart fail2ban after ferm restart #2465
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After a ferm restart, the fail2ban iptables rules are not restored. There is already some code to reload fail2ban after a ferm restart but that doesn't seem to work. fail2ban-client reload/restart and
systemctl reload fail2ban
do not restore its iptables rules after a ferm restart; butsystemctl restart fail2ban
does.I am assuming the host is using systemd, however. Not sure if that's a problem, but this fixes it for me.