Skip to main content
added 386 characters in body
Source Link
shivams
  • 163
  • 1
  • 2
  • 9

I am using rsyslog v5.8.11. I found this version number from what rsyslog logs on restart. I am trying to apply rate-limiting in rsyslog but it is of no use. I am still losing messages. In the configuration file I put these options to implement rate-limiting

$SystemLogRateLimitInterval 5
$SystemLogRateLimitBurst 10000

This is of no use as I am still losing messages at the same rate. I even tried to put

$SystemLogRateLimitInterval 0

This should have stopped the rate-limiting feature of rsyslog but instead nothing happened. I am still losing message. These logs are critical to me. Is there any way possible to stop losing messages in rsyslog.

UPDATE

On restart i also found this in rsyslog logs.

rsyslogd: invalid selector line (port), probably not doing what was intended

Is losing logs somehow related to this error.

There are the logs showing that i am losing logs due to rate-limiting.

rsyslogd-2177: imuxsock begins to drop messages from pid 25810 due to rate-limiting
rsyslogd-2177: imuxsock lost 103 messages from pid 25810 due to rate-limiting

Such type of logs are coming no matter what setting is applied by me. If logs are lost due to UDP will rsyslog log in this manner too?

I am using rsyslog v5.8.11. I found this version number from what rsyslog logs on restart. I am trying to apply rate-limiting in rsyslog but it is of no use. I am still losing messages. In the configuration file I put these options to implement rate-limiting

$SystemLogRateLimitInterval 5
$SystemLogRateLimitBurst 10000

This is of no use as I am still losing messages at the same rate. I even tried to put

$SystemLogRateLimitInterval 0

This should have stopped the rate-limiting feature of rsyslog but instead nothing happened. I am still losing message. These logs are critical to me. Is there any way possible to stop losing messages in rsyslog.

UPDATE

On restart i also found this in rsyslog logs.

rsyslogd: invalid selector line (port), probably not doing what was intended

Is losing logs somehow related to this error.

I am using rsyslog v5.8.11. I found this version number from what rsyslog logs on restart. I am trying to apply rate-limiting in rsyslog but it is of no use. I am still losing messages. In the configuration file I put these options to implement rate-limiting

$SystemLogRateLimitInterval 5
$SystemLogRateLimitBurst 10000

This is of no use as I am still losing messages at the same rate. I even tried to put

$SystemLogRateLimitInterval 0

This should have stopped the rate-limiting feature of rsyslog but instead nothing happened. I am still losing message. These logs are critical to me. Is there any way possible to stop losing messages in rsyslog.

UPDATE

On restart i also found this in rsyslog logs.

rsyslogd: invalid selector line (port), probably not doing what was intended

Is losing logs somehow related to this error.

There are the logs showing that i am losing logs due to rate-limiting.

rsyslogd-2177: imuxsock begins to drop messages from pid 25810 due to rate-limiting
rsyslogd-2177: imuxsock lost 103 messages from pid 25810 due to rate-limiting

Such type of logs are coming no matter what setting is applied by me. If logs are lost due to UDP will rsyslog log in this manner too?

added 199 characters in body
Source Link
shivams
  • 163
  • 1
  • 2
  • 9

I am using rsyslog v5.8.11. I found this version number from what rsyslog logs on restart. I am trying to apply rate-limiting in rsyslog but it is of no use. I am still losing messages. In the configuration file I put these options to implement rate-limiting

$SystemLogRateLimitInterval 5
$SystemLogRateLimitBurst 10000

This is of no use as I am still losing messages at the same rate. I even tried to put

$SystemLogRateLimitInterval 0

This should have stopped the rate-limiting feature of rsyslog but instead nothing happened. I am still losing message. These logs are critical to me. Is there any way possible to stop losing messages in rsyslog.

UPDATE

On restart i also found this in rsyslog logs.

rsyslogd: invalid selector line (port), probably not doing what was intended

Is losing logs somehow related to this error.

I am using rsyslog v5.8.11. I found this version number from what rsyslog logs on restart. I am trying to apply rate-limiting in rsyslog but it is of no use. I am still losing messages. In the configuration file I put these options to implement rate-limiting

$SystemLogRateLimitInterval 5
$SystemLogRateLimitBurst 10000

This is of no use as I am still losing messages at the same rate. I even tried to put

$SystemLogRateLimitInterval 0

This should have stopped the rate-limiting feature of rsyslog but instead nothing happened. I am still losing message. These logs are critical to me. Is there any way possible to stop losing messages in rsyslog.

I am using rsyslog v5.8.11. I found this version number from what rsyslog logs on restart. I am trying to apply rate-limiting in rsyslog but it is of no use. I am still losing messages. In the configuration file I put these options to implement rate-limiting

$SystemLogRateLimitInterval 5
$SystemLogRateLimitBurst 10000

This is of no use as I am still losing messages at the same rate. I even tried to put

$SystemLogRateLimitInterval 0

This should have stopped the rate-limiting feature of rsyslog but instead nothing happened. I am still losing message. These logs are critical to me. Is there any way possible to stop losing messages in rsyslog.

UPDATE

On restart i also found this in rsyslog logs.

rsyslogd: invalid selector line (port), probably not doing what was intended

Is losing logs somehow related to this error.

Rsyslog loosingis losing messages

I am using rsyslog v5.8.11. ThisI found this version number i found from what rsyslogrsyslog logs on restart. I am trying to apply rate-limiting in rsyslogrsyslog but it is of no use. I am still loosinglosing messages. In the configuration file iI put these options to implement rate-limiting

$SystemLogRateLimitInterval 5
$SystemLogRateLimitBurst 10000

This is of no use ias I am still loosinglosing messages at the same rate. I even tried to put

$SystemLogRateLimitInterval 0

This should have stopped the rate-limiting feature of rsyslogrsyslog but instead nothing happened. I am still loosinglosing message. These logs are critical to me. Is there any way possible to stop loosinglosing messages in rsyslogrsyslog.

Rsyslog loosing messages

I am using rsyslog v5.8.11. This version number i found from what rsyslog logs on restart. I am trying to apply rate-limiting in rsyslog but it is of no use. I am still loosing messages. In configuration file i put these options to implement rate-limiting

$SystemLogRateLimitInterval 5
$SystemLogRateLimitBurst 10000

This is of no use i am still loosing messages at the same rate. I even tried to put

$SystemLogRateLimitInterval 0

This should have stopped rate-limiting feature of rsyslog but instead nothing happened. I am still loosing message. These logs are critical to me. Is there any way possible to stop loosing messages in rsyslog.

Rsyslog is losing messages

I am using rsyslog v5.8.11. I found this version number from what rsyslog logs on restart. I am trying to apply rate-limiting in rsyslog but it is of no use. I am still losing messages. In the configuration file I put these options to implement rate-limiting

$SystemLogRateLimitInterval 5
$SystemLogRateLimitBurst 10000

This is of no use as I am still losing messages at the same rate. I even tried to put

$SystemLogRateLimitInterval 0

This should have stopped the rate-limiting feature of rsyslog but instead nothing happened. I am still losing message. These logs are critical to me. Is there any way possible to stop losing messages in rsyslog.

Source Link
shivams
  • 163
  • 1
  • 2
  • 9
Loading