- 1 Troubleshooting
- 1.1 I get emails containing "Here are/is more information about <ip>" and then nothing
- 1.2 I have Postfix on my system but no "mail" command. How can I get e-mail notifications?
- 1.3 Why do my CVS users using SSH getting blocked?
- 1.4 I get the error "Please check the format and your locale settings"
- 1.5 How do I increase verbosity?
- 1.6 Fail2ban-client is unable to contact server
- 1.7 Fail2ban is running but not banning SSH bruteforce
- 1.8 Fail2ban is failing to ban VSFTPD bruteforce
I get emails containing "Here are/is more information about <ip>" and then nothing
You are using a mail-whois*/sendmail-whois* action and you don't have the whois executable installed.
I have Postfix on my system but no "mail" command. How can I get e-mail notifications?
As of version 0.8.1, "mail" actions are deprecated. Please use the "sendmail" ones instead. E.g. sendmail-whois instead of mail-whois in your jail.[conf|local].
You probably have the sendmail command. Copy /etc/fail2ban/action.d/mail-whois.conf to /etc/fail2ban/action.d/mail-whois.local, edit this file and replace mail with sendmail. Here is an example:
actionban = echo -en "From:root <fail2ban> To: <dest> Subject: [Fail2Ban] <name>: banned <ip> Hi,\n The IP <ip> has just been banned by Fail2Ban after <failures> attempts against <name>.\n\n Here are more information about <ip>:\n `whois <ip>`\n Regards,\n Fail2Ban"|sendmail -t
mail.conf can be modified too.
Why do my CVS users using SSH getting blocked?
If you are using the Eclipse CVS integration with SSH, then each access of the CVS results in a failed access before a valid one is done. As a consequence your CVS users get banned from time to time.
I get the error "Please check the format and your locale settings"
The error looks like this:
ERROR: time data did not match format: data=Mar 21 10:00:50 fmt=%b %d %H:%M:%S ERROR: Please check the format and your locale settings.
This is a known bug. Since 0.6.1, Fail2ban uses your locale settings for date and time format. However, some daemons do not take care of locale and write their log messages using the POSIX standard. Please look at this bug for more details.
You can try to override the LANG variable:
# LANG=en_US /etc/init.d/fail2ban restart
You can get all the available locale with:
# locale -a
How do I increase verbosity?
In order to increase the verbosity of Fail2ban, use the command line option -vvv for fail2ban-client and fail2ban (only for 0.6.x). Set loglevel to 4 in /etc/fail2ban/fail2ban.conf (only for > 0.6.x).
Fail2ban-client is unable to contact server
Did you make sure to run fail2ban-client status using sudo?
$ fail2ban-client status ERROR Unable to contact server. Is it running? $ sudo fail2ban-client status Status |- Number of jail: 1 `- Jail list: ssh
Fail2ban is running but not banning SSH bruteforce
NB:This example is based on a Debian system, but can be easily done on any distro.
The package is well installed:
# dpkg -l |grep fail ii fail2ban 0.8.1-2 bans IPs that cause multiple authentication
The service is running:
# /etc/init.d/fail2ban status Status of authentication failure monitor: fail2ban is running
SSH jail is set up and ready:
# sudo fail2ban-client status Status |- Number of jail: 1 `- Jail list: ssh
SSH bruteforce logs are identified by fail2ban:
# fail2ban-regex /var/log/auth.log /etc/fail2ban/filter.d/sshd.conf .... Success, the total number of match is 30
So, check that all your logs are synchronized: all logs files (auth.log, syslog,..) must use the same time reference (if your server is not very busy, there will probably be an important difference between the output of date command and the last event logged in syslog. You can force to generate a log in syslog using the logger command and check then with the output of date command)
# date Wed Nov 28 13:49:02 CET 2007 # tail -2 /var/log/auth.log Nov 28 13:39:12 <SERVERNAME> sudo: pam_unix(sudo:session): session opened for user roo t by <user>(uid=0) Nov 28 13:39:12 <SERVERNAME> sudo: pam_unix(sudo:session): session closed for user roo t
If time reference is not the same everywhere, then fail2ban won't ban any IP!
If you change your timezone remember to restart syslogd so fail2ban will see the correct time in the log files.
Check if backend = auto. And set backend = polling. In some cases fail2ban won't be notified by gamin, but will chose to use it when auto is set.
Fail2ban is failing to ban VSFTPD bruteforce
Scenario: VSFTP configuration is set for PAM authentication, using xferlog in standard format. Fail2ban for vsftpd is watching /var/log/secure
- Problem: PAM sends failed login information to /var/log/secure, but the remote server's IP address has been replaced by a DNS name. Resulting DNS name does not resolve or does not resolve correctly, thus fail2ban is unable to ban the IP address.
- Fix: Configure VSFTP for "dual_log_enable=YES", and have fail2ban watch /var/log/vsftpd.log instead. This log file shows the incoming ip address instead of the DNS name.
Scenario: Timestamps in /var/log/vsftpd.log are in GMT instead of the local time zone.
- Problem: Fail2ban won't ban if the timestamps it finds don't match its idea of the current time.
- Fix: Add "use_localtime=YES" to /etc/vsftpd/vsftpd.conf and restart the vsftpd service.
NB: This will also cause file timestamps in directory listings and other timestamps displayed to clients to be in your local time zone. If this is unacceptable, then you may wish to configure fail2ban to monitory /var/log/secure, whose timestamps are in the local time zone, but this may cause other problems as described above.