Layer 7 Access Management

Tech Tip : CA Single Sign-On : Siteminder Startup Script and Cores not working

  • 1.  Tech Tip : CA Single Sign-On : Siteminder Startup Script and Cores not working

    Posted 12-04-2018 05:04 AM

    Issue:


    When we reboot the Policy Server machine, the Policy Server cannot
    start properly. We don't see it in memory.

     

    We've configured the start script as :

     

    /etc/init.d/sm/S98sm

    this file is symbolic link to rc5.d folder.

     

    S98sm

     

    # this script starts and stops the siteminder policy server
    # at boot time
    # start

    case "$1" in

    'start')

    su - smuser -c /opt/CA/siteminder/start-all &

    ;;

    'stop')

    su - smuser -c /opt/CA/siteminder/stop-all &

    ;;

    esac

     

    Cause:

     

    Out of the box, OpenRC needs the script within /etc/init.d and doesn't

    expect any subfolder.

     

    Understanding the rc Scripts in Linux

    /etc/init.d/

     

    To avoid script duplication, the files in the rc#.d/ 

    directories are actually symbolic links to script files located in the
    /etc/init.d/ directory. Every service installed on the system installs
    a script in this directory which can be used to control that
    service. These scripts are written to take start options specifying
    that they should start the service, and stop options specifying that
    they should stop the service.

     

    https://www.thegeekdiary.com/understanding-the-rc-scripts-in-linux/

     

    Resolution:

     

    Putting the S98sm in /etc/init.d/ folder and making a symlink
    /etc/rc3.d/S98sm to /etc/init.d/S98sm solved the issue.

     

    KB : KB000122258