Auto Startup Script has been configured according to the documentation.
When manually starting up policy server via command-line (start-all) the policy server starts up just fine.
But when the machine is rebooted, policy server starts but is then killed so policy server need to be started up manually.
"/var/log/messages" reports the following.
Feb 11 15:38:31 smps-02 systemd: Starting S98sm Service... |
"systemctl status S98sm" reports the following.
[[email protected] log]# systemctl status S98sm |
This is because the default Startup Timeout is 90 seconds.
If the service does not start within 90 seconds to return a success result then it will be killed and considered failed start.
Release : 12.8.x
Component : SITEMINDER POLICY SERVER
You can increase the StartupTimeout in the "/etc/systemd/system/S98sm.service"
Following sample shows the TimeoutStartSec being set to 3000 seconds. You may need to test to come up with sufficient value.
"infinity" is also a valid option but should rather investigate why the startup would take so long.
[Unit] |
If the TimeoutStartSec value is sufficient, then the following should be observed.
"/var/log/messages" reports the following.
Feb 11 15:42:02 smps-02 systemd: Starting S98sm Service... |
"systemctl status S98sm" reports the following.
[[email protected] log]# systemctl status S98sm |
More detail on TimeoutStartSec: https://bugzilla.redhat.com/show_bug.cgi?id=1446015