On Tue, 13 Jan 2015, Francois Gouget wrote: > On Tue, 13 Jan 2015, Yaroslav Halchenko wrote: > [...] > > Known issue... didn't have time unfortunately even though workaround is > > trivial - willing to try?
> This issue was systematic this morning and now it's gone and I have no > idea why. (I see the fail2ban-php-url-fopen iptables chain so it's > enabled). race conditions are always fun! > However that prevents me from testing the patch :-( > (all I can say is it does not seem to hurt) it shouldn't indeed ;-) just observe your box for few days with this patch in place and restarting fail2ban few times... if you could restart fail2ban tomorrow morning approx at the same time (may be there is morning load high etc) -- that would be great > What I did have to change though is the logpath. My understanding is > that it should parse the Apache access log so I did: > -logpath = /var/www/*/logs/access_log > +logpath = /var/log/apache*/*access.log well -- that could have lead also to less files being attempted to load, etc, thus hiding this bug away again ;) -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
