Environment

• Cb Response Server: All Versions
• RHEL: All Supported Versions
• CentOS: All Supported Versions

Objective

Provide steps to collect server-side diagnostics for standalone and clustered installations of the Cb Response Server

Resolution

Ensure there is available disk space allocated to it before executing this script. Running this script without sufficient space could result in server failure

1. On your Cb Response Server (on Master server, if applicable), run the cbdiag script with the --post (optional) argument:
   

   sudo /usr/share/cb/cbdiag --post

2. If the command fails to post to the Alliance Server, then the cbdiag_*.zip archive file will have been saved in the location you ran the command from

The --post argument will automatically send results to the Alliance Server
In a cluster environment, diagnostics from minion nodes should be collected at the same time
Ask the Support Engineer assigned your case if you're unsure
If the post fails, send this file to us manually at Cb Vault 

Additional Notes

• The cbdiag script uses the /tmp directory as a temporary staging directory.
• If the /tmp directory does not have sufficient space, the cbdiag script can be redirected using the following command
  

  /usr/share/cb/cbdiag --tmpdir=/more/space/here --post

Related Content

cbdiag - "no space left on device" error when executing