Troubleshooting
Problem
When you run stopEngine.sh, it does not shut down the Engine in Sterling Secure Proxy.
Symptom
bin> ./stopEngine.sh
Enter the passphrase for the Engine:
***Could not connect to Engine. Either Engine is not running or the Engine connection parameters are incorrect
Cause
When the stopEngine script is executed, and no host= was specified, the code gets the local hostname and tries to resolve that to the IP address.
If the firewall configuration blocks the hostname resolution, this could cause the problem. One example would be if the IP address is natted.
Resolving The Problem
Specify host=<natted IP address> with the stopEngine.sh command.
For example, if the natted ip address is 1.1.1.1, then enter:
./stopEngine.sh host=1.1.1.1
Was this topic helpful?
Document Information
Modified date:
13 October 2021
UID
swg21991282