Resolve rsyslogd log loss

Recently, it was found that the logs of several machines running keepalived could not be printed. Fortunately, an error was thrown. The message is as follows:

[root@yw_lvs2_backup etc] # tail-n 1000000 / var/log/messages-20130526 | grep "rate-limiting" May 20 11:43:55 yw_lvs2_backup rsyslogd-2177: imuxsock begins to drop messages from pid 17131 due to rate-limitingMay 20 11:44:05 yw_lvs2_backup rsyslogd-2177: imuxsock lost 328 messages from pid 17131 due to rate-limitingMay 20 12:11:41 yw_lvs2_backup rsyslogd-2177: imuxsock begins to drop messages from pid 20261 due to rate-limitingMay 20 12:12:09 Yw_lvs2_backup rsyslogd-2177: imuxsock lost 333 messages from pid 20261 due to rate-limitingMay 23 17:31:38 yw_lvs2_backup rsyslogd-2177: imuxsock begins to drop messages from pid 20261 due to rate-limitingMay 23 18:18:23 yw_lvs2_backup rsyslogd-2177: imuxsock lost 335 messages from pid 20261 due to rate-limitingMay 24 18:02:59 yw_lvs2_backup rsyslogd-2177: imuxsock begins to drop messages from pid 20261 due to rate-limitingMay 24 18:03:52 yw_lvs2_backup rsyslogd-2177: imuxsock Lost 337 messages from pid 20261 due to rate-limitingMay 24 18:03:52 yw_lvs2_backup rsyslogd-2177: imuxsock begins to drop messages from pid 20261 due to rate-limitingMay 24 18:42:08 yw_lvs2_backup rsyslogd-2177: imuxsock lost 353 messages from pid 20261 due to rate-limiting

So Baidu failed, and Google finally understood it, and the solution was as follows:

Echo'$SystemLogRateLimitInterval 60'> > / etc/rsyslog.confecho'$SystemLogRateLimitBurst 3000'> > / etc/rsyslog.conf restart rsyslog/etc/init.d/rsyslog resart