Usage of hb_report for SLES HAE
This document (7007262) is provided subject to the disclaimer at the end of this document.
SUSE Linux Enterprise Server 15
To setup ssh keys (I use rsa in this example) for this, the command to run as user root is:
ssh-keygen -t rsa
which will create the following two keys in the /root/.ssh/ directory:
scp /root/.ssh/id_rsa.pub root@MY_OTHER_SERVER:/tmp/
and on this other server added to the authorized keys:
cat /tmp/id_rsa.pub >> /root/.ssh/authorized_keys
After this it is possible for root to ssh without password from one server to the other. This should be done for each and every member server of the cluster.
Now hb_report can be used and you may run the hb_report command on the cluster node of your choice, running it only on one node is sufficient, because hb_report will collect all the logs and cluster configurations from all the cluster members.
Assuming there was an incident to investigate on 25.11.2020 09:45, the interesting data would be from this time and from some time above and before. To ensure to capture all information that might have lead to this incident.
So the timeframe in question is from 25.11.2020 08:45 to 25.11.2020 10:45.
And that is the parameters for hb_report:
hb_report -u root -f "2020/11/25 08:45" -t "2020/11/25 10:45" /tmp/hb_report_log
which will then gather all data from all available cluster nodes and create a file named:
which contains the information that is needed.
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7007262
- Creation Date: 25-Nov-2010
- Modified Date:28-Jun-2021
- SUSE Linux Enterprise High Availability Extension
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com