Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
|Summary:||Fail2ban can't start on OpenVZ host system|
|Product:||[Fedora] Fedora EPEL||Reporter:||Jakub Jedelsky <jakub.jedelsky>|
|Component:||fail2ban||Assignee:||Adam Miller <maxamillion>|
|Status:||CLOSED ERRATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||fail2ban-0.8.13-2.el5||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2014-08-15 18:59:57 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Jakub Jedelsky 2011-01-18 10:10:28 UTC
Created attachment 474013 [details] Suport for OpenVZ host server; check pid of running instance via vzpid Description of problem: Fail2ban can't start on OpenVZ host server if any guest has a fail2ban instance started - because of PID check in init script. Prepared patch for init script is added as attachment. Version-Release number of selected component (if applicable): 0.8.4 How reproducible: Start fail2ban on openvz host with guest running fail2ban too. Actual results: Can't start becouse of pid Expected results: Can start Additional info:
Comment 1 Orion Poplawski 2014-03-18 00:12:47 UTC
I believe the getpid check is removed in 0.8.11-1. Reopen if this is not fixed.
Comment 2 Orion Poplawski 2014-03-18 00:14:17 UTC
Ah crap, just saw this is for el5
Comment 3 Fedora Update System 2014-07-21 23:13:18 UTC
fail2ban-0.8.13-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/fail2ban-0.8.13-1.el5
Comment 4 Fedora Update System 2014-07-22 18:10:03 UTC
Package fail2ban-0.8.13-1.el5: * should fix your issue, * was pushed to the Fedora EPEL 5 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing fail2ban-0.8.13-1.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1996/fail2ban-0.8.13-1.el5 then log in and leave karma (feedback).
Comment 5 Fedora Update System 2014-07-30 19:35:39 UTC
Package fail2ban-0.8.13-2.el5: * should fix your issue, * was pushed to the Fedora EPEL 5 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing fail2ban-0.8.13-2.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-1996/fail2ban-0.8.13-2.el5 then log in and leave karma (feedback).
Comment 6 Fedora Update System 2014-08-15 18:59:57 UTC
fail2ban-0.8.13-2.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.