cs_bd.out

Business Directory log. Lists the current user and actions specified by VM_ARGS, such as installing, starting, stopping, and uninstalling Windows services, the BD repository, and the BD Monitor Daemon.

cs_bd_csmonitor_daemon.log

Tracks the Business Directory Monitor if it is running as a daemon.

cs_bd_bundles.log

Tracks the activity of Business Directory when they are installed as a bundle.

cs_bd_cluster.log

Records all Active Cluster log messages. This file resides in the cluster directory under the logs directory. For usage in a TDV or BD cluster environment, refer to the TDV Active Cluster Guide. The Cluster Logging Detail Level and Cluster Event configuration parameters determine what to include.

cs_bd_csmonitor_collector.log

Log for the TDV Monitor Server (which is distinct from the Monitor Daemon process, MonitorBoot). Collectors hosted within the monitored TDV instances periodically take snapshots of the current state of the host instance, and keep track of general activity such as requests, sessions, transactions, and events.

cs_bd_csmonitor_server.log

Tracks Business Directory Monitor activities.

cs_data_cache-<day>.log

Data cache logs, each with a 3-letter day of the week (Mon, Tue, Wed, and so on) in its name. These reside in the cs_data_cache directory under the logs directory.

cs_bd_monitor_events.log

Monitor Daemon events log. Records the categories of events selected through configuration parameters.

cs_bd_monitor.log

Monitor Daemon main log. If the Server does not start or stops responding, this log and cs_bd_server.log are the files to check for errors.

cs_bd_monitor.out

Combines stdout and stderror for the Monitor Daemon (MonitorBoot) process. Any thread dumps of the Monitor Daemon process are written to this file.

Note: In the windows platform, additional log files are created with a numeric suffix that increments by 1 (for example cs_bd_monitor.out1, cs_bd_monitor.out2, etc), once a defined limit is reached. This limit is specified in the file <BD_Install_Dir>/bd/conf/monitor/wrapper.conf

The default limit is 10MB.

cs_repository-<day>.log

Repository logs, each with a 3-letter day of the week (Mon, Tue, Wed, and so on) in its name. These reside in the cs_repository directory under the logs directory. These files record repository database events and status for TDV and BD.

Note: If you use “composite.sh monitor stop” from the command-line, ServerBoot posts the message, “LOG: could not receive data from client: No connection could be made because the target machine actively refused it.” Because ServerBoot is a child process, it cannot be prevented from posting this message. However, if this message is not logged twice in a row, No error has actually occurred.

cs_bd_server_client.log

Log of activities of BD Server clients.

cs_bd_server_dsrc.log

Log of data source functionality.

cs_bd_server_events.log

Server events log. Records the categories of events selected through configuration parameters.

cs_bd_server_file_cache.log

Tracks Monitor file-cache activities.

cs_bd_server_metadata.log

Records what objects are being written to the repository, or changes to it.

For usage in a TDV or Business Directory cluster environment, refer to the TDV Active Cluster Guide. The Cluster Logging Detail Level and Cluster Event configuration parameters controls the categories of logging to include.

cs_bd_server_status.log

Server Status log files can be used to determine software license conformance and help with corporate asset management. This log keeps data from each server session that is initiated.

cs_bd_server_task.log

Supplements cs_bd_server.log with exceptions that occur outside of the main execution thread (for example, in background threads).

cs_bd_server.log

Main log. Nearly every error that occurs is logged here. A notable exception is unexpected Server crashes. If the Server does not start or stops responding, this log and cs_monitor.log are the files to check for errors. This file also includes data source type and version information.

cs_bd_server.out

Standard output and error log for BD Server (BDServerBoot) processes. Any thread dumps of a ServerBoot process are written to this file.

cs_bd_tools.log

Tracks the errors that occur from the command line utilities (for eg. bd_encryption_util.sh, bd_server.sh, etc.).