"Unable to stop the CA Access Gateway Engine" running sps-ctl stop

Products

• SITEMINDER
• CA Single Sign On Secure Proxy Server (SiteMinder)

Issue/Introduction

When running a CA Access Gateway (SPS), trying to stop it, the command line returns an error:

  # ./sps-ctl stop
  httpd (no pid file) not running
  CA Access Gateway Proxy has been successfully stopped..
  Attempting to stop CA Access Gateway Engine..
  Sending stop message to server...
  Cannot stop Proxy Engine
  java.net.ConnectException: Connection refused (Connection refused)
          at java.net.PlainSocketImpl.socketConnect(Native Method)

  [...omitted for brevity...]

  Unable to stop the CA Access Gateway Engine..
  CA Access Gateway Engine may not be initialized or may not be running.
  Consult CA Access Gateway Engine logs for details.        

 

Resolution

When the account that runs the CA Access Gateway (SPS) differs from the one that tries to stop it, this issue might occur.

If the embedded Tomcat server is in an undetermined state, this can happen too.

To investigate further what is causing this problem, run the following commands:

• On the CA Access Gateway (SPS) machine, as root, run the command:
  
  # ps auxww | grep -i Tomcat
  
  and check if the Tomcat is in memory and if the state is not Zombie (Z);
  
  
• On the CA Access Gateway (SPS) machine, as root, run the command:
  
  # ls -Rltrha / > ls.txt
  
  And check from the ls.txt file, examine the owner set for the CA Access Gateway (SPS) installed files. The owner should be the one running the CA Access Gateway (SPS) as seen from the ps command above.
• Checking the following log files might help to get further indication about the problem:
  
  server.conf;
  server.log;
  nohup*.log;
  access_log;
  error_log;