If fail2ban and munin are installed in default paths, the path to fail2ban-client utility is wrong in /usr/local/share/munin/plugins/fail2ban. It's set to /usr/bin/fail2ban-client and should be /usr/local/bin/fail2ban-client. Fix: Change the path in /usr/local/share/munin/plugins/fail2ban to /usr/local/bin/fail2ban-client Or add a section in plugin-conf.d/plugins.conf: [fail2ban*] user root env.client /usr/local/bin/fail2ban-client
Responsible Changed From-To: freebsd-ports-bugs->freebsd-python freebsd-python@ wants this port PRs (via the GNATS Auto Assign Tool)
State Changed From-To: open->feedback Awaiting maintainers feedback (via the GNATS Auto Assign Tool)
Maintainer of security/py-fail2ban, Please note that PR ports/179549 has just been submitted. If it contains a patch for an upgrade, an enhancement or a bug fix you agree on, reply to this email stating that you approve the patch and a committer will take care of it. The full text of the PR can be found at: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/179549 -- Edwin Groothuis via the GNATS Auto Assign Tool edwin@FreeBSD.org
Is this a bug of py-fail2ban or of munin? From the bug description it looks more like munin uses the wrong path.
Sorry, this is for port sysutils/munin-node. Fabian
Responsible Changed From-To: freebsd-python->freebsd-ports-bugs reclassify based on feedback from submitter.
Responsible Changed From-To: freebsd-ports-bugs->flo Over to maintainer.
Responsible Changed From-To: flo->zeising Take from flo, I'm the new munin maintainer.
State Changed From-To: feedback->open Feedback recieved. I'll try to get to this as soon as possible, together with some other munin related PRs and issues. Thank you for your patiene.