SPS service fails to start

Products

• CA Single Sign On Secure Proxy Server (SiteMinder)
• CA Single Sign On SOA Security Manager (SiteMinder)
• CA Single Sign-On

Issue/Introduction

The 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 /opt/CA/secure-proxy/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: '/opt/CA/secure-proxy/httpd/bin/httpd -d /opt/CA/secure-proxy/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 

Environment

OS: Linux Red Hat 7.0 Environment: Development

Cause

The java / proxy-engine part was not shutdown correctly.

Resolution

To address this issue you need to delete the proxy-engine/tmp/sps.pid file and the process then started up correctly. 

 

If the java / proxy-engine part is not shutdown correctly the file can be left behind.   kill -9 for example does not give the process time to delete the pid file. 

 

 

Additional Information

Later versions of SPS should not encounter this problem as there are process checks in place.