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:04:12 UTC

[jira] [Created] (INFRA-8843) updates to fail2ban configuration do not trigger restart to fail2ban daemon

David Nalley created INFRA-8843:
-----------------------------------

             Summary: 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


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)