The diagnostics command generates a diagnostic package that Symantec Support can use to analyze problems with the product.
You should specify a valid URL unless you use the --find-other-cores option. If you specify a valid URL but do not specify the data collection options, diagnostics uses the following parameters by default:
--config --crash-info 5 --logs 100000
When the user name or password are part of the URL, write them in quotes if they have any special shell characters in them. The password can be specified in the URL or at the password prompt. An example of the URL syntax is as follows:
If you specify a path that ends with a forward slash, the diagnostics file is written to the path that you specify with the default file name. If you specify a path that does not end with a forward slash, the backup file is written with the file name specified in the path.
The default diagnostics file name is in the following format:
An option cannot be specified more than once whether it is in its long form or short form. For the --cores option, a component cannot be specified more than once either with the component name or convenient string all. If you attempt to, an error message appears along with the appropriate usage text.
Collect only the configuration data. The configuration data includes Symantec Protection Center (SPC) registration details, if available.
Collect the latest n core directories, including core files for a component. The valid range for n is 1 through 9,999.
The list of components include the following:
--cores mta n collects MTA core packages
--cores bmagent n collects Brightmail Agent core packages
--cores bmserver n collects Brightmail Server core packages
--cores conduit n collects Conduit core packages
--cores jlu-controller n collects Java LiveUpdate core packages
--cores dds n collects Directory Data Service core packages
--cores other n collects the other core files that are not collected with other options.
--cores all n
all is a convenient identifier that means all components.
Collect the latest n core directories (excluding the core files in those directories) for the following processes:
The valid range for n is 1 through 9,999.
Collect the exact data match (EDM) record sets.
Discover any core file outside of /data/scanner/jobs and move them to /data/scanner/jobs/other.
If Symantec Messaging Gateway discovers and moves any core files, an email notification is sent to the administrators that are specified to receive alerts. If not, no email notification is sent.
You can use this option with the delete cores command to clean up core files on your product. Run this command first to move the core files that are not in the jobs directory to the jobs directory. Then use delete cores to delete the core files.
If --find-other-cores is the only data collection option specified, a URL is not required. No diagnostics package is generated.
Force diagnostics to run even if a diagnostics collection that is started from the user interface is still in progress. If a package creation is in progress, the existing diagnostics collection fails.
Generate a core image of the specified component and download it. You can use this option to capture necessary data regarding a hung or spinning component, before restarting the component. This option does not stop or restart a process, but it may cause the process to pause briefly. The available components are:
Display this message.
Collect queue data from old postfix queues.
This command is only useful on configurations in which Symantec Messaging Gateway is migrated from version 7.7 or earlier. This command is not applicable for Symantec Messaging Gateway version 8 or higher.
Collect legacy ldapsync data.
This command is only useful on configurations in which Symantec Messaging Gateway is migrated from version 8 or earlier. This command is not applicable for Symantec Messaging Gateway version 9 or higher.
Collect all logs of all log files.
Collect log data that is limited to n lines per log file.
The valid range for n is 1 through 2,147,483,647.
Collect a snapshot output of the following monitor command: monitor -c 6 --proc bmserver --proc mta system database disk mta p_all and existing monitor logs under /data/monitor.
Collect all rules that are present on the Scanner, except exact data match data.
Collect Message Audit Log files.
Show the command process in verbose mode.
The syntax for the URL paths referenced by this command is as follows:
Copies the diagnostics package remotely through SCP.
Copies the diagnostics package remotely through FTP.
If no user name and password are specified, an anonymous login is used.
Logon is attempted with the user name and password credentials that are provided on the command line. If special characters are included in the password, you must enclose the password in single quotes ('). If the special characters in a password include a single quote, you can use the double quote instead ("). If no credentials are specified, anonymous logon is used.
Create a diagnostics file and transfer it with the SCP protocol. The diagnostics file (in the format:
diagnostics.yy-mmm-dd-hh-mm.hostname.tar.gz) is transferred to the SCP destination.
The month is expressed in the three-letter format, not two-digit format.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
This will clear the history and restart the chat.