Administration Guide > TDV Logging Information > About TDV Log Files > Server, Monitor, and Studio Log Files
 
Server, Monitor, and Studio Log Files
TDV provides log and output files for TDV Server, Business Directory Server, and Studio. You can access logs directly. If you have appropriate rights, you can use the Send/Save Logs tool in Studio or Manager to access the files, and to export all of the log files into a zip file.
• The Studio main log file is located in <Studio_install_dir>/logs (“Studio” in the table).
• Most of the other files are generated for both TDV Server and Business Directory Server.
• TDV Server log and output files are stored in <TDV_install_dir>/logs (“TDV” in the table).
• Business Directory Server log and output files are stored in <BD_install_dir>/logs (“BD” in the table).
• In a clustered environment, logs are not shared between instances, so be sure to retrieve log files from the appropriate server. For this purpose, always connect through physical addresses, not virtual addresses.
Note: For information about the installer log files, refer to Installation and Uninstallation Logs.
File Name
Log Directory
Description
cs_bd.out
BD
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_cs_csmonitor_daemon.log
cs_bd_csmonitor_daemon.log
TDV,
BD
Tracks the TDV or Business Directory Monitor if it is running as a daemon.
cs_bundles.log
cs_bd_bundles.log
TDV,
BD
Tracks the activity of TDV and Business Directory when they are installed as a bundle.
cs_cluster.log
cs_bd_cluster.log
TDV,
BD
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_csmonitor_collector.log
cs_bd_csmonitor_collector.log
TDV,
BD
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_csmonitor_server.log
cs_bd_csmonitor_server.log
TDV,
BD
Tracks TDV and Business Directory Monitor activities.
cs_data_cache-<day>.log
TDV
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_monitor_events.log
cs_bd_monitor_events.log
TDV,
BD
Monitor Daemon events log. Records the categories of events selected through configuration parameters. See Configuring and Enabling Event Logging.
cs_monitor.log
cs_bd_monitor.log
TDV,
BD
Monitor Daemon main log. If the TDV Server does not start or stops responding, this log and cs_server.log are the files to check for errors.
cs_monitor.out
cs_bd_monitor.out
TDV,
BD
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_monitor.out1, cs_monitor.out2, etc), once a defined limit is reached. This limit is specified in the file <TDV_Install_Dir>/conf/monitor/wrapper.conf
The default limit is 10MB.
cs_repository-<day>.log
TDV, BD
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_server_client.log
cs_bd_server_client.log
TDV,
BD
Log of activities of TDV Server or BD Server clients. Use this in combination with cs_studio.log to resolve connection issues between Studio and TDV.
cs_server_dsrc.log
cs_bd_server_dsrc.log
TDV,
BD
Log of data source functionality.
cs_server_events.log
cs_bd_server_events.log
TDV,
BD
Server events log. Records the categories of events selected through configuration parameters. See Configuring and Enabling Event Logging.
cs_server_file_cache.log
cs_bd_server_file_cache.log
TDV,
BD
Tracks TDV and Business Directory Monitor file-cache activities.
cs_server_metadata.log
cs_bd_server_metadata.log
TDV,
BD
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_server_status.log
cs_bd_server_status.log
TDV,
BD
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_server_task.log
cs_bd_server_task.log
TDV,
BD
Supplements cs_server.log with exceptions that occur outside of the main execution thread (for example, in background threads).
cs_server.log
cs_bd_server.log
TDV,
BD
Main log. Nearly every error that occurs is logged here. A notable exception is unexpected Server crashes. If the TDV 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_server.out
cs_bd_server.out
TDV,
BD
Standard output and error log for TDV (ServerBoot) and BD Server (BDServerBoot) processes. Any thread dumps of a ServerBoot process are written to this file.
cs_tools.log
cs_bd_tools.log
TDV, BD
Tracks the errors that occur from the command line utilities in TDV Server and BD (for eg. server_util.sh, encryption_util.sh, bd_encryption_util.sh, bd_server.sh, etc.).
cs_studio.log
Studio
The Studio main log file. Use this in combination with cs_server_client.log to resolve connection issues between Studio and TDV.