To investigate issue within Qlik Catalog, the support engineer will need a few log files to deduce the root cause. In this article we will instruct you on where to find them.
First a few variables:
QDC_HOME: Home Directory where qdc is housed on the local server, this is set during installation through the Pre-requisite script within the QDCinstaller. The default is: usr/local/qdc
Tomcat: Apache Tomcat directory. Directory name will differ based on Tomcat version.
Environment
Core_env.properties
- Log into your Qlik Catalog Server Terminal
- Navigate to QDC_HOME/<Tomcat>/conf
- The core_env.properties will be in this directory and can then be added to the ticket
Catalina.out
- Log into your Qlik Catalog Server Terminal
- Navigate to QDC_HOME/<Tomcat>/logs
- The catalina.out will be in this directory and it should be zipped up and added to the ticket
Container logs
Centos Installation: Docker
- Log into your Qlik Catalog Server Terminal
- Navigate to QDC_HOME/qlikcore
- Run docker ps
- Identify the container ID for the licenses container
- Run docker logs -f [container ID]
- Recreate the behavior that caused the error
- Attach the output to a .txt file and upload it to the case
Red Hat Installation: Podman
- Log into your Qlik Catalog Server Terminal
- Navigate to QDC_HOME/qlikcore
- Run podman ps
- Identify the container ID for the licenses container
- Run podman logs -f [container ID]
- Recreate the behavior that caused the error
- Attach the output to a .txt file and upload it to the case