Overview of TrueSight Server Automation log files
A standard TrueSight Server Automation installation provides default logging behavior that satisfies the needs of many organizations. Defaults vary for Windows and UNIX systems. The following table lists the various log files used by TrueSight Server Automation that might be of interest to you.
Log file name | Description and default location | Where to configure |
|---|---|---|
TrueSight Server Automation Application Server | ||
appserver.log | Application Server log, installDirectory/br/appserver.log The log file is generated as a stream at the info level. | installDirectory/br/deployments/deploymentName/log4j2.xml For more information, see Controlling-Application-Server-logging. Besides configuring log settings through the log4j2.xml file, you can also change the name of the log file through the console. |
AppServerLauncher.log | Application Server Launcher log, installDirectory/br/AppServerLauncher.log | installDirectory/br/deployments/_template/log4j2.xml |
post_install.log | Application Server configuration log, installDirectory/br/post_install.log | installDirectory/br/deployments/deploymentName/log4j2.xml |
console.log | Application Server Console log, installDirectory/br/console.log | installDirectory/br/deployments/deploymentName/log4j2.xml For more information, see Enabling more detailed logging. Besides configuring log settings through the log4j2.xml file, you can also change the name of the log file through the console. |
Note: If you have multiple Application Server deployments, the names listed above are for the log files of the default Application Server deployment. The names of the log files for all other Application Server deployments are prefixed with the name of the deployment, connected with an underscore. | ||
RSCD Agent | ||
rscd.log |
The log file is generated as a rollfile at the info1 level. | rscdInstallDirectory/log4crc.txt For more information, see Controlling-RSCD-agent-logging. Alternatively, to set the log level to debug, you can use the agentctl toggle command. |
rscdsvc.log | Windows RSCD Agent service log, rscdInstallDirectory\rscdsvc.log The log file is generated as a rollfile at the info level. | |
keystroke.log | nexec session log, rscdInstallDirectory/log/keystroke.log | |
bldeploy*.log and bltargetjobmanager*.log | A pair of Deploy Job logs in rscdInstallDirectory/Transactions/log/ or in the location specified for the server through the TRANSACTION_DIR property. By default, logging is on the debug level. For more information, see Logs-for-Deploy-Jobs. Note: BLPackage Deploy Jobs on the console log to stdout as a stream at the debug level. The priority level can be overridden using Transaction Options when defining the BLPackage Deploy Job. For more information, see Specifying-job-options. | rscdInstallDirectory/log4crc.txt |
blasadmin | ||
blasadmin.log | blasadmin utility log, installDirectory\bin\blasadmin.log | <where to configure> |
TrueSight Server Automation Console (Windows) | ||
.log | TrueSight Server Automation Console log, | installDirectory\br\rcp.cf |
BLWorkbenchPlugin.log | BLWorkbenchPlugin log, | installDirectory\br\rcp.cf |
TrueSight Server Automation Console (UNIX) | ||
.log | TrueSight Server Automation Console log, | installDirectory/br/rcp.cf |
BLWorkbenchPlugin.log | BLWorkbenchPlugin log, | installDirectory/br/rcp.cf |
PXE server | ||
pxesrvr.log | PXE server log, installDirectory/br/pxesrvr.log | installDirectory/br/deployments/_pxe/log4j2.xml For more information, see Controlling-PXE-server-logging. |
tftpsvr.log | TFTP Server log, installDirectory/br/tftpsvr.log | installDirectory/br/tftpsvr.cf For more information, see Controlling-PXE-server-logging. |
BLCLI (Windows) | ||
blcli.log | %APPDATA%\BladeLogic\blcli.log | %APPDATA%\BladeLogic\blcli-log.cf For more information, see BLCLI-command-results. |
BLCLI (UNIX) | ||
blcli.log | $HOME/.bladelogic/blcli.log | $HOME/.bladelogic/blcli-log.cf For more information, see BLCLI-command-results. |
Custom Configuration Objects | ||
blcoserver_*.log | Custom Configuration Object log, one log file for each custom configuration object. The name of the custom configuration object appears within the log file name. The log file is stored by default in rscdInstallDirectory. | rscdInstallDirectory\log4crc.txt |
REST APIs | ||
restapi_<deployment_name>.log | The log file is located on the Application Server at the following path:
| <TSSA_installation_directory>\NSH\br\restapi_<deployment_name>.log For more information, see Using-the-REST-APIs. |