You can use the s9s_error_reporter tool to generate error reports, and then attach the error report to the Support Ticket.
s9s_error_reporter -i <CLUSTER_ID>
Where <CLUSTER_ID> is the ID of the cluster you want to create the error report for. Run the script on the controller. A file error_report_YYYYMMDD-HHMMSS.tar.gz will be created and this should be attached to the support ticket.
Run all commands below on the controller:
To invoke it do:
bash s9s_error_reporter -i 1
#as a non-root user:
sudo s9s_error_reporter -i 1
It will print out something like:
Severalnines: Copying logs
192.168.100.150: Executing 'cp /var/lib/mysql/error.log /tmp'[ok]
192.168.100.153: Executing 'rm /tmp/cmon.log'[ok]
Please attach /tmp/error_report_20120301-215701.tar.gz to the support issue.
So attach the generated log file to your Support Issue, and we will be able to help you much faster.
s9s_error_reporter generates a tar.gz file containing a lot of information about the Cluster (cmon logs, error logs, and the content of some important cmon tables).
We also recommend you take a screenshot showing the problem area, e.g, the Overview from the UI is always great to see if there are node failures / cluster issues / missing data.
I get following message when execute bash ./s9s_error_reporter -i 1
Could not find mysql client binary
Change MYSQL_BIN in beginning of the scipt
to show the path, run which mysql
After that, vi s9s_error_reporter and change the MYSQL_BIN to following:
Hope this help who get the same error.
Thanks for the remark. We will fix this issue in the next release.
Please sign in to leave a comment.