We have a hard-to-diagnose problem we are working with the TAC. We have to debug a problem that occurs only a couple of times a day, and which we cannot depend on external syslog to reliably deliver debug messages for, since it may involve switching drops on the control plane. We are trying to capture at the debug level of logging during the problem on the controller, however that level of logging easily wraps the 75Kish system log buffer by the time we can get in and show the logs, much less tar them up.
We are currently trying to guess which of the most noisy debug level processes we can turn off and then individually turn debug on for as many other processes as we can, each by hand, since it does not appear one can override a "debug" with a more specific "info" or "errors" setting. However, this will probably not be sufficient to prevent a log wrap on the services we are interested in.
So two specific questions:
1) Is there any way to allocate larger (potentially very large) logging buffers on the controller? Would that involve a reboot?
2) Could someone explain how to use "logging level X ap-debug" since we cannot seem to find documentation for the required "name"
parameter (online help says "Debug String Range 1-63")?
Other than that, does anyone have any other tips or tricks that might be useful in this situation?