Locating Contour Logs in KOTS

Published Date: April 29, 2026
Audience: Everyone
Products and Versions Covered: 

• Jama Connect® all versions
  • Self-hosted: All

Summary

Contour logging can be relevant to troubleshoot Application behavior. Outside of commands to retrieve the logging via kuberentes such as:

kubectl logs core-0

Users may wish to find the 'permanent' path to these logging files.

Resolution

You can find contour logging with the following command on the Application Server:

sudo ls -l /var/openebs/local/$(kubectl get pvc | grep volume-core-0 | awk '{print $3}')/logs/contour

That will return a list such as:

-rw-r----- 1 91 91        0 Apr  6 18:42 contour-access.log
-rw-r----- 1 91 91    10883 Apr 23 19:14 contour-api.log
-rw-r----- 1 91 91        0 Apr  6 18:42 contour-cache.log
-rw-r----- 1 91 91     4792 Apr 21 19:36 contour-datasource.log
-rw-r----- 1 91 91        0 Apr  6 18:42 contour-delete.log
-rw-r----- 1 91 91 32336457 Apr 27 20:07 contour-dwr.log
-rw-r----- 1 91 91        0 Apr  6 18:42 contour-integrationsync.log
-rw-r----- 1 91 91        0 Apr  6 18:42 contour-threaddump.log
-rw-r----- 1 91 91  2690481 Apr 29 22:00 contour.log
-rw-r----- 1 91 91   112338 Apr 29 22:00 jama-job.log
-rw-r----- 1 91 91        0 Apr  6 18:42 session.log
support@support-app-02:~$ 

Additional Resources 

• Success Programs
• Success Catalog
• Datasheets
• Request a Solution Offering or Training from the Success Catalog

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.