With /etc/init.d/fail2ban start, you can always start fail2ban daemon,
but iptables are not modified. Thus, to add a fail2ban line in iptables,
you have to reload fail2ban...
hm -= interesting it is just that in one sh -x traces you gave
to me start command didn't come to actually
it seems that no need for root ;-) I think we know what is the reason
now... sorry for such a lengthy troubleshooting
I am 99% sure that the cause is insufficient delay in client waiting for
server to come up
could you please modify in /usr/bin/fail2ban-client
cnt 10
to
cnt 100
and start it
Hi Bertrand,
Tried to start stop fail2ban few times and it seems to start/stop. I am
not sure on the status of iptables after its start or log file since I
am not in adm group, but look:
,
|
Yaroslav Halchenko a écrit :
indeed strange... unfortunately it would be impossible for me to try it
myself - no sparc around
I can open a ssh access to one on mine ;-)
could you please boost verbosity in fail2ban.conf (or override it in
fail2ba.local) and then send me along
Yaroslav Halchenko a ц╘crit :
indeed strange... unfortunately it would be impossible for me to try it
myself - no sparc around
I can open a ssh access to one on mine ;-)
if you don't mind giving me root access (or at least sudo to
/etc/init.d/fail2ban) that would be great but we might
Package: fail2ban
Version: 0.7.4-3
Hello,
I see a strange 'feature' on a SparcSTATION 20 running debian/testing
(Linux hilbert 2.6.18.2 #4 SMP Wed Nov 15 17:09:47 CET 2006 sparc
GNU/Linux).
fail2ban cannot be launched by /etc/init.d/fail2ban start, but if I try
to launch fail2ban
indeed strange... unfortunately it would be impossible for me to try it
myself - no sparc around
could you please boost verbosity in fail2ban.conf (or override it in
fail2ba.local) and then send me along fail2ban.log (if it has anything
in) and output of
sh -x /etc/init.d/fail2ban start
Thank
7 matches
Mail list logo
