Service fails to start in CA Access Gateway (SPS)

Products

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

Issue/Introduction

The CA Access Gateway (SPS) service does not start and the following log entries are recorded:

[Wed May 10 16:16:03.513227 2017] [jk:warn] [pid 3458:tid 4151666432] No JkShmFile defined in httpd.conf. Using default /{home_sps}/httpd/logs/jk-runtime-status
[Wed May 10 16:16:03.513974 2017] [mpm_worker:notice] [pid 3458:tid 4151666432] AH00292: Apache/2.4.12 (Unix) mod_jk/1.2.40 configured -- resuming normal operations
[Wed May 10 16:16:03.513988 2017] [core:notice] [pid 3458:tid 4151666432] AH00094: Command line: '/{home_sps}/httpd/bin/httpd -d /{home_sps}/httpd'
[Wed May 10 16:16:03.514004 2017] [mpm_worker:warn] [pid 3458:tid 4151666432] AH00291: long lost child came home! (pid 4306)
[Wed May 10 16:16:03.514014 2017] [mpm_worker:warn] [pid 3458:tid 4151666432] AH00291: long lost child came home! (pid 4307)
[Wed May 10 16:19:56.030438 2017] [mpm_worker:notice] [pid 3458:tid 4151666432] AH00295: caught SIGTERM, shutting down 

 

Cause

The java and proxy-engine part was not shut down correctly.

To illustrate, the use of the command "kill -9" does not give the process time to delete the PID file.

 

Resolution

To address this issue, delete the /{home_sps} /proxy-engine/tmp/sps.pid file, and the process then started up correctly. 

If the java or proxy-engine part is not shutdown correctly, the file can be left behind.