search cancel

After installing APM for SSO Policy Server agent - xpsconfig changes result in SSO failing to start.


Article ID: 8660


Updated On:


CA Application Performance Management Agent (APM / Wily / Introscope) INTROSCOPE


After installing the APM for SSO Policy Server agent, the instructions have you run xpsconfig, and then add to SMAuditHandlers the entry 

On starting the Policy Server, it then fails to start - seemingly hanging at a certain point over and over again.

Rerunning xpsconfig results in a large memory map, starting with an entry similar to:

libIntroscopeNativeDataAPI was loaded from /disk/apps/policyserver/siteminder/lib
*** glibc detected *** XPSConfig: corrupted double-linked list: 0x00000000020fdcd0 ***


  APM for SSO 13.1 on Linux Policy Server


 This is caused by an invalid entry for the environmental variable  INTROSCOPE_NATIVEDATAAPI_LOGPATH - OR - that the referenced folder path does not exist / is not accessible.


 To resolve the problem:

1. Verify that the environmental variable "INTROSCOPE_NATIVEDATAAPI_LOGPATH" is set (in the same session) as you are running the policy server software.

2. If this is set, then check that the folder specified exists (it will not be created by the agent), and that it is accessible by the Policy Server and Agent Processes.

3. If the path is set as /logs/ca/apm_13.1/, make sure there is a '/' at the end of the path, otherwise the Policy Server will fail to start.