1
votes

One of the actions for fail2ban is configured to run a ruby script; however, fail2ban fails when trying to execute the ruby script with a "Command not found" error. I don't understand this error because I'm providing the full path to the ruby script and it has execution permissions:

Here's my fail2ban action:

[root:a17924e746f0:~]# cat /etc/fail2ban/action.d/404.conf
# Fail2Ban action configuration file for Subzero/Core

[Definition]
actionstart =
actionstop =
actioncheck =
actionban = /root/ban_modify.rb ban <ip>
actionunban = /root/ban_modify.rb unban <ip>

Here are the contents to the /root/ban_modify.rb script:

#!/usr/bin/env ruby

command = ARGV[0]
ip_address = ARGV[1]

blacklist = File.open("/root/blacklist.txt").read.split("\n")

if command == "unban"
  if blacklist.include? "#{ip_address} deny"
    blacklist.delete "#{ip_address} deny"
  end
elsif command == "ban"
  blacklist << "#{ip_address} deny"
end

File.open("/root/blacklist.txt", "w") {|f| f.write(blacklist.join("\n"))}

Very simple. This blacklist.txt file is used by Apache to permanently ban individuals from the web server when a fail2ban condition is met.

However, when I issue the following command: sudo /usr/bin/fail2ban-client set 404 unbanip <my ip>

I get the following error:

2019-08-19 20:56:43,508 fail2ban.utils          [16176]: Level 39 7ff7395873f0 -- exec: ban_modify.rb ban <myip>
2019-08-19 20:56:43,509 fail2ban.utils          [16176]: ERROR   7ff7395873f0 -- stderr: '/bin/sh: 1: ban_modify.rb: not found'
2019-08-19 20:56:43,509 fail2ban.utils          [16176]: ERROR   7ff7395873f0 -- returned 127
2019-08-19 20:56:43,509 fail2ban.utils          [16176]: INFO    HINT on 127: "Command not found".  Make sure that all commands in 'ban_modify.rb ban <myip>' are in the PATH of fail2ban-server process (grep -a PATH= /proc/`pidof -x fail2ban-server`/environ). You may want to start "fail2ban-server -f" separately, initiate it with "fail2ban-client reload" in another shell session and observe if additional informative error messages appear in the terminals.
2019-08-19 20:56:43,509 fail2ban.actions        [16176]: ERROR   Failed to execute ban jail '404' action '404' info 'ActionInfo({'ip': '<myip>', 'family': 'inet4', 'ip-rev': '<myip>.', 'ip-host': '<myip>', 'fid': '<myip>', 'failures': 1, 'time': 1566266203.3465006, 'matches': '', 'restored': 0, 'F-*': {'matches': [], 'failures': 1}, 'ipmatches': '', 'ipjailmatches': '', 'ipfailures': 1, 'ipjailfailures': 1})': Error banning <myip>

I'm not sure why this error is happening if the actionban is pointing to the full path of a ruby script.

I even tried changing the contents of /root/ban_modify.rb to just simply puts "Hello World". Tried changing the banaction to iptables-allports and that still failed. It seems like banaction just simply doesn't work.

2
What suggested command (grep -a PATH= /proc/`pidof -x fail2ban-server`/environ) returns? - Aleksei Matiushkin

2 Answers

0
votes

You can enable fail2ban debug mode & check fail2ban log for more details.

# change fail2ban log level
sudo nano /etc/fail2ban/fail2ban.conf
loglevel = DEBUG 

# restart fail2ban
sudo systemctl restart fail2ban

# check logs
tail -f /var/log/fail2ban.log
-1
votes

You can restart the fail2ban and check it again:

sudo systemctl restart fail2ban