1 Topic by virakocha (edited by virakocha 2017-01-03 22:51:50)

  • virakocha
  • Member
  • Offline
  • Registered: 2016-03-15
  • Posts: 13

Topic: After SOGO installation fail2ban ERROR (Solved)

======== Required information ====
- iRedMail version (check /etc/iredmail-release): v0.9.5-1
- Linux/BSD distribution name and version: Debian 8 (jessie)
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): v0.6.3 (MySQL)
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? NO
- Related log if you're reporting an issue:
====

Dear all,

At the beginning I installed iRedmail without SOGO and than I followed the steps from here -> http://www.iredmail.org/forum/topic1044 … stall.html
and added export USE_SOGO='YES' to config file and executed bash iRedMail.sh

It has returned with an error. Can't remember what it was but exactly but it was something regarding sogo users I believe.

So now I saw that on my email I got this

/etc/cron.daily/spamassassin:
Job for spamassassin.service failed. See 'systemctl status spamassassin.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript spamassassin, action "reload" failed.

Than I also checked fail2ban status and the following ERRORS were displayed 

root@mail:/home/ziga# service fail2ban status
● fail2ban.service - LSB: Start/stop fail2ban
   Loaded: loaded (/etc/init.d/fail2ban)
   Active: active (running) since Tue 2016-12-27 16:37:46 CET; 5s ago
  Process: 2654 ExecStop=/etc/init.d/fail2ban stop (code=exited, status=0/SUCCESS)
  Process: 2703 ExecStart=/etc/init.d/fail2ban start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/fail2ban.service
           └─2714 /usr/bin/python /usr/bin/fail2ban-server -b -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid

Dec 27 16:37:46 my.domain.com fail2ban.jail[2714]: INFO Jail 'owncloud' started
Dec 27 16:37:46 my.domain.com fail2ban[2703]: Starting authentication failure monitor: fail2ban.
Dec 27 16:37:46 my.domain.com systemd[1]: Started LSB: Start/stop fail2ban.
Dec 27 16:37:46 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-apache
                                                               iptables -A fail2ban-apache -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports http,https -j fail2ban-apache...
Dec 27 16:37:46 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-apache-noscript
                                                               iptables -A fail2ban-apache-noscript -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports http,https -j fail2ban-apache-noscript...
Dec 27 16:37:46 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-apache-overflows
                                                               iptables -A fail2ban-apache-overflows -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports http,https -j fail2ban-apache-overflows...
Dec 27 16:37:46 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-sshd
                                                               iptables -A fail2ban-sshd -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports 22 -j fail2ban-sshd...
Dec 27 16:37:46 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-sshd-ddos
                                                               iptables -A fail2ban-sshd-ddos -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports 22 -j fail2ban-sshd-ddos...
Dec 27 16:37:46 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-roundcube
                                                               iptables -A fail2ban-roundcube -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports http,https,smtp,submission,pop3,pop3s,imap,imaps,sieve -j fail2ban-roundcube...
Dec 27 16:37:47 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-dovecot
                                                               iptables -A fail2ban-dovecot -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports http,https,smtp,submission,pop3,pop3s,imap,imaps,sieve -j fail2ban-dovecot...
Dec 27 16:37:47 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-postfix
                                                               iptables -A fail2ban-postfix -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports http,https,smtp,submission,pop3,pop3s,imap,imaps,sieve -j fail2ban-postfix...
Hint: Some lines were ellipsized, use -l to show in full.

Does anyone know what could be the problem. Before I try to reinstall the fail2ban service.

Thanks in advance
Z

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by devedames

  • devedames
  • devedames
  • Member
  • Offline
  • Registered: 2015-04-08
  • Posts: 42

Re: After SOGO installation fail2ban ERROR (Solved)

virakocha wrote:

======== Required information ====
- iRedMail version (check /etc/iredmail-release): v0.9.5-1
- Linux/BSD distribution name and version: Debian 8 (jessie)
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): v0.6.3 (MySQL)
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? NO
- Related log if you're reporting an issue:
====

Dear all,

At the beginning I installed iRedmail without SOGO and than I followed the steps from here -> http://www.iredmail.org/forum/topic1044 … stall.html
and added export USE_SOGO='YES' to config file and executed bash iRedMail.sh

It has returned with an error. Can't remember what it was but exactly but it was something regarding sogo users I believe.

So now I saw that on my email I got this

/etc/cron.daily/spamassassin:
Job for spamassassin.service failed. See 'systemctl status spamassassin.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript spamassassin, action "reload" failed.

Than I also checked fail2ban status and the following ERRORS were displayed 

root@mail:/home/ziga# service fail2ban status
● fail2ban.service - LSB: Start/stop fail2ban
   Loaded: loaded (/etc/init.d/fail2ban)
   Active: active (running) since Tue 2016-12-27 16:37:46 CET; 5s ago
  Process: 2654 ExecStop=/etc/init.d/fail2ban stop (code=exited, status=0/SUCCESS)
  Process: 2703 ExecStart=/etc/init.d/fail2ban start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/fail2ban.service
           └─2714 /usr/bin/python /usr/bin/fail2ban-server -b -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid

Dec 27 16:37:46 my.domain.com fail2ban.jail[2714]: INFO Jail 'owncloud' started
Dec 27 16:37:46 my.domain.com fail2ban[2703]: Starting authentication failure monitor: fail2ban.
Dec 27 16:37:46 my.domain.com systemd[1]: Started LSB: Start/stop fail2ban.
Dec 27 16:37:46 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-apache
                                                               iptables -A fail2ban-apache -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports http,https -j fail2ban-apache...
Dec 27 16:37:46 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-apache-noscript
                                                               iptables -A fail2ban-apache-noscript -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports http,https -j fail2ban-apache-noscript...
Dec 27 16:37:46 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-apache-overflows
                                                               iptables -A fail2ban-apache-overflows -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports http,https -j fail2ban-apache-overflows...
Dec 27 16:37:46 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-sshd
                                                               iptables -A fail2ban-sshd -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports 22 -j fail2ban-sshd...
Dec 27 16:37:46 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-sshd-ddos
                                                               iptables -A fail2ban-sshd-ddos -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports 22 -j fail2ban-sshd-ddos...
Dec 27 16:37:46 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-roundcube
                                                               iptables -A fail2ban-roundcube -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports http,https,smtp,submission,pop3,pop3s,imap,imaps,sieve -j fail2ban-roundcube...
Dec 27 16:37:47 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-dovecot
                                                               iptables -A fail2ban-dovecot -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports http,https,smtp,submission,pop3,pop3s,imap,imaps,sieve -j fail2ban-dovecot...
Dec 27 16:37:47 my.domain.com fail2ban.actions.action[2714]: ERROR iptables -N fail2ban-postfix
                                                               iptables -A fail2ban-postfix -j RETURN
                                                               iptables -I INPUT -p tcp -m multiport --dports http,https,smtp,submission,pop3,pop3s,imap,imaps,sieve -j fail2ban-postfix...
Hint: Some lines were ellipsized, use -l to show in full.

Does anyone know what could be the problem. Before I try to reinstall the fail2ban service.

Thanks in advance
Z



Restart both fail2ban and iptables.

Give it a try.

3 Reply by virakocha

  • virakocha
  • Member
  • Offline
  • Registered: 2016-03-15
  • Posts: 13

Re: After SOGO installation fail2ban ERROR (Solved)

I have tried that even restarting the server. Same problem sad. I did notice that after a time the msg that I posted before are changed with the following

root@mail:/var/lib/amavis/db# service fail2ban status
● fail2ban.service - LSB: Start/stop fail2ban
   Loaded: loaded (/etc/init.d/fail2ban)
   Active: active (running) since Tue 2016-12-27 16:56:54 CET; 16h ago
  Process: 4257 ExecStop=/etc/init.d/fail2ban stop (code=exited, status=0/SUCCESS)
  Process: 4305 ExecStart=/etc/init.d/fail2ban start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/fail2ban.service
           └─4317 /usr/bin/python /usr/bin/fail2ban-server -b -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid

Dec 28 01:06:29 mail.aero145.si fail2ban.actions.action[4317]: ERROR 86400 returned 7f00
Dec 28 01:06:29 mail.aero145.si fail2ban.actions.action[4317]: INFO HINT on 7f00: "Command not found".  Make sure that all commands in '86400' 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 addi...
Dec 28 01:12:33 mail.aero145.si fail2ban.actions.action[4317]: ERROR 86400 returned 7f00
Dec 28 01:12:33 mail.aero145.si fail2ban.actions.action[4317]: INFO HINT on 7f00: "Command not found".  Make sure that all commands in '86400' 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 addi...
Dec 28 04:24:07 mail.aero145.si fail2ban.actions.action[4317]: ERROR 86400 returned 7f00
Dec 28 04:24:07 mail.aero145.si fail2ban.actions.action[4317]: INFO HINT on 7f00: "Command not found".  Make sure that all commands in '86400' 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 addi...
Dec 28 08:03:33 mail.aero145.si fail2ban.actions.action[4317]: ERROR 86400 returned 7f00
Dec 28 08:03:33 mail.aero145.si fail2ban.actions.action[4317]: INFO HINT on 7f00: "Command not found".  Make sure that all commands in '86400' 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 addi...
Dec 28 08:42:53 mail.aero145.si fail2ban.actions.action[4317]: ERROR 86400 returned 7f00
Dec 28 08:42:53 mail.aero145.si fail2ban.actions.action[4317]: INFO HINT on 7f00: "Command not found".  Make sure that all commands in '86400' 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 addi...
Hint: Some lines were ellipsized, use -l to show in full.

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,241

Re: After SOGO installation fail2ban ERROR (Solved)

Seems your /etc/fail2ban/jail.local was improperly configured. Please double check.

5 Reply by virakocha

  • virakocha
  • Member
  • Offline
  • Registered: 2016-03-15
  • Posts: 13

Re: After SOGO installation fail2ban ERROR (Solved)

Problem fixed after fail2ban reinstalled. smile