The tpm diag command will create a ZIP file including log files and current dataservice status. It will connect to all servers listed in the tpm reverse output attempting to collect information.
shell> tpm diag
NOTE >> host1 >> Diagnostic information written to /home/tungsten/tungsten-diag-2013-10-09-21-04-23.zip
The information collected depends on the installation type:
Within a staging directory installation, all the hosts configured within the cluster will be contacted, and all the information across all hosts will be incorporated into the Zip file that is created.
Within an INI installation, the other hosts in the cluster will be contacted if ssh has been configured and the other hosts can be reached. If ssh is not available, a warning will be printed, and each host will need to be accessed individually to run tpm diag.
The structure of the created file will depend on the configured hosts, but will include all the logs for each accessible host configured. For example:
Archive: tungsten-diag-2014-07-08-11-24-01.zip Length Date Time Name --------- ---------- ----- ---- 0 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ 0 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl1/ 20977 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl1/cctrl.txt 19608 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl1/connector.log 1195 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl1/manifest.json 94 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl1/thl.txt 87397 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl1/tmsvc.log 444 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl1/tpm.txt 1142 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl1/trepctl.json 1411 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl1/trepctl.txt 45862 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl1/trepsvc.log 0 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl2/ 20977 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl2/cctrl.txt 19608 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl2/connector.log 1195 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl2/manifest.json 94 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl2/thl.txt 91661 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl2/tmsvc.log 444 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl2/tpm.txt 1120 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl2/trepctl.json 1388 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl2/trepctl.txt 44500 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl2/trepsvc.log 0 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl3/ 20977 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl3/cctrl.txt 19608 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl3/connector.log 1195 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl3/manifest.json 94 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl3/thl.txt 86444 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl3/tmsvc.log 444 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl3/tpm.txt 1120 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl3/trepctl.json 1387 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl3/trepctl.txt 44500 2014-07-08 11:24 tungsten-diag-2014-07-08-11-24-01/ct_ssl3/trepsvc.log --------- ------- 534886 31 files