Skip to main content
Version: 2.8

Troubleshooting D1 and Conversion Service errors

This page lists the most common D1 and Conversion Service errors that you might encounter, and provides instructions how to troubleshoot them.

Shutdown aborted - missing CATALINA_PID​

You might run into the following error on attempt to shut down D1 or Conversion Service:

./tribefire-console-start.sh
/installation_dir/runtime/host/bin/catalina.pid was set but the specified file does not exist. Is Tomcat running? Stop aborted.

This error is caused by using ./catalina.sh run instead of ./tribefire-console-start.sh for starting the service. To avoid this error, use ./tribefire-console-start.sh to start D1 or Conversion Service and ./tribefire-console-stop.sh to shut it down. For details, see Starting and stopping D1 and Conversion Service.

D1 or Conversion Service suddenly shuts down​

If D1 or Conversion Service suddenly shuts down, in most of the cases, it is caused by an out-of-memory issue.

Perform the following steps to troubleshoot this problem:

  • Check the logs for the java.lang.OutOfMemoryError error. Most likely, you will find it in the catalina.out.
info

You can check logs in a text editor, or in the command line. If you review the logs in the command line, you can use grep filter to search for the problem more easy.

Sessions ending on a host shared between D1 and Conversion Service​

Session cookies are domain-bound in D1 and Conversion Service installations. As a result, when Conversion Service and D1 are running on the same host, it is impossible to log in to both nodes at the same time.

Deployment type specific problem

This problem is typical for development environments, and it should not normally occur in the production environments (see recommended architecture for production).

Consider the following situation:

  • D1 is running on localhost:8080
  • Conversion Service is running on localhost:9090

The D1 session ends when the Conversion Service session starts (and the other way around).

You can solve the problem by resolving your localhost IP to a different domain. To do this, open the etc/hosts file and add the following lines (assuming your localhost IP is 127.0.0.1):

127.0.0.1 adx-alias
127.0.0.1 conversion-alias

You should now be able to access D1 on adx-alias:8080 and Conversion Service on conversion-alias:9080. Getting logged in one node should no longer cause the session on the other node to end, because from the browser perspective D1 and Conversion Service are now on different hosts.

One or more Tribefire listeners failed to start​

If you are not able to access Tribefire services on Conversion Service node or the landing page on the D1 node, check the logs for the following items:

SEVERE  StandardContext                   'One or more listeners failed to start. Full details will be found in the appropriate container log file'  []
SEVERE  StandardContext                   'Context [/tribefire-services] startup failed due to previous errors'  []

To troubleshoot this error, check if the correct database driver is placed in the additional-libraries folder (which should be in the same location as your installation directory), as described in the System Database configuration in the installation instructions.