sps.service: Failed with result 'timeout' with CA Access Gateway (SPS)

Products

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

Issue/Introduction

 

Starting CA Access Gateway (SPS) with the command

  # systemctl status sps

then, the systemctl command reports the error:

  Active: failed (Result: timeout) since Tue 2024-08-06 11:43:09 CEST; 2 weeks 0 days ago

  Aug 06 11:38:11 server.example.com systemd[1]: sps.service: New main PID 44012 does not belong to s>
  Aug 06 11:38:11 server.example.com su[43431]: pam_unix(su:session): session closed for user <name>
  Aug 06 11:43:09 server.example.com systemd[1]: sps.service: start operation timed out. Terminating.
  Aug 06 11:43:09 server.example.com systemd[1]: sps.service: Failed with result 'timeout'.
  Aug 06 11:43:09 server.example.com systemd[1]: Failed to start LSB: start and stop CA Secure Proxy.

 

Resolution

The out of the box CA Access Gateway (SPS) doesn't provide a script for SysV nor Systemd.

To integrate CA Access Gateway (SPS) with fully RedHat systemd, open an Enhancement Request (Idea) (1).

One way to make it work with Systemd, edit the file /{home_sps}/proxy-engine/sps-ctl and change the line

[SU_CMD="su $RUN_AS_USER -s /bin/sh]

with

[SU_CMD="runuser $RUN_AS_USER -s /bin/sh]

That will make the systemctl to not report an error anymore.

 

Additional Information

 

1. Creating an Idea/Enhancement Request for SiteMinder