View Source

h2. Reporting Issues

Anytime you experience troubles running KIM, you should check the logs. They provide information that may help you to solve the problem. Tomcat logs can be found at: *<TOMCAT_HOME>/logs* and KIM logs can be found at: *<KIM_HOME>/log*. You can control the amount of details in KIM logs by modifying the [log4j|http://logging.apache.org/log4j/1.2/manual.html] configuration file *<KIM_HOME>/config/log.prop*. See [the log4j 1.2 documentation|http://logging.apache.org/log4j/1.2/manual.html] for details on log tuning.

h2. Collecting Full Logging Information

There are generally two types of problems you might experience. One type can be problems that are repeated multiple times if specific steps are performed, others can cause shutdown issues or can occur randomly.

If you can isolate a scenario reproducing the problem, you can follow the steps below to collect and send us the full logging information we need in order to assist you:

# Stop KIM.
\\
\\
# Enable *DEBUG* logging of KIM by changing the line
{{_@log4j.rootLogger=INFO, aAll, cAll@_}}
to
{{_@log4j.rootLogger=DEBUG, aAll, cAll@_}}
in the KIM section of *<KIM_HOME>/config/log.prop*.
{note}Keep in mind that KIM performance will be significantly reduced in *DEBUG* mode.{note}\\
# Archive and then delete the contents of the *<KIM_HOME>/log* folder.
\\
\\
# Open the servlet container log folder, archive and delete its content.
\\
\\
# Start KIM.
\\
\\
# Execute the scenario leading to the problem.
\\
\\
# Stop KIM.
\\
\\
# Collect the following logs:
#* The contents of the *<KIM_HOME>/log* folder.
#* The console output of KIM.
(/) *Tip*: On Linux, start KIM with
{code}nohup ./kim start &{code}
This will put the console output in *<KIM_HOME>/bin/nohup.out*.
#* The console output or any other scripts used in the tests - tools/populate, tools/rdf etc.
#* The contents of the servlet container log folder.
\\
\\
# Zip and send them to _[kim-discussion@ontotext.com|mailto:kim-discussion@ontotext.com]_.
{note}When debugging a shutdown issue of KIM, start from step 7.{note}

For problems that you can not reproduce using a step by step scenario, follow the instructions below:

# Stop KIM.
\\
\\
# Collect the following logs:
#* The contents of the *<KIM_HOME>/log* folder.
#* The console output of KIM.
(/) *Tip*: On Linux, start KIM with {code}nohup ./kim start &{code}. This will put the console output in *<KIM_HOME>/bin/nohup.out*.
#* The console output or any other scripts used in the tests - tools/populate, tools/rdf etc.
#* The contents of the servlet container log folder.
\\
\\
# Zip and send them to _[kim-discussion@ontotext.com|mailto:kim-discussion@ontotext.com]_.