Installation Issues

Common Issues

Corrupt Binary

gunzip: sfx_archive.tar.gz: not in gzip format

If you see this error, something went wrong during the transfer process of the installer. The easiest way to confirm this is to calculate the MD5 of the installer you're attempting to run, and compare it to the MD5 hash listed on our Hub site. Most likely this occurred if the file was transferred in ASCII mode instead of binary mode, particularly if SCP/SFTP was used.


To resolve the issue, transfer the file again, and explicitly specifying binary mode.

Failed Migration Due to Access Restrictions

Error on rename ... (Errcode: 13)

If you see this error, a migration failed during Contrast startup. The failure was most likely caused by the current user having insufficient privileges to modify files in the directory in which Contrast was installed.


To resolve the issue, uninstall Contrast and delete the remaining data files. You can then either elevate the user's permissions in the installation directory or choose a new directory where the user has full privileges. While it's uncommon, Administrator users can encounter this problem if there are extra file restrictions put in place by your organization.

Superadmin Configuration Unaccessible in 3.1.3

There is a known bug in Contrast EOP 3.1.3 that makes the Superadmin configuration interface inaccessible.


To resolve this issue, you must create an empty file in the filesystem at $CONTRAST_HOME/data/conf/

Multiple contrast-server JARs

There is a known issue in contrast 3.1.1 - 3.1.3 where the contrast-server binary isn't replaced during the upgrade process. This could cause classloading issues in the server which cause functionality to become unpredictable.


To resolve this issue, remove the older JARs from the $CONTRAST_HOME/lib directory that start with contrast-server-3.1. There should only be a single contrast-server version in that directory. After removing the files, restart Contrast.

Database Backup Gives Error

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)

In some fresh vanilla installations of Redhat or CentOS, the server could have an unresolvable hostname. During the installation process, Contrast detects the hostname for the server to set configuration parameters for how to connect to the database.

Example: A default CentOS 5.6 installation sets its hostname to centos.localdomain, but a corresponding entry isn't added to the /etc/hosts file.

If the hostname is unresolvable, the system defaults to localhost, which works for other areas of the system. However, the automated backup uses the mysqldump tool that associates the localhost hostname with a file socket connection instead of a network socket connection.


To resolve this error, set the database hostname to either a resolvable hostname or the IP address assigned to the server. This can be done using the encrypted properties editor tool that ships with the product.

$ bin/edit-properties -e data/esapi -f data/conf/

Once you're in the properties editor, type the name of the property that you would like to change. In this case, you want to update the value of the to the new hostname or IP address assigned to the server. Once you update this value, hit Q to quit out of the tool, select Y to save, then enter a comment for your change. You can verify the backup functions by running the $CONTRAST_HOME/bin/ script manually (as the contrast_service user, or whatever user you designated during installation).

sudo -u contrast_service /opt/Contrast/bin/
Reading Database Configuration
Ensuring Database Connectivity: Up
Backing up Schema: contrast to /opt/Contrast/data/backups/db/contrast.20150223.sql

Service Won't Start Due to Missing sudo/su

The sudo and/or su commands might not be available on some flavors of Linux. However, this is a simple issue to resolve.

For example, the runuser command is the default on the default installation of Amazon Linux within AWS, but it isn't an option during the installation. While Contrast makes an effort to support as many environments as possible with our Enterprise On-Premises (EOP) product, it's impossible to predict every potential scenario and test it internally.


You can resolve this issue by either installing sudo or su on your target server. If that's not an option, you can edit the $CONTRAST_HOME/bin/contrast-server.initd script directly and update it to reflect your environment.

Can't Find Your Problem?

If you have an issue that these answers don't solve, submit a ticket to the Support team with a description of the issue, the steps that caused it to occur, and any logs or screenshots that you have. The team will address your issue as soon as possible.

The ActiveMQ Disk is Full

If you're seeing errors in your log file related to a queue, it's likely that the storage of your ActiveMQ database is causing the problem. You might observe any of the following in your contrast.log file:

  • "Failed to page in more queue" messages
  • queue://
  • A link to
  • Any reference to ActiveMQ with ERROR log level
  • "Failed to page in more queue messages" java.lang.NegativeArraySizeException thrown by
  • "Failed to fill batch" caused by NegativeArraySizeException.
  • "Problem retrieving message for browse" thrown by

When the disk first fills up, you might start to see error messages in contrast.log every 30 seconds. Example error message:

Main:store:queue://queue/ ... percentUsage=102% ... Persistent store is Full, 100% of SOME#. Stopping producer

At this point, you should check to see why Contrast thinks that your disk is full. It's likely that ActiveMQ surpassed its allotted storage; but, in some cases, your disk could be full.

Before clearing any files, stop the Contrast process, and then begin the process of clearing out unnecessary files. If you see these ActiveMQ errors, you can resolve this in just a few steps:

  • Confirm the Contrast isn't running.
  • Navigate to $CONTRAST_HOME/data/activemq.
  • Delete everything in this folder (both the data and index folders).
  • Start Contrast.

Base_Directory Error When Starting Contrast

If you receive an error that BASE_DIRECTORY must be set when you try to start Contrast, it's an indication that you have a CATALINA_HOME directory already set in your system environment. Some products that use Tomcat require you to set this directory in the environment; but, unfortunately, it steps on our startup scripts.

The simplest way to resolve this error is to edit the CONTRAST_HOME/server/bin/ file, and set the CATALINA_HOME to Contrast's Tomcat directory by adding:

# Address hard-coded environment variable for CATALINA_HOME - Set this directory to your 
# $CONTRAST_HOME/server directory
set CATALINA_HOME=/opt/contrast/server

New Native Thread Error

If you're seeing an error in your /opt/Contrast/contrast-error.log that's similar to the example below, you might be bumping up against the thread limit set by your operating system.

SEVERE: Servlet.service() for servlet [spring] in context with path [/Contrast] threw exception 
[Request processing failed; nested exception is java.util.concurrent.ExecutionException: 
java.lang.OutOfMemoryError: unable to create new native thread] with root cause
java.lang.OutOfMemoryError: unable to create new native thread
 at java.lang.Thread.start0(Native Method)
 at java.lang.Thread.start(

To address this issue, increase the number of threads that the Contrast user can start in your /etc/security/limits.d/90-nproc.conf file.

Note: To modify a system configuration file, you must have root access or the ability to sudo. Consult your System Administrator for additional details.

You can add the line <contrast-username> soft nproc unlimited to the end of the file and restart the contrast-server using the command sudo service contrast-server restart.