www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Corey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-8843) updates to fail2ban configuration do not trigger restart to fail2ban daemon
Date Tue, 09 Dec 2014 22:20:13 GMT

    [ https://issues.apache.org/jira/browse/INFRA-8843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240163#comment-14240163
] 

Geoffrey Corey commented on INFRA-8843:
---------------------------------------

Fail2ban is now set to be always on on hades. Need to movie it out to the correct yaml file
now.

> 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)

Mime
View raw message