Server log files
|In this topic:|
Server log files
The Klocwork server log files are created when you start the Klocwork servers for the first time, and updated every time you restart the servers. They are stored in the following location:
For each server, the <projects_root>/logs directory contains:
- a main log file, named <server>.log
- <log-file>.log.command, which records the commands used to run the server. For example, the database.command.log file contains a record of all the commands you used to start or stop the Database Server.
When running Klocwork servers as Windows services, logging information is directed to the Windows event log. The following log files are also stored in <projects_root>/logs:
- <server>_service.log, showing the output when the server was started
- <server>_servicestop.log, showing the output when the server was stopped
Database Server messages in database.log
The Database Server messages are of the form
<ddmmyy> <hh:mm:ss> <path to mysqld executable>: <message>
031104 14:34:08 /space/jlee_local/klocwork/3rdparty/bin/mysqld: Shutdown Complete
License Server messages in license.log
The License Server messages are of the form
hh:mm:ss (<vendor daemon>) <message>
15:26:20 (lmgrd) klocwork using TCP-port 27000
Klocwork Server messages in klocwork.log
The Klocwork Server log file records message strings when the Klocwork Server is started or stopped.
Using CATALINA_BASE: "C:\Klocwork\Server\projects_root\tomcat" Using CATALINA_HOME: "C:\Klocwork\Server\3rdparty\tomcat" Using CATALINA_TMPDIR: "C:\Klocwork\Server\projects_root\tomcat\temp" Using JRE_HOME: "C:\Klocwork\Server\_jvm" Using CLASSPATH: "C:\Klocwork\Server\3rdparty\tomcat\bin\bootstrap.jar;C:\Klocwork\Server\3rdparty\tomcat\bin\tomcat-juli.jar"
Additional Klocwork Server logs
In addition to the Klocwork Server log file (klocwork.log), you will find the following Klocwork Server logs at <projects_root>/tomcat/logs:
- catalina.out (Unix only)
A log is produced for each day when a Klocwork Server event occurs.
These third-party logs may provide useful troubleshooting information (aside from the localhost_access_log file, which provides only a record of which user accessed the server).