On Tue, 13 Jan 2015, Yaroslav Halchenko wrote:
[...]
ok then -- just monitor its operation with correct files loaded then
Just to touch base. This error has not reappeared since my previous
email so hopefully it won't. I did not apply the patch so I have no idea
what triggered it initially and
On Tue, 13 Jan 2015, Francois Gouget wrote:
On Tue, 13 Jan 2015, Yaroslav Halchenko wrote:
[...]
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 =
forcemerge 774689 775272
thanks
Known issue... didn't have time unfortunately even though workaround is
trivial - willing to try?
$ git diff
diff --git a/server/__init__.py b/server/__init__.py
index 2b76f4b..74f3b75 100644
--- a/server/__init__.py
+++ b/server/__init__.py
@@ -23,3 +23,7 @@
Package: fail2ban
Version: 0.8.13-1
Severity: normal
Dear Maintainer,
Enabling php-url-fopen causes fail2ban to fail on startup with the following
error:
2015-01-13 14:07:23,618 fail2ban.filter [4845]: ERROR Error in
FilterPyinotify callback:
'module' object has no attribute
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
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
On Tue, 13 Jan 2015, Yaroslav Halchenko wrote:
[...]
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
7 matches
Mail list logo
