Skip to main content
Sign in

Proxy service fails to start due to trustStorePassword misconfiguration

  • Updated

Issue

The Fusion proxy service fails to start when running ./proxy start, displaying an error similar to:

Error starting proxy: proxy service (pid 5408) failed

This may occur after restarting Fusion or attempting to start the proxy service individually on Fusion 4.x environments. The failure may persist even after stopping and restarting all Fusion services.

 

Environment

  • Fusion 4.2.x 
  • Windows, Linux (note: commands and paths may vary from Linux environments)
  • Affects legacy Fusion deployments using non-containerized start/stop scripts

 

Symptoms

  • ./proxy start fails with a proxy service (pid XXXX) failed message
  • Starting all services via ./fusion start does not resolve the proxy startup issue
  • Logs show other Fusion components starting correctly (e.g., Solr, API, Spark)
  • Error message appears repeatedly for the proxy service on each restart attempt
  • Reviewing logs reveals trust store related exceptions

 

Resolution

This issue can be caused by a misconfigured or incorrect trustStorePassword in the Fusion configuration. To resolve the issue:

1. Stop all Fusion services

Use the Fusion stop script to stop all services:

./fusion stop

If applicable, ensure that ingestion services and ZooKeeper are also stopped on each machine.

On Windows, verify that all Java processes have terminated using Task Manager, or by running:

tasklist | findstr java

2. Review the proxy logs

Locate and open the proxy.log file in the Fusion logs directory. Look for any exceptions referencing trustStore, SSL, or password-related issues. For example:

java.io.IOException: Keystore was tampered with, or password was incorrect

This indicates an invalid trustStorePassword is being used.

3. Update the trustStorePassword

Edit the relevant configuration file (usually start.ini, depending on deployment) and ensure the correct trustStorePassword is provided.

Common configuration file to check:

  • $FUSION_HOME/apps/jetty/proxy/start.ini

Ensure that the following properties are valid and match the key-store contents:

trustStorePassword=<correct_password>
keyStorePassword=<correct_password> 

If encrypted, confirm that Fusion’s decryption is properly configured and the secret key is accessible.

4. Restart all services

After making the configuration changes, restart all Fusion components:

./fusion start

Then verify the status:

./fusion status

The proxy service should now start successfully.

 

Additional information

  • Attempting to start the proxy individually (./proxy start) may fail if other dependencies or trust settings are not fully initialized.
  • The Jetty-based proxy in Fusion 4 requires valid and readable SSL keystore/truststore credentials; misconfigurations commonly result in silent startup failures.
  • Ensure both Fusion and ZooKeeper are fully stopped before restarting services to avoid conflicts.
 
Powered by Zendesk