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:
I believe the getpid check is removed in 0.8.11-1. Reopen if this is not fixed.
Ah crap, just saw this is for el5
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
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).
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).
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.