PingAuthorize

Available tool options

The following options are available for the collect-support-data tool:

--noLdap

Specifies that no information should be collected over LDAP. Use this option only if the server is completely unresponsive or won’t start, and only as a last resort.

--pid <pid>

Specifies the ID of an additional process from which information should be collected. This is a useful option for troubleshooting external server tools, and you can specify it multiple times for each external server.

--sequential

Use this option to troubleshoot Out of Memory errors. By default, the collect-support-data tool collects data in parallel to minimize the collection time necessary for some analysis utilities. This option specifies that data collection should be run sequentially rather than in parallel. Specifying this option reduces the initial memory footprint of the collect-support-data tool but increases the time required for completion.

--reportCount <count>

Specifies the number of reports generated for commands that support sampling (for example, vmstat, iostat, or mpstat). If you specify a value of 0, no reports are generated for these commands. If you don’t provide this option, the number of reports generated defaults to 10.

--reportInterval <interval>

Specifies the number of seconds between reports for commands that support sampling (for example, mpstat). You must specify a value greater than 0 for this option. If you don’t provide this option, the number of seconds between reports defaults to 1.

--maxJstacks <number>

Specifies the number of jstack samples to collect. If you don’t provide this option, the number of samples collected defaults to 10.

--collectExpensiveData

Specifies that data for expensive or long-running processes should be collected. To prevent a negative impact on server performance, data for these processes are not collected by default.

--comment <comment>

Allows provisioning of additional information about the collected data set. The comment you provide will be added to the generated archive as a README file.

--includeBinaryFiles

Specifies that binary files should be included in the archive collection. By default, all binary files are excluded from data collection.

--outputPath

Specifies the path (and optionally, the name) for the support data archive file. If the path specifies a filename, the archive is written to that file. If the path specifies a directory, the file is written to that directory with a server-generated name.

--useRemoteServer

Invokes the collect-support-data tool against a remote server instance and streams the output and resulting support data archive back to the client. This is a useful option when the server instance is running in a container, as it might otherwise be difficult to invoke commands or access files in that container.