Date: Sat, 20 May 2017 13:39:07 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 219419] security/py-fail2ban Message-ID: <bug-219419-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219419 Bug ID: 219419 Summary: security/py-fail2ban Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: lukasz@wasikowski.net CC: theis@gmx.at CC: theis@gmx.at Flags: maintainer-feedback?(theis@gmx.at) py27-fail2ban-0.9.6 on FreeBSD 11.0. I'm getting in /var/log/fail2ban.log those messages: 2017-05-20 15:32:27,751 fail2ban.action [83091]: ERROR=20=20 /usr/local/etc/fail2ban/filter.d/ignorecommands/apache-fakegooglebot 66.249.69.193 -- returned 127 2017-05-20 15:32:27,758 fail2ban.action [83091]: INFO HINT on 12= 7: "Command not found". Make sure that all commands in '/usr/local/etc/fail2ban/filter.d/ignorecommands/apache-fakegooglebot 66.249.69.193' are in the PATH of fail2ban-server process (grep -a PATH=3D /proc/`pidof -x fail2ban-server`/environ). You may want to start "fail2ban-server -f" separately, initiate it with "fail2ban-client reload" = in another shell session and observe if additional informative error messages appear in the terminals. Seems that python detection via env in /etc/fail2ban/filter.d/ignorecommands/apache-fakegooglebot is not working right. Setting #!/usr/local/bin/python2.7 as shebang instead of # !/usr/bin/env fail2ban-python fixes this issue. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219419-13>