https://bugs.contribs.org/show_bug.cgi?id=10817
Bug ID: 10817
Summary: Fail2ban panel does not propagate configuration change
as needed.
Classification: Contribs
Product: SME Contribs
Version: 9.2
Hardware: ---
OS: ---
Status: CONFIRMED
Severity: normal
Priority: P3
Component: smeserver-fail2ban
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected],
[email protected],
[email protected], [email protected],
[email protected]
Depends on: 10814
Target Milestone: ---
+++ This bug was initially created as a clone of Bug #10814 +++
pressing Save doesn't apply the change (doesn't seem to execute signal-event
fail2ban-conf)
Thanks
(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...
(In reply to Jean-Philippe Pialasse from comment #6)
> (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|HTT
> PDbadbotsStatus|enabled|HTTPDoverflowsStatus|enabled|Mail|enabled|status|enab
> led
> 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|HTT
> PDbadbotsStatus|enabled|HTTPDoverflowsStatus|enabled|Mail|enabled|status|enab
> led|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|HTT
> PDbadbotsStatus|enabled|HTTPDoverflowsStatus|enabled|Mail|enabled|status|enab
> led|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|HTT
> PDbadbotsStatus|enabled|HTTPDoverflowsStatus|enabled|Mail|disabled|status|ena
> bled|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
as a resumé some config changes needs fail2ban reload, and some might need masq
reload.
currently only masq reoad is achieved using fail2ban-conf
hence some changes are done in the db, configuration files are modified, but
not acknowledges by the running service.
Referenced Bugs:
https://bugs.contribs.org/show_bug.cgi?id=10814
[Bug 10814] Fail2ban panel errors
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list 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/
