1 Topic by vinacc (edited by vinacc 2017-01-25 02:42:20)

  • vinacc
  • Member
  • Offline
  • Registered: 2016-05-04
  • Posts: 37

Topic: [Update 0.9.6] fail2ban crash server

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

After upgrading the server, if I try to send an email from Outlook least it happened always in the process of sending mail server crashes. Apache does not respond even, I have to restart the machine as you can?

----

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

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,770

Re: [Update 0.9.6] fail2ban crash server

Any related error in server log files?
Try to temporarily disable fail2ban service, and try again.

3 Reply by vinacc

  • vinacc
  • Member
  • Offline
  • Registered: 2016-05-04
  • Posts: 37

Re: [Update 0.9.6] fail2ban crash server

Hello,

It seems to be no error between the logs. The fail2ban log appears to be empty. Indeed fail2ban disabling the server sends and receives emails properly and does not seem to go down.

What is the problem in your opinion? How do I re-enable fail2ban order not to crash it all?

4 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,770

Re: [Update 0.9.6] fail2ban crash server

Check /etc/fail2ban/jail.local. It scans log files and extract failures, then call iptables to block the bad clients.

5 Reply by vinacc

  • vinacc
  • Member
  • Offline
  • Registered: 2016-05-04
  • Posts: 37

Re: [Update 0.9.6] fail2ban crash server

These errors may be found in the log:

/var/log/dovecot.log

Jan 24 17:59:44 master: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Jan 24 17:59:44 lmtp(3386): Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Jan 24 17:59:44 anvil: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Jan 24 17:59:44 log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Jan 24 17:59:44 config: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Jan 24 17:59:44 imap-login: Error: read(anvil) failed: EOF
Jan 24 17:59:44 imap-login: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Jan 24 17:59:44 imap-login: Error: read(anvil) failed: EOF
Jan 24 17:59:44 imap-login: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Jan 24 17:59:44 imap-login: Error: read(anvil) failed: EOF
Jan 24 17:59:44 imap-login: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Jan 24 17:59:44 imap-login: Error: read(anvil) failed: EOF
Jan 24 17:59:44 imap-login: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Jan 24 17:59:44 imap(vinacc@mydomain.com): Info: Disconnected: Disconnected in IDLE in=1274 out=6651
Jan 24 17:59:44 imap(vinacc@mydomain.com): Info: Connection closed in=21 out=414
Jan 24 17:59:44 dict: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Jan 24 17:59:44 lmtp(3390): Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Jan 24 17:59:44 lmtp(3391): Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Jan 24 17:59:44 lmtp(3392): Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Jan 24 17:59:44 lmtp(3393): Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Jan 24 18:00:11 master: Info: Dovecot v2.2.13 starting up for pop3, imap, sieve, lmtp (core dumps disabled)

Until yesterday has always functioned properly. Today with the update we've changed just the dovecoat rule of fail2ban. It could be the problem?