The tungsten_send_diag command is a utility script which assists in the upload of files to Continuent support.
tungsten_send_diag may be used in place of the Section 9.5.6, “tpm diag Command” to generate a diagnostic package.
tungsten_send_diag [ --args, -a ] [ --case, -c ] [ --cleanup ] [ --contentType ] [ --debug ] [ --diag, -d ] [ --email, -e ] [ --file, -f ] [ --help, -h ] [ --tpm, -t ] [ --verbose, -v ]
Where:
Table 8.54. tungsten_send_diag Command-line Options
| Option | Description |
|---|---|
--args, -a | Specify arguments to be passed to tpm diag. Arguments must be passed in quotes. Requires the --diag option. |
--case, -c | Specify the support case number |
--cleanup | When specified, will cause the removal of the diagnostic archive file generated by the --diag argument. |
--contentType | Specify the Content-Type for a file you are uploading |
--debug | Debug mode is VERY chatty, avoid it unless you really need it. |
--diag, -d | Automatically generate a tpm diag zip file and upload it |
--email, -e | Email address to embed into the uploaded file name |
--file, -f | File name to upload |
--help, -h | Show help text |
--tpm, -t | Full path to the tpm command you wish to use to execute a tpm diag |
--verbose, -v | Show verbose output |
You must specify either
--diag,
--tpm, or
--file, but not both. For
example:
shell> tungsten_send_diag --diag -c 1234
To have tpm diag gather all nodes, add the
--args '--all', for example:
shell> tungsten_send_diag --diag -c 1234 --args '--all'
You must specify either
--email or
--case, and you may provide
both if you wish. For example:
shell> tungsten_send_diag -f example.zip -e you@yourdomain.com -c 1234
Using --tpm to specify one
or more tpm commands implies the
--diag option, you do not
need to specify --diag if
you use --tpm (or
-t). For example:
shell> tungsten_send_diag -c 1234 -t /opt/replicator/tungsten/tools/tpmYou may generate multiple diags by specifying multiple tpm binaries with multiple arguments, i.e.:
shell> tungsten_send_diag -c 1234 -t /opt/continuent/tungsten/tools/tpm -t /opt/replicator/tungsten/tools/tpmIf you are unable to use tungsten_send_diag due to network rules and restrictions within your organisation, then you do not need to complete these steps.
Continuent is committed to implementing security best practices. To safeguard your uploaded diagnostic data, we routinely rotate the access keys used for upload functionality in our products. As a result, we routinely release a new version of tungsten_send_diag outside of our normal software release cycle.
Updated releases are made available via the download portal here
To install the new file:
Download the latest file from the download portal.
Upload the file to all hosts running Tungsten software. A good suggestion
would be to place the file into $HOME
path of the tungsten OS user.
Ensure the ownership of the file is correct
shell> chown tungsten: tungsten_send_diag
Copy the file to the running path of the tungsten deployment, by default
this would be under /opt/continuent. The value of this is determined
by the install-path within your tungsten.ini
file.
shell> cp ~/tungsten_send_diag /opt/continuent/tungsten/tungsten-replicator/bin
Copy the file to the software staging path, by default this would be under
/opt/continuent/software. If unsure, the value of this is determined
by executing tpm query staging, for example:
file.
shell>tpm query stagingtungsten@db1:/opt/continuent/software/tungsten-replicator-7.1.4-10 shell>cp ~/tungsten_send_diag/opt/continuent/software/tungsten-replicator-7.1.4-10/tungsten-replicator/bin
The final step will ensure that the new version of tungsten_send_diag is preserved should you execute ./tools/tpm update --replace-release from the staging directory during subsequent updates.
If upgrading to a new version of Tungsten that does not include the latest version of tungsten_send_diag, the above steps will need to be carried out post upgrade.