Identity Manager : Installing Provisioning Directory fails with core dump
search cancel

Identity Manager : Installing Provisioning Directory fails with core dump


Article ID: 272832


Updated On:


CA Identity Suite


Attempting to install IDM Provisioning Directory component, after successfully installing Symantec Directory on a Linux host, reuslts in to failure to install and the installer core dumps reporting something similar to what you see below.

OpenJDK Server VM warning: You have loaded library /your/path/1801264.tmp which might have disabled stack guard. The VM will try to fix the stack guard now.
It's highly recommended that you fix the library with 'execstack -c <libfile>', or link it with '-z noexecstack'.
# A fatal error has been detected by the Java Runtime Environment:
#  SIGSEGV (0xb) at pc=0xf7d95837, pid=2941430, tid=2878008128
# JRE version: OpenJDK Runtime Environment (7.0-b32) (build 1.7.0-u80-unofficial-b32)
# Java VM: OpenJDK Server VM (24.80-b11 mixed mode linux-x86 )
# Problematic frame:
# C  []  strlen+0x37
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
# An error report file with more information is saved as:
# /your/path/hs_err_pid2941430.log
# If you would like to submit a bug report, please visit:


Release : 14.4


Problem could be related to having your own installation owner/user defined while you do not want to use the default 'dsa' user for Symantec Directory.

Please check the /etc/passwd and /etc/group files to make sure the user is define only once along with the fact that it has '*' instead of 'x' in the definition.


/etc/passwd -> myuser:x:20136:3026:DXserver Administrator:/my/path/CA/Directory/dxserver:/bin/bash
/etc/group ->  etrdir:*:3026:myuser,myuser1,myuser2


/etc/passwd -> myuser:*:20136:3026:DXserver Administrator:/my/path/CA/Directory/dxserver:/bin/bash
/etc/group ->  etrdir:*:3026:myuser,myuser1,myuser2

Also the fact that having it defined multiple times can cause the installer to get confused and cause a problem.

In short, having just defined once and with "myuser:*:..." instead of "myuser:x:..." should resolve the issue.