Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

Linux uses this mechanism to throttle the spamming of log events, decreasing the likelihood of a denial-of-service attack.

You can find tune this feature by amending two settings net.core.message_burst and net.core.message_cost .

These parameters are used to limit the warning messages written to the kernel log from the networking code. They enforce a rate limit to make a denial-of-service attack impossible. A higher message_cost factor, results in fewer messages that will be written. Message_burst controls when messages will be dropped. The default settings limit warning messages to one every five seconds.

To check their current values use:

sudo sysctl -a | grep net.core.message_

To amend them:

sysctl -w net.core.message_cost=0

Please note that disabling this mechanism is not recommend in production environments.

More information: https://www.kernel.org/doc/Documentation/sysctl/net.txt

Are you sure the kaudit messages are from the networking code (and use net.core.message_cost ) and not general kernel.printk_ratelimit_burst ? Marki555 Oct 28, 2020 at 15:53 @Marki555 is correct, I reduced spammy log messages by increasing kernel.printk_ratelimit and kernel.printk_ratelimit_burst to higher values. Changing net.core.message_cost didn't solve the issue. mVChr Jun 16, 2021 at 22:36

Thanks for contributing an answer to Stack Overflow!

  • Please be sure to answer the question . Provide details and share your research!

But avoid

  • Asking for help, clarification, or responding to other answers.
  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers .