Bug 179549 - sysutils/munin-node: fail2ban plugin wrong path for fail2ban-client
Summary: sysutils/munin-node: fail2ban plugin wrong path for fail2ban-client
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Mathieu Arnold
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-14 10:40 UTC by Fabian Abplanalp
Modified: 2014-09-03 07:29 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fabian Abplanalp 2013-06-14 10:40:00 UTC
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
Comment 1 Edwin Groothuis freebsd_committer 2013-06-17 00:46:00 UTC
Responsible Changed
From-To: freebsd-ports-bugs->freebsd-python

freebsd-python@ wants this port PRs (via the GNATS Auto Assign Tool)
Comment 2 Edwin Groothuis freebsd_committer 2013-06-17 00:46:01 UTC
State Changed
From-To: open->feedback

Awaiting maintainers feedback (via the GNATS Auto Assign Tool)
Comment 3 Edwin Groothuis freebsd_committer 2013-06-17 00:46:01 UTC
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
Comment 4 theis 2013-06-17 06:47:24 UTC
Is this a bug of py-fail2ban or of munin?
 From the bug description it looks more like munin uses the wrong path.
Comment 5 fabian.abplanalp 2013-06-17 13:45:29 UTC
Sorry, this is for port sysutils/munin-node.

Fabian
Comment 6 Mark Linimon freebsd_committer freebsd_triage 2013-06-25 06:10:37 UTC
Responsible Changed
From-To: freebsd-python->freebsd-ports-bugs

reclassify based on feedback from submitter.
Comment 7 Mark Linimon freebsd_committer freebsd_triage 2013-07-20 23:21:29 UTC
Responsible Changed
From-To: freebsd-ports-bugs->flo

Over to maintainer.
Comment 8 Niclas Zeising freebsd_committer 2014-04-05 12:36:58 UTC
Responsible Changed
From-To: flo->zeising

Take from flo, I'm the new munin maintainer.
Comment 9 Niclas Zeising freebsd_committer 2014-04-05 12:40:04 UTC
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.