TCCS logging

You can examine TCCS log files to troubleshoot problems. TCCS log files are stored in: Windows systems: %USERPROFILE% \user-name\Siemens\ogs\tccs\TCCS\process\ tccs_os-user-name_%TCCS_CONFIG_host-name.log Linux systems: $HOME/user-name/Siemens/logs/tccs/TCCS/process/ tccs_os-user-name_$TCCS_CONFIG_host-name.log Users can change the log file location by setting the LOG_VOLUME_LOCATION environment variable to a different location. There are two logging configuration files, stored in the same location as the TCCS startup script. log.properties When TCCS starts, it looks for this file’s location in the classpath. The location is specified by the LogVolumeLocation parameter, which points to the logs value, which specifies the relative path to the TCCS startup script. TCCS log files are output to the TCCS/process subdirectory within the logs directory. Users can change the location that TCCS log files are stored by setting the LOG_VOLUME_LOCATION environment variable. In which case, the TCCS log files are written to LOG_VOLUME_LOCATION/TCCS/process. The log.properties file contains the LogConfigLocation parameter, which specifies the name of the logger definition file, stored in the same directory as the log.properties file. By default, this is the log4j2.xml file. log4j2.xml This file contains an Appenders section and an MLD Loggers section. The appenders are referenced by the logger definitions. Users can add additional loggers to the file. The following must be specified for each logger entry: logger name Specifies the name of the MLD logger. level value Specifies the level of logging performed by the specified logger. See the following table for default logging levels. By default, all logging levels are set to warn. appender-ref Specifies the appender to reference. For example: Logging level name Description fatal Logs only fatal errors. Fatal errors typically result in application shutdown. error Logs all errors. warn Logs all warnings and errors. info Includes debugging logs along with all warnings and errors. debug Includes debug log levels and debugging logs, along with all warnings and errors. Users can define their own custom log4j configuration. This allows them to supply their own configuration without affecting other users sharing the same TCCS deployment environment. In this case, the LOG_CONFIG_LOCATION environment variable must be set to specify the location of the custom log4j file.