You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "David Nalley (JIRA)" <ji...@apache.org> on 2014/12/09 22:05:12 UTC
[jira] [Commented] (INFRA-8843) updates to fail2ban configuration
do not trigger restart to fail2ban daemon
[ https://issues.apache.org/jira/browse/INFRA-8843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240058#comment-14240058 ]
David Nalley commented on INFRA-8843:
-------------------------------------
See commit b4fdd3dcf2984f101d87b76fa1d104039e9fb30d for what I updated.
> updates to fail2ban configuration do not trigger restart to fail2ban daemon
> ---------------------------------------------------------------------------
>
> Key: INFRA-8843
> URL: https://issues.apache.org/jira/browse/INFRA-8843
> Project: Infrastructure
> Issue Type: Bug
> Components: Puppet
> Reporter: David Nalley
> Assignee: Geoffrey Corey
>
> I added a fix for sshd in fail2ban and two things happened:
> 1. fail2ban is not configured to ensure that it's always running.
> root@hades:/var/log# service fail2ban status
> * Status of authentication failure monitor * fail2ban is not running
> 2. After I restarted fail2ban and the new config came in, nothing triggered a restart or reload after the new configuration was present.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)