DSAs do not start and are reported in an inconsistent state
search cancel

DSAs do not start and are reported in an inconsistent state

book

Article ID: 39811

calendar_today

Updated On: 04-23-2025

Products

CA Directory CA Identity Manager CA Identity Portal CA Identity Suite

Issue/Introduction

One or more DSAs does not start and reports 'inconsistent,' or 'Error 13: The data is invalid'.

e.g.

<hostname>-impd-co inconsistent
<hostname>-impd-inc inconsistent
<hostname>-impd-main inconsistent
<hostname>-impd-notify inconsistent

 

Resolution

There may be PID files left over from a previous start which should have been deleted by the software if a graceful stop of DSA was made. If not, the files may still exist which caused the DSA failure to start with 'inconsistent' state.

Try running the start with 'forcestart' option which is designed to check for existing PID files, delete them and attempts to start the DSA.

i.e. dxserver forcestart <dsaname>

NOTE: This 'forcestart' option does not work with 'all' option (e.g. dxserver forcestart all). Individual DSA name has to be provided.