I was running fail2ban 0.8.11 which is the version installed on Ubuntu 14.04 with apt-get. I downloaded and installed the latest source, 0.93.
When I start it up, I get two error messages.
WARNING Wrong value for 'loglevel' in 'Definition'. Using default one: '1'
WARNING 'logpath' not defined in 'INCLUDES'. Using default one: '/var/log/messages'
I've seen some conversation regarding the loglevel message. It was changed from int
to string
in one of the more recent updates. As far as I've been able to ascertain, it's not a real problem.
I don't know whether the logpath
error is signficant or not. I have this set in fail2ban.conf
logpath = /var/log/fail2ban.log
Fail2ban is not banning any ip address, and it's not writing anything to the logs - neither /var/log/fail2ban.log
nor /var/log/messages
. That includes not writing any messages when it starts or stops. The service is running, though, and I receive warning emails when it is started or stopped.
I've also noticed that I get a broken pipe error when I use the interactive client:
fail2ban> status
Status
|- Number of jail: 2
`- Jail list: recidive, ssh
ERROR [Errno 32] Broken pipe
fail2ban>
I have a feeling this might be something straightforward, but I'm not sure what. The installation is pretty much default. I hadn't maed any significant changes before installing the new version.