Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add feature to change/maximize kernel event logging #5

Open
mwbringmann opened this issue Feb 27, 2020 · 3 comments
Open

Add feature to change/maximize kernel event logging #5

mwbringmann opened this issue Feb 27, 2020 · 3 comments
Assignees

Comments

@mwbringmann
Copy link

Some distros or configurations may limit the amount / severity of kernel event information that is
stored into kernel logs like /var/log/messages in order to better manage system disk resources.
This optimization for performance also limits the amount of information available for debugging
problems and/or crashes. It would probably be useful for debugging to have an option that will
maximize the amount of information written to the kernel logs.

  • Remove 'quiet' option from kernel boot command lines
  • Revise default '/etc/sysctl.conf' setting of 'kernel.printk' to include all KERN_ messages
@sourabhjains
Copy link
Contributor

sourabhjains commented Mar 3, 2020

Hello Michael,

We can add a plugin to handle all the checks related to kernel logging.

  • Sourabh Jain

@ananthmg
Copy link

ananthmg commented Mar 3, 2020

While I agree that more logging in debug would be useful, making it default during test may mask some issues due to subtle timing changes, and we will end up discovering them in the field. I think the plugin making kernel logs verbose and/or removing the quiet option needs to be an optional one, for use only during very early testing.

@mwbringmann
Copy link
Author

Even an option to handle this issue would be desirable.
Whether it always sets the limits to 'unlimited' (and removes 'quiet' when ever it is observed), or there are arguments to the option to set its behavior, the modification would be an improvement.

Additionally, you might have arguments to the option to change the maximum size of the log files saved by normal sosreport/sosconfig processing. I believe that both of those tools impose a default setting of 'tail of 25M bytes'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants