Provisioning Server service crash and down core dump slapd

Products

• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• CA Identity Suite

Issue/Introduction

im_ps crashes and generate a core.<pid> under folder /opt/CA/IdentityManager/ProvisioningServer/bin for first attempting of bind on im_ps.

Environment

CA Identity Suite 14.x Virtual Appliance
Also works on non-vapp *unix builds. 

Resolution

1. Login as config user and su - imps user

2. cd to ProvisioningServer/bin folder and run:

$>gdb ./slapd ./core.1234 -ex 'thread apply all bt full' -ex quit |& tee backtrace.log (where core.<pid> is the core file generated when im_ps crashed and generated the core file)

3.  Open the resulting backtrace.log and review for the message:
Core was generated by `./slapd -n im_ps -s 64 -f ../data/im_ps.conf -h ldap://localhost:20389 ldap://c'. Program terminated with signal 11, Segmentation fault. #0 0x0079b69f in _LoadSAPIFuncs () at /home/etadev/src/ECS2/ECS/CommonServices/Unix/Logging/eCSLogAPI.cpp:2875 2875 /home/etadev/src/ECS2/ECS/CommonServices/Unix/Logging/eCSLogAPI.cpp: No such file or directory. in /home/etadev/src/ECS2/ECS/CommonServices/Unix/Logging/eCSLogAPI.cpp

4.  Make the following adjustment to clear this error;  go to Provisioning Manager/System/Global Properties/Logging tab and uncheck "Common Services", "Unicenter Console" and "eTrust Audit" tabs.

5.  Generate the backtrace again as described in step 2.