IBM Support

stopEngine.sh does not shut down the Engine

Technical Blog Post


Abstract

stopEngine.sh does not shut down the Engine

Body

stopEngine.sh does not shut down the Engine

 

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
 

 

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.

In this case the user should specify host=<natted IP address>.  For example, if the natted ip address is 1.1.1.1, then they should enter:

./stopEngine.sh host=1.1.1.1
 

stopEngine.sh does not shut down the Engine

 

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS4PJT","label":"IBM Sterling Connect:Direct"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

UID

ibm11123599

Page Feedback