DSA status comes back as 'does not exist'

Document ID:  TEC1003658
Last Modified Date:  08/11/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Directory

Releases

  • CA Directory:Release:12.0
  • CA Directory:Release:12.5
  • CA Directory:Release:12.6

Components

  • CA Directory:ETRDIR
  • IdentityMinder(Identity Manager):IDMGR
Question:

You may come across a situation where when you run 'dxserver status' command line tool to check status on your DSAs and all or some of them report back as "does not exist". You already confirmed that all necessary config files exist so it should exist.

Answer:

There is a high possibility that somehow the actual 'dxserver' process attached to this {dsaname} has disappeared. e.g. crashed, got killed with 'kill -9' command accidentally etc.

 

When this happens, chances are, it left behind PID file under $DXHOME/pid folder for this DSA in question. This PID is not an actual number but rather reflects the {dsaname}.

 

In order to address this:

 

* Manually delete the PID name associated with the {dsaname} that shows up as "does not exist" in 'dxserver status' output.

* Re-run 'dxsevrer status' and it should be reported as 'stopped'.

* Restart those DSAs for which you deleted the PID files and re-run 'dxserver status' to confirm those report back as 'started'.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >