I just found the problem.  
The /tmp/fail2ban.sock file had been sitting there since January 18 (through multiple reboots) and keeping fail2ban from starting up.

root@mythtv:/tmp# ls -l
total 316
-rw-r--r-- 1 root         root         0 Jul 17  2012 350
-rwxrwxr-x 1 mythtv       mythtv       6 Oct  8  2009 Miro_Download_Daemon_100.txt
drwx------ 2 root         root      4096 Jul 17  2012 _KnoppMyth-main.3973-27
-rw-r--r-- 1 mythtv       mythtv     336 Feb 22  2009 apps
-rw-r--r-- 1 mythtv       mythtv     145 Feb 22  2009 config
-rw-r--r-- 1 root         root       898 Jun 21  2009 crontab
-rw-r--r-- 1 root         root     67380 Feb 22  2009 end_of_initrd
srwx------ 1 root         root         0 Jan 18 13:36 fail2ban.sock

After I deleted the /tmp/fail2ban.sock file, fail2ban started up and populated the /var/log/fail2ban.log with info.

I was just able to update to fail2ban 0.8.3 and python-central 0.6.8
fail2ban started and ran after the updates
I believe fail2ban 0.8.3 is a version after the .sock file bug was fixed?


From: Eric <neutron68@yahoo.com>
To: "fail2ban-users@lists.sourceforge.net" <fail2ban-users@lists.sourceforge.net>
Sent: Friday, May 23, 2014 12:12 AM
Subject: need help geting an older fail2ban working

Back in January 2014, I had fail2ban working in my Knoppmyth R5.5 machine (Debian etch from 2008).
Then, I tried to update to slightly newer versions of fail2ban and python-central. 
Now, when I try and start or restart fail2ban, I get an error.

root@mythtv:/etc/fail2ban# /etc/init.d/fail2ban restart
Restarting authentication failure monitor: fail2ban failed!

Does anyone know what the error message is specifically indicating?
Is there anywhere else that would give a clue?
The /var/log/fail2ban.log file is empty.

Here are the versions of the components I had running at one time.
I just tried these same versions of the .deb files in a Knoppmyth R5.5 virtual machine, and they work in the virtual machine.

http://archive.debian.net/ etch/all/fail2ban  (version 0.7.5-2etch1)
http://archive.debian.net/ etch/python/python (version 2.4.4-2)
http://archive.debian.net/ etch/all/python-central (version 0.5.12)

For fail2ban, I used the command "dpkg -i fail2ban_0.7.5-2etch1_all.deb"

In my real-world machine, I started with these versions. 
For the newer version of fail2ban, I also needed to update the python-central version to version 0.6.17.
Now, fail2ban won't run.
I have been trying to use the dpkg command to "go back" and overwrite the newer with the older.  dpkg seems to complete the process of installing the older, but when you try and start fail2ban, it doesn't work.  (with the error you see)

There must be some way to get back to a working setup, but I'm not sure how.
Use dpkg to remove and then manually delete all the files from the newer versions?

Help appreciated.