Log Message Format

CDT prints log messages on the screen in this format:

<TimeStamp> *<Log_Level>* [<Name_of_Object>]: <Log_Message>

Example:

Mon Jan 15 17:35:50 2018 *A* [Main]:

Current execution logs are in this directory:

/var/log/CPcdt/logs_2018-01-15-17-35-50/

CDT saves its log messages in the CDT log files in this format:

<TimeStamp> *<Log_Level>*: <Log_Message>

Example:

Mon Jan 15 17:35:50 2018 *A*:

Current execution logs are in this directory:

/var/log/CPcdt/logs_2018-01-15-17-35-50/

CDT sends its log messages to the Syslog server in this format:

<TimeStamp> CDT *<Log_Level>* [<Name_of_Object>]: <Log_Message>

Example:

Mon Jan 15 17:35:50 2018 CDT *A* [Main]:

Current execution logs are in this directory:

/var/log/CPcdt/logs_2018-01-15-17-35-50/

Debug Configuration

A number of debug configurations are available, which can control different aspects of CDT's operation.

Change the CDT primary configuration file in this way:

Step	Description
1	Backup the current CentralDeploymentTool.xml file: `[Expert@HostName:0]# cd /some_path_to_CDT/` `[Expert@HostName:0]# cp -v CentralDeploymentTool.xml{,_ORIGINAL}`
2	Edit the current CentralDeploymentTool.xml file: `[Expert@HostName:0]# vi CentralDeploymentTool.xml`
3	Go to the end of the file.
4	Add the relevant keys (see the table below) above the last tag </CentralDeploymentTool> in the following way: `... ... ...` `<Debug` KEY1`="`VALUE1`"/>` `<Debug` KEY2`="`VALUE2`"/>` `<Debug` KEY3`="`VALUE3`"/>` `... ... ...` `<Debug` KEYn`="`VALUEn`"/>` `</CentralDeploymentTool>`
5	Save the changes in the file and exit from Vi editor.
6	Run the CDT.

Important Notes:

If a key is not defined explicitly, then its default value is used (see the table below).
Enclose all values in double-quotes.
String values are case-sensitive.

List of keys:

Key Name	Default Value	Description
`InstallationTimeout`	`10800`	Timeout (in sec) for package installation
`StartDATimeout`	`300`	How much time (in sec) to wait for CPUSE "DA" service to start
`StopDATimeout`	`300`	How much time (in sec) to wait for CPUSE "DA" service to stop
`ValidatePolicyTimeout`	`1200`	How much time (in sec) to wait for security policy to be fetched
`ClusterValidationTimeout`	`1200`	How much time (in sec) to wait for cluster to become valid (synchronized)
`CollectLogsTimeout`	`600`	How much time (in sec) to wait for CPUSE logs collection to finish
`ExecuteInstallCmdTimeout`	`600`	How much time (in sec) to wait for CPUSE `install` command to finish
`ExecuteImportCmdTimeout`	`600`	How much time (in sec) to wait for CPUSE `import` command to finish
`DbgetTimeout`	`300`	How much time (in sec) to wait for `dbget` command to finish
`DbsetTimeout`	`300`	How much time (in sec) to wait for `dbset` command to finish
`CUSyncForVRRP`	`FALSE`	If set to `TRUE`, performs cluster Connectivity Upgrade on VRRP cluster (for specified clients with packages that support this)
`MDSAuditing`	`FALSE`	If set to `TRUE`, requires entering Multi-Domain Server Superuser or Domain Management Server Superuser username and password for performing installations. The username is logged for auditing purposes.
`CreateSnapshotTimeout`	`5400`	How much time (in sec) to wait for Gaia snapshot to finish
`DownloadingFromCloud`	`3600`	How much time (in sec) to wait for download from Cloud to finish
`CuSyncTimeout`	`900`	How much time (in sec) to wait for cluster synchronization to finish during Connectivity Upgrade
`ExecuteUninstallCmdTimeout`	`600`	How much time (in sec) to wait for CPUSE `uninstall` command to start
`FinishUninstallTimeout`	`3600`	How much time (in sec) to wait for package uninstall to finish
`FinishImportTimeout`	`1800`	How much time (in sec) to wait for package import to finish
`WaitAfterReboot`	`300`	How much time (in sec) to wait after we perform reboot