最近發現跑keepalived的幾臺機器的日志總是打印不完，還好給拋了一個報錯，信息如下：
[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-limiting May 20 11:44:05 yw_lvs2_backup rsyslogd-2177: imuxsock lost 328 messages from pid 17131 due to rate-limiting May 20 12:11:41 yw_lvs2_backup rsyslogd-2177: imuxsock begins to drop messages from pid 20261 due to rate-limiting May 20 12:12:09 yw_lvs2_backup rsyslogd-2177: imuxsock lost 333 messages from pid 20261 due to rate-limiting May 23 17:31:38 yw_lvs2_backup rsyslogd-2177: imuxsock begins to drop messages from pid 20261 due to rate-limiting May 23 18:18:23 yw_lvs2_backup rsyslogd-2177: imuxsock lost 335 messages from pid 20261 due to rate-limiting May 24 18:02:59 yw_lvs2_backup rsyslogd-2177: imuxsock begins to drop messages from pid 20261 due to rate-limiting May 24 18:03:52 yw_lvs2_backup rsyslogd-2177: imuxsock lost 337 messages from pid 20261 due to rate-limiting May 24 18:03:52 yw_lvs2_backup rsyslogd-2177: imuxsock begins to drop messages from pid 20261 due to rate-limiting May 24 18:42:08 yw_lvs2_backup rsyslogd-2177: imuxsock lost 353 messages from pid 20261 due to rate-limiting
于是百度之，未果，谷歌一番終于明白這么回事了，解決方案如下：
echo ‘$SystemLogRateLimitInterval 60’ >> /etc/rsyslog.conf echo ‘$SystemLogRateLimitBurst 3000’ >> /etc/rsyslog.conf 重啟rsyslog /etc/init.d/rsyslog resart
免責聲明：本站發布的內容（圖片、視頻和文字）以原創、轉載和分享為主，文章觀點不代表本網站立場，如果涉及侵權請聯系站長郵箱：is@yisu.com進行舉報，并提供相關證據，一經查實，將立刻刪除涉嫌侵權內容。
