You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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'.
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.
The text was updated successfully, but these errors were encountered: