Remote log stack traces without kdump in highly available environments
Issue
- I've had an outage in my highly available environment and suspect it may be due to a kernel panic, but for some reason kdump is not working. I can't take an outage to reboot the systems to get
kdumpor serial console logging working. Is there a way I can configure my systems to collect panic information from another incident without rebooting?
Environment
- Red Hat Enterprise Linux Server 5 (with the High Availability or Resilient Storage Add Ons)
- Red Hat Enterprise Linux Server 6 (with the High Availability or Resilient Storage Add Ons)
- Red Hat Cluster Suite
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
