Hi Girish,
To understand what cause the Policy Server restart, you do need to
note the PID and the time when the Policy Server crashes, by looking
in the smexec.log if Policy Server runs on Linux, or in the event log
if it runs on Windows.
Once you know that, analyse the smps.log along with the
smtracedefault.log to find the same PID and point out the Thread which
is in middle of a transaction with the tracing stopped.
Then, recreate the issue running Debug Diag if Policy Server runs on
Windows, or enable core dump on Linux if the Policy Server runs on
Linux.
Once the crash has been recreated, if the problem is really a crash,
then analyse the Debug Diag file or run pkgcore script against the
coredump on Linux to understand the reason why the Policy Server
crash.
Which Policy Server version do you run ?
Best Regards,
Patrick
Original Message:
Sent: 11-26-2020 11:55 PM
From: Girish Chandra
Subject: Policy server restarting automatically
Hello Community,
In our prod environment two policy servers are configured with failover mode. In that primary policy server restarting automatically within few seconds, no information in smps logs.
This happened two times with 10days time period. We are using CA directory for user store and policy store. we have only 5k users in user store, and we haven't did any update in Siteminder.
Please help me to understand what causes for this.
Regards,
Girish Chandra