Semaphore application log files
- Last Updated: June 23, 2026
- 4 minute read
- Semaphore
- Documentation
This section describes the available logging facilities for the Semaphore applications. Log files can be used to help trace down issues and/or track activity occurring in the various Semaphore components.
Classification Server logging
| Default Configuration File | <Installation Directory>\conf\config.xml (configuration format is originally based on the “log4cpp” logging mechanism) |
|---|---|
| Default Log Location | <Installation Directory>\logs |
| Log Levels | **DEBUG - Most verbose logging INFO - Information logging messages NOTICE - Notification logging messages WARN - Warning messages (recommended setting for production use) ERROR - Error messages CRIT - Critical (error) messages ALERT - Alerting messages (not used) FATAL **- Fatal (error) messages |
| Log File Name | crt.log - Contains a log of all (successful) requests to CS. runtime.log - Contains a log of all CS activity. |
| Log File Format (crt.log) | Layout is configurable in the configuration file, default is as follows (CSV format): <Error number or 0 if no error>,<Finish time in yyyy-MM-dd HH:mm:ssZ“>,<Source IP Address>,<Operation>,<Time Taken>,<File Name>,<URL>,<Meta Original URL>,<Document Hash>,<Audit Tag>,<Scores> If error, then the format is as follows: <Error Number>,<Finish time in yyyy-MM-dd HH:mm:ssZ”>,<Source IP Address>,<Operation>,<Time Taken>,<File Name>,<URL>,<Meta Original URL>,<Audit Tag>,<Error Component>,<Error Message> |
| Log File Format (runtime.log) | <Request date in dd Mmm YYYY HH:mm:ss.sss> [<thread>] [component] : <Message> |
Note: For any classification server failures, the “failures” directory (set in the “failure_dir” setting) contains a file with the request and (if possible) another file containing the original document. Similarly you can configure classification server to save any successful requests (for debugging purposes) by un-commenting the “success_dir” settings from the default configuration file.
Document Analyzer (Studio sub-component) logging
| Default Log Location | <Studio Installation Directory>\da\logs\ |
|---|---|
| Log Levels | **TRACE - Most verbose logging DEBUG - Debugging log messages INFO - Information logging messages WARN - Warning messages (recommended setting for production use) ERROR **- Error messages only |
| Log File Name (Default) | DA.log (log file rotation based upon date) |
| Log File Format | YYYY-MM-DD HH:MM:SS.sss <Message Level> [<section>] <class section> - <Message text> |
Additional log files in “<Studio Installation Directory>\da\logs\” that may of assistance when troubleshooting Document Analyzer issues:
- gc-<datetime>.log - Standard Java garbage collection logs (often shows signs of memory issues).
Knowledge Model Management (Studio sub-component) logging
| Default Logging Configuration File | <Studio Installation Directory>\kmm\webapps\ROOT\WEB-INF\classes\logback.xml (uses the “logback” logging framework, further information is available from logback.qos.ch) |
|---|---|
| Default Log Location | <Studio Installation Directory>\kmm\logs |
| Log Levels | **TRACE - Most verbose logging DEBUG - Debugging log messages INFO - Information logging messages WARN - Warning messages (recommended setting for production use) ERROR **- Error messages only |
| Log File Name (Default) | SemaphoreWorkbench.log (maximum log size of 1 Mb with log file rotation based upon date/maximum size) |
| Log File Format (SemaphoreWorkbench.log) | Layout is configurable in the configuration file, default is as follows: YYYY-MM-DD HH:MM:SS,sss <log level> [<thread reference>] <Module Name>:<Module line number> - <Message> |
| Log File Format (SemaphoreSparql.log) | Layout is as follows: YYYY-MM-DD HH:MM:SS,sss <log level> [<thread reference>] <Module Name>:<Module line number> - <Message> (followed by SPARQL statement) |
Additional logs in “<Studio Installation Directory>\kmm\logs” that may of assistance when troubleshooting Knowledge Model Management issues:
- catalina.log - All nested tomcat instance messages are logged here. The information found here is configured by “<Studio Installation Directory>\kmm\conf\logback-tomcat.xml” (this facility makes use of “logback” logging framework, for more information see logback.qos.ch).
- catalina.out - Back-end (Tomcat) Catalina server containing all events.
- gc-<datetime>.log - Standard Java garbage collection logs (often shows signs of memory issues).
- localhost-access.log - Access logs for KMM, that is, all web accesses to Knowledge Model Management are logged here. The information found here is configured by “<Studio Installation Directory>\kmm\conf\logback-access.xml” (this facility makes use of “logback” logging framework, for more information see logback.qos.ch).
- localhost.log - Default back-end (Tomcat) log containing log events from the default application (Studio).
- SemaphoreSparql.log - A record of all SPARQL execution (including reports). Configured in “<Studio Installation Directory>\kmm\webapps\ROOT\WEB-INF\classes\logback.xml” (uses the “logback” logging framework, further information is available from logback.qos.ch). Files roll over daily with up to 30 days of history kept.
Semantic Enhancement Server logging
| Default Logging Configuration Files | <SES Installation Directory>\solr\server\resources\log4j.properties (uses the “log4j” logging framework, further information is available from log4j) |
|---|---|
| Default Log Location | <SES Installation Directory>\solr\server\logs\ |
| Log Levels | **DEBUG - Most verbose logging INFO - Informational logging messages WARN - Warning messages (recommended for production environments) ERROR **- Error messages only |
| Log File Name | solr.log - Contains the log for the running SoLR instance hosting SES. |
| Log File Format | Layout is configurable in the configuration file, default is as follows: YYYY-MM-DD HH:MM:SS,sss <log level> (section) [<core reference>] <Module Name> <Message text> |
Publisher logging
| Default Log Location | <Studio Installation Directory>\kmm\logs\publisher-logs |
|---|---|
| Log File Name | PublisherPlugin-<model name>-<date time of publish>.log |
| Log File Format | YYYY-MM-DD HH:MM:SS,sss [:] <log level> [<section>] <Module Name>:<Line Number> - <Message text> |
Studio logging
| Default Configuration File | <Studio Installation Directory>\studio\webapps\ROOT\WEB-INF\classes\logback.xml |
|---|---|
| Default Log Location | <Studio Installation Directory>\studio\logs\ |
| Log Levels | **TRACE - Most verbose logging DEBUG - Debugging log messages INFO - Information logging messages WARN - Warning messages (recommended setting for production use) ERROR **- Error messages only |
| Log File Name (Default) | Studio.log (maximum log size of 1 Mb with log file rotation based upon date/maximum size) |
| Log File Format | YYYY-MM-DD HH:MM:SS.sss [<user>:<connection>] <Message Level> {<Thread>} [<class section>] : <Message text> |
Additional logs in “<Studio Installation Directory>\studio\logs” that may of assistance in troubleshooting Studio issues:
- catalina.log - All nested tomcat instance messages are logged here. The information found here is configured by “<Studio Installation Directory>\studio\conf\logback-tomcat.xml” (this facility makes use of “logback” logging framework, for more information see logback.qos.ch).
- catalina.out - Back-end (Tomcat) Catalina server containing all events.
- gc-<datetime>.log - Standard Java garbage collection logs (often shows signs of memory issues).
- localhost-access.log - Access logs for studio, that is, all web accesses to Studio are logged here. The information found here is configured by “<Studio Installation Directory>\studio\conf\logback-access.xml” (this facility makes use of “logback” logging framework, for more information see logback.qos.ch).
- localhost.log - Default back-end (Tomcat) log containing log events from the default application (Studio).