Downloading diagnostic data

About this task

Download a compressed tarball that contains diagnostic information about the OpsCenter daemon and all the nodes in a specific cluster. Examine the diagnostic data and provide the diagnostic tarball to DataStax Support to facilitate resolving any issues.

If downloading the tarball times out, increase the default value of the diagnostic_tarball_download_timeout option in cluster_name.conf. Increasing the default value is recommended for DSE multi-instance clusters or for slower machines and connections.

The location of the cluster_name.conf file depends on the type of installation:

  • Package installations: /etc/opscenter/clusters/cluster_name.conf

  • Tarball installations: install_location/conf/clusters/cluster_name.conf

Procedure

  1. From the OpsCenter Monitoring main menu, click Help > Diagnostics.

    The Collect Diagnostic Data dialog appears.

    collectDxData

  2. If the OpsCenter instance is monitoring multiple clusters, select a cluster.

  3. Click Download.

  4. If DataStax Enterprise was installed using the Installer-No Services or tarball, or the system.log is not located in the default directory (/var/log/cassandra), OpsCenter cannot detect the system log location. The DSE System Log Location dialog appears and prompts you to enter the full path to the system.log location.

    dxTarballSysLogLocation

    If you do not enter the system log location, the system log information is not included in the diagnostic report tarball.

    1. Enter the full path to the DSE system log in the System Log Location box.

    2. Click Save.

  5. A message indicates that OpsCenter is collecting cluster data. Save the tarball to your local machine.

    diagnostics.tar.gz

    Depending on your browser settings, you might be prompted for a file directory in which to save the tarball. For assistance with troubleshooting issues, provide the diagnostic tarball to DataStax Support.

    When the zipped tarball is expanded, the main folder is named cluster name-diagnostics-UTC timestamp. For example,

    prodNorth-diagnostics-2017_08_30_15_32_41_UTC