1 Topic by alexandercolhost

  • alexandercolhost
  • Member
  • Offline
  • Registered: 2020-07-02
  • Posts: 38

Topic: Issue with rate limiting in the logs

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.4.0 MARIADB edition.
- Deployed with iRedMail Easy or the downloadable installer? downloadable installer
- Linux/BSD distribution name and version: CentOS Linux release 8.3.2011
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? iRedAdmin-Pro    4.8 (MySQL)
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Hello,

Can you please help us to validate how we can change the options to save all the log in the server? we see the next info in the syslog status:

service syslog status
Jun 11 08:29:01 mail3.correopremium.com rsyslogd[470843]: imjournal: journal files changed, reloading...  [v8.1911.0-6.el8 try https://www.rsyslog.com/e/0 ]
Jun 11 08:29:01 mail3.correopremium.com rsyslogd[470843]: imjournal: journal files changed, reloading...  [v8.1911.0-6.el8 try https://www.rsyslog.com/e/0 ]
Jun 11 08:32:30 mail3.correopremium.com rsyslogd[470843]: imjournal from <mail3:dovecot>: begin to drop messages due to rate-limiting
Jun 11 08:37:43 mail3.correopremium.com rsyslogd[470843]: imjournal: 20998 messages lost due to rate-limiting (20000 allowed within 600 seconds)
Jun 11 08:42:33 mail3.correopremium.com rsyslogd[470843]: imjournal from <mail3:dovecot>: begin to drop messages due to rate-limiting

Many thanks

----

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,768

Re: Issue with rate limiting in the logs

- Is this a very busy mail server? 20000 log lines in 600 seconds?
- You can disable rate limit in /etc/rsyslog.conf:

# Disable rate limit.
$imjournalRatelimitInterval 0
$imjournalRatelimitBurst 0

3 Reply by alexandercolhost

  • alexandercolhost
  • Member
  • Offline
  • Registered: 2020-07-02
  • Posts: 38

Re: Issue with rate limiting in the logs

ZhangHuangbin wrote:

- Is this a very busy mail server? 20000 log lines in 600 seconds?
- You can disable rate limit in /etc/rsyslog.conf:

# Disable rate limit.
$imjournalRatelimitInterval 0
$imjournalRatelimitBurst 0

Thanks, but we dont see that variables in the file /etc/rsyslog.conf

we see the next lines:
#### MODULES ####

module(load="imuxsock"    # provides support for local system logging (e.g. via logger command)
       SysSock.Use="off") # Turn off message reception via local log socket;
                          # local messages are retrieved through imjournal now.
module(load="imjournal"             # provides access to the systemd journal
       StateFile="imjournal.state") # File to store the position in the journal
#module(load="imklog") # reads kernel messages (the same are read from journald)
#module(load="immark") # provides --MARK-- message capability

Thanks for any help

4 Reply by ZhangHuangbin

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

Re: Issue with rate limiting in the logs

Append to rsyslog.conf please.

5 Reply by alexandercolhost

  • alexandercolhost
  • Member
  • Offline
  • Registered: 2020-07-02
  • Posts: 38

Re: Issue with rate limiting in the logs

ZhangHuangbin wrote:

Append to rsyslog.conf please.

thanks

it worked well