Download diagnostic data
You can download a compressed tarball that contains diagnostic information about the OpsCenter daemon and all the nodes in a specific cluster.
You can examine the diagnostic data yourself, or provide the diagnostic tarball to IBM Support for troubleshooting assistance.
-
In the OpsCenter Monitoring menu, select Help, and then click Diagnostics.
-
If the OpsCenter instance is monitoring multiple clusters, select a cluster.
-
Click Download.
-
If OpsCenter cannot detect the
system.loglocation, enter the full path tosystem.login DSE System Log Location when prompted, and then click Save.This happens if DataStax Enterprise (DSE) was installed using the Installer-No Services or tarball options, or if
system.logisn’t located in the default directory (/var/log/cassandra).If you don’t provide the path to
system.log, then the system log information isn’t included in the diagnostic report tarball. -
Wait while OpsCenter collects cluster data and prepares the tarball.
If the tarball download times out, increase the default value of the
diagnostic_tarball_download_timeoutoption in your cluster-specific configuration file (CLUSTER_NAME.conf). Increasing this value is recommended for DSE multi-instance clusters, as well as slower machines and connections.The
CLUSTER_NAME.conffile is located at/etc/opscenter/clusters/for package installations and atINSTALL_DIRECTORY/conf/clusters/for tarball installations. -
Save the
diagnostics.tar.gztarball to your local machine. Depending on your browser, you might need to specify a directory where you want to save the diagnostic report tarball.If you extract the tarball, the primary directory is named
cluster name-diagnostics-timestamp_UTC, such asprodNorth-diagnostics-2017_08_30_15_32_41_UTC. -
For assistance with troubleshooting issues, provide the diagnostic report tarball to IBM Support.
