[SRU] fail2ban fails to start after reboot
Bug #222804 reported by
Troy Jendra
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fail2ban (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Hardy |
Fix Released
|
High
|
Chris Coulson |
Bug Description
Binary package hint: fail2ban
Due to /var/run being mounted as tmpfs, after a reboot, the /var/run/fail2ban is no longer present.
This stops fail2ban from starting.
Adding something like "[ -d /var/run/fail2ban ] || mkdir /var/run/fail2ban" in the start section of /etc/init.
Related branches
Changed in fail2ban: | |
status: | Fix Released → Confirmed |
Changed in fail2ban: | |
status: | Confirmed → Fix Released |
status: | New → In Progress |
Changed in fail2ban: | |
status: | Fix Released → Confirmed |
Changed in fail2ban: | |
status: | Confirmed → Fix Released |
Changed in fail2ban: | |
importance: | Undecided → High |
milestone: | none → ubuntu-8.04.2 |
Changed in fail2ban: | |
assignee: | nobody → chrisccoulson |
status: | Confirmed → In Progress |
To post a comment you must log in.
This bug was fixed in the package fail2ban - 0.8.2-3
---------------
fail2ban (0.8.2-3) unstable; urgency=low
* Changes propagated from upstream trunk (future 0.8.3):
- Fixed "fail2ban-client get <jail> logpath". Bug #1916986.
- Changed some log level.
- Added "Day/Month/Year Hour:Minute:Second" date template. Thanks to
Dennis Winter.
- Fixed PID file while started in daemon mode. Thanks to Christian
Jobic who submitted a similar patch (closes: #479703)
- Added gssftpd filter. Thanks to Kevin Zembower.
- Process failtickets as long as failmanager is not empty.
* Assure that /var/run/fail2ban exists upon start (LP: #222804, #223706)
-- Ubuntu Archive Auto-Sync <email address hidden> Wed, 07 May 2008 06:55:47 +0100