https://bugs.contribs.org/show_bug.cgi?id=10814

--- Comment #6 from Jean-Philippe Pialasse <[email protected]> ---
(In reply to bunkobugsy from comment #5)
> > Pressing Save actually runs fail2ban-update, modifies db values, my bad.
> 
> but it doesn't produce any effect (for example toggling SEND_MAIL_STATUS),
> it probably needs signal-event fail2ban-conf to be run...

this is another problem, please open another bug report or we will start a mess
there and nothing will get fixed.

however the event is played as planned :
Oct 15 21:38:15 test /etc/e-smith/web/panels/manager/cgi-bin/fail2ban[17419]:
/home/e-smith/db/configuration: OLD
fail2ban=service|BanTime|86400|FilterLocalNetworks|enabled|FindTime|10800|HTTPDbadbotsStatus|enabled|HTTPDoverflowsStatus|enabled|Mail|enabled|status|enabled
Oct 15 21:38:15 test /etc/e-smith/web/panels/manager/cgi-bin/fail2ban[17419]:
/home/e-smith/db/configuration: NEW
fail2ban=service|BanTime|86400|FilterLocalNetworks|enabled|FindTime|10800|HTTPDbadbotsStatus|enabled|HTTPDoverflowsStatus|enabled|Mail|enabled|status|enabled|wordpress|enabled
Oct 15 21:38:15 test esmith::event[17421]: Processing event: fail2ban-update 
Oct 15 21:38:15 test esmith::event[17421]: Running event handler:
/etc/e-smith/events/actions/generic_template_expand
Oct 15 21:38:15 test esmith::event[17421]: expanding /etc/rc.d/init.d/masq 
Oct 15 21:38:15 test esmith::event[17421]:
generic_template_expand=action|Event|fail2ban-update|Action|generic_template_expand|Start|1571189895
240110|End|1571189895 423308|Elapsed|0.183198
Oct 15 21:38:15 test esmith::event[17421]: Running event handler:
/etc/e-smith/events/actions/adjust-services
Oct 15 21:38:15 test esmith::event[17421]: adjusting non-supervised masq
(adjust) 
Oct 15 21:38:15 test esmith::event[17421]:
adjust-services=action|Event|fail2ban-update|Action|adjust-services|Start|1571189895
423552|End|1571189895 885907|Elapsed|0.462355

or even
Oct 15 21:40:09 test /etc/e-smith/web/panels/manager/cgi-bin/fail2ban[18309]:
/home/e-smith/db/configuration: OLD
fail2ban=service|BanTime|86400|FilterLocalNetworks|enabled|FindTime|10800|HTTPDbadbotsStatus|enabled|HTTPDoverflowsStatus|enabled|Mail|enabled|status|enabled|wordpress|disabled
Oct 15 21:40:09 test /etc/e-smith/web/panels/manager/cgi-bin/fail2ban[18309]:
/home/e-smith/db/configuration: NEW
fail2ban=service|BanTime|86400|FilterLocalNetworks|enabled|FindTime|10800|HTTPDbadbotsStatus|enabled|HTTPDoverflowsStatus|enabled|Mail|disabled|status|enabled|wordpress|disabled
Oct 15 21:40:09 test esmith::event[18311]: Processing event: fail2ban-update 
Oct 15 21:40:09 test esmith::event[18311]: Running event handler:
/etc/e-smith/events/actions/generic_template_expand
Oct 15 21:40:09 test esmith::event[18311]: expanding /etc/rc.d/init.d/masq 
Oct 15 21:40:09 test esmith::event[18311]:
generic_template_expand=action|Event|fail2ban-update|Action|generic_template_expand|Start|1571190009
660209|End|1571190009 838613|Elapsed|0.178404
Oct 15 21:40:09 test esmith::event[18311]: Running event handler:
/etc/e-smith/events/actions/adjust-services
Oct 15 21:40:09 test esmith::event[18311]: adjusting non-supervised masq
(adjust) 
Oct 15 21:40:10 test esmith::event[18311]:
adjust-services=action|Event|fail2ban-update|Action|adjust-services|Start|1571190009
838904|End|1571190010 353769|Elapsed|0.514865


but indeed it would need a
/etc/e-smith/events/fail2ban-conf/services2adjust/fail2ban ->restart so also a
fail2ban-conf event as fail2ban-update only acts on masq, ****just clone this
bug with a dedicated subject please*****.
maybe in this case a reload would suffice, need to investigate, hence a new
bug, so we could only keep the fail2ban-update event and add  a fail2ban
reload.
or maybe as you state it would rather be better to simply use fail2ban-conf




(In reply to bunkobugsy from comment #0)
> Sorry for insisting on this, but for me:
> 
> 1. no entries show up under Blocked Hosts (even though I'm sure there are
> bans in effect)



# rpm -q smeserver-fail2ban
smeserver-fail2ban-0.1.18-7.el6.sme.noarch
# sfail2ban 
 ftp:   
 http-auth:     
 http-badbots:  
 http-fakegooglebot:    
 http-noscript: 188.213.49.210 89.35.39.60 66.249.64.227 66.249.64.236
80.200.210.36 85.218.36.239
 http-overflows:        
 http-scan:     188.213.49.210 89.35.39.60 5.128.131.224 87.98.175.135
 http-shellshock:       
 imap:  
 pam-generic:   
 qpsmtpd:       92.118.38.53 51.255.86.223
 recidive:      
 ssh:   104.244.79.146 116.110.117.42 45.9.148.35 104.168.253.82
183.166.128.171 67.205.183.187
 ssh-ddos:      
 wordpress:     


Blocked Hosts

This is a list of hosts that are currently blocked.
Adresse IP      JAIL    Action
188.213.49.210  http-noscript   Supprimer WHITELIST
89.35.39.60     http-noscript   Supprimer WHITELIST
66.249.64.227   http-noscript   Supprimer WHITELIST
66.249.64.236   http-noscript   Supprimer WHITELIST
80.200.210.36   http-noscript   Supprimer WHITELIST
85.218.36.239   http-noscript   Supprimer WHITELIST
188.213.49.210  http-scan       Supprimer WHITELIST
89.35.39.60     http-scan       Supprimer WHITELIST
5.128.131.224   http-scan       Supprimer WHITELIST
87.98.175.135   http-scan       Supprimer WHITELIST
92.118.38.53    qpsmtpd         Supprimer WHITELIST
51.255.86.223   qpsmtpd         Supprimer WHITELIST
104.244.79.146  ssh     Supprimer WHITELIST
116.110.117.42  ssh     Supprimer WHITELIST
45.9.148.35     ssh     Supprimer WHITELIST
104.168.253.82  ssh     Supprimer WHITELIST
183.166.128.171         ssh     Supprimer WHITELIST
67.205.183.187  ssh     Supprimer WHITELIST


WORKSFORME


# sfail2ban
 MediaWiki:     
 http-auth:     
 http-badbots:  
 http-fakegooglebot:    
 http-noscript: 
 http-overflows:        
 http-scan:     
 http-shellshock:       
 imap:  
 pam-generic:   
 qpsmtpd:       45.227.253.138
 recidive:      78.128.113.117 45.227.253.133 45.82.153.37 92.118.38.53
78.128.113.118
 ssh:   
 ssh-ddos:      
 sshd-denyhosts:        158.69.117.126 167.114.102.185 92.222.69.186


Blocked Hosts

This is a list of hosts that are currently blocked.
Adresse IP      JAIL    Action
45.227.253.138  qpsmtpd         Supprimer WHITELIST
78.128.113.117  recidive        Supprimer WHITELIST
45.227.253.133  recidive        Supprimer WHITELIST
45.82.153.37    recidive        Supprimer WHITELIST
92.118.38.53    recidive        Supprimer WHITELIST
78.128.113.118  recidive        Supprimer WHITELIST
158.69.117.126  sshd-denyhosts  Supprimer WHITELIST
167.114.102.185         sshd-denyhosts  Supprimer WHITELIST
92.222.69.186   sshd-denyhosts  Supprimer WHITELIST


WORKSFORME


# sfail2ban 
 http-auth:     
 http-badbots:  
 http-fakegooglebot:    
 http-noscript: 
 http-overflows:        
 http-scan:     
 http-shellshock:       
 imap:  
 nextcloud:     
 pam-generic:   
 qpsmtpd:       
 recidive:      193.32.160.142 193.32.160.136 193.32.160.135
 ssh:   
 ssh-ddos:      
 wordpress:     


Blocked Hosts

This is a list of hosts that are currently blocked.
Adresse IP      JAIL    Action
193.32.160.142  recidive        Supprimer WHITELIST
193.32.160.136  recidive        Supprimer WHITELIST
193.32.160.135  recidive        Supprimer WHITELIST


WORKSFORME

pasted there only 3 servers, but I tried numerous and all are working, the only
one without output had no bans neither in cli.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
_______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/

Reply via email to