fail2ban does not create /var/run/fail2ban

[Matt LaPlante]

Binary package hint: fail2ban

I just upgraded from gutsy to hardy, and noticed fail2ban stopped running. Kicking off the daemon manually produces the following:

root@localhost:~# fail2ban-server
2008-04-28 11:14:24,896 fail2ban.server : INFO Starting Fail2ban v0.8.2
2008-04-28 11:14:24,897 fail2ban.server : ERROR Unable to create PID file: [Errno 2] No such file or directory: '/var/run/fail2ban/fail2ban.pid'

Sure enough, if i mkdir /var/run/fail2ban it appears to start working again. Why, then, does the init script not create this directory itself?

[Launchpad Janitor (janitor)]

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

[David Portwood (dzportwood)]

This appears to still not be fixed, as of this writing.