Bug 1422500
| Summary: | directory /var/run/fail2ban/ is missing at startup | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Aldo Necci <necci> |
| Component: | fail2ban | Assignee: | Orion Poplawski <orion> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel7 | CC: | akiran28, athmanem, jncneo, orion, poil, vonsch |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | fail2ban-0.9.6-3.el7 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-02-25 02:50:01 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
Aldo Necci
2017-02-15 12:38:26 UTC
This issue is only for Fail2ban version 0.9.6 on EPEL7 Unfortunately the systemd version in EL7.3 does not automatically detect and create new tmpfiles.d entries. Running 'systemd-tmpfiles --create' or rebooting will create the directory'. I'll look into running that in the post install scripts. fail2ban-0.9.6-3.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-79373a2a0e fail2ban-0.9.6-3.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-79373a2a0e fail2ban-0.9.6-3.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report. Hi, I have fail2ban-0.9.6-3.el7 and I have this problem. # rpm -qa fail2ban fail2ban-0.9.6-3.el7.noarch -- Subject: L'unité (unit) fail2ban.service a commencé à démarrer -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- L'unité (unit) fail2ban.service a commencé à démarrer. juin 22 11:42:57 xxxxxx fail2ban-client[26924]: ERROR There is no directory /var/run/fail2ban to contain the socket file /var/run/fail2ban/fail2ban.sock. juin 22 11:42:57 xxxxxx systemd[1]: fail2ban.service: control process exited, code=exited status=255 juin 22 11:42:57 xxxxxx systemd[1]: Failed to start Fail2Ban Service. -- Subject: L'unité (unit) fail2ban.service a échoué -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel Best regards, (In reply to poil from comment #6) > Hi, > > I have fail2ban-0.9.6-3.el7 and I have this problem. > > # rpm -qa fail2ban > fail2ban-0.9.6-3.el7.noarch > > -- Subject: L'unité (unit) fail2ban.service a commencé à démarrer > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- L'unité (unit) fail2ban.service a commencé à démarrer. > juin 22 11:42:57 xxxxxx fail2ban-client[26924]: ERROR There is no directory > /var/run/fail2ban to contain the socket file /var/run/fail2ban/fail2ban.sock. > juin 22 11:42:57 xxxxxx systemd[1]: fail2ban.service: control process > exited, code=exited status=255 > juin 22 11:42:57 xxxxxx systemd[1]: Failed to start Fail2Ban Service. > -- Subject: L'unité (unit) fail2ban.service a échoué > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > > > Best regards, Errata: Not the package, I have the problem on only this server, I'm looking why ... |