Bug 892365

Summary:	fail2ban-client won't start after latest upgrade
Product:	[Fedora] Fedora	Reporter:	William H. Haller <bill>
Component:	fail2ban	Assignee:	Axel Thimm <axel.thimm>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	17	CC:	axel.thimm, jonathan.underwood, jv+fedora, orion
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	fail2ban-0.8.8-3.fc17	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-03-14 23:59:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description William H. Haller 2013-01-06 21:38:28 UTC

Description of problem: Latest release fails to start


Version-Release number of selected component (if applicable):fail2ban-0.8.8-1.fc17.noarch


How reproducible:always


Steps to Reproduce:
1.fail2ban-client start
2.
3.
  
Actual results:Fails to start. Cannot load module common.version


Expected results:fail2ban starts


Additional info:At some point a test was added to only add the module path if fail2ban appears to be running from /usr. Now that /bin and /usr/bin are joined, the executable appears to be running in /bin rather than /usr/bin so fails to insert the /usr/share/fail2ban directory as a place to look for modules. Commenting out the test in fail2ban-server and fail2ban-client and adjusting the spacing fixes the problem.

Comment 1 Fedora Update System 2013-02-14 22:23:59 UTC

fail2ban-0.8.8-3.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/fail2ban-0.8.8-3.fc18

Comment 2 Fedora Update System 2013-02-14 22:24:19 UTC

fail2ban-0.8.8-3.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/fail2ban-0.8.8-3.fc17

Comment 3 Fedora Update System 2013-02-16 00:56:58 UTC

Package fail2ban-0.8.8-3.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing fail2ban-0.8.8-3.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-2525/fail2ban-0.8.8-3.fc18
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2013-03-14 23:59:12 UTC

fail2ban-0.8.8-3.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 5 Orion Poplawski 2013-03-16 14:56:37 UTC

*** Bug 916158 has been marked as a duplicate of this bug. ***

Comment 6 Fedora Update System 2013-06-03 03:07:38 UTC

fail2ban-0.8.8-3.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.