Why does my DXadmind not start on Windows?

book

Article ID: 52532

calendar_today

Updated On:

Products

DIRECTORY SINGLE SIGN ON - LEGACY CA Data Protection (DataMinder) CA User Activity Reporting

Issue/Introduction

Description

DXadmind may not start because port 2123 may be in use by another process. The following procedure describes how to debug this issue and provides instructions to change the port if necessary.

Solution

You may find that after the Directory install your dxadmind fails to start.

  1. To find out the status of dxadmind run the following command
    C:\dxadmind status
    dxadmind is stopped

  2. To start dxadmind you need to run the following command
    C:\>dxadmind start
    Starting dxadmind....
    dxadmind failed to start!

  3. Since your dxadmind is not starting you can run the following command to start in debug mode
    C:\>dxadmind debug
    Matching host in XML not found
    0 hosts found in XML config

  4. Once you have finished running the above command all the debug logging will be logged in the %DXHOME%/logs/dxadmind.log

  5. If the dxadmind.log contains the following information which is highlighted in bold, it means that dxadmind was not able to bind to port 2123.

    Matching host in XML not found
    0 hosts found in XML config
    daemon_init: ldaps://155.XX.XXX.XXX:2123 ldaps://127.0.0.1:2123
    daemon_init: ldaps://155.XX.XXX.XXX:2123 ldaps://127.0.0.1:2123
    daemon_init: listen on ldaps://155.XX.XXX.XXX:2123
    daemon_init: listen on ldaps://155.XX.XXX.XXX:2123
    daemon_init: listen on ldaps://127.0.0.1:2123
    daemon_init: listen on ldaps://127.0.0.1:2123
    daemon_init: 2 listeners to open...
    daemon_init: 2 listeners to open...
    daemon: bind(1652) failed errno=10013 (WSAEACCES)
    daemon: bind(1652) failed errno=10013 (WSAEACCES)
    slap_open_listener: failed on ldaps://155.XX.XXX.XXX:2123
    slap_open_listener: failed on ldaps://155.XX.XXX.XXX:2123

    dxadmind stopped.
    dxadmind stopped.
    connections_destroy: nothing to destroy.
    connections_destroy: nothing to destroy.
    No error

  6. To confirm that some other process is using the port 2123, you could use the "netstat -b" command or some other third party tool.

  7. Once you have found out which process was using port 2123 you can do one of the following

    1. Rename %DXHOME%/config/dsaconfig.xml file to dsaconfig.xml.old

    2. Run command "dxadmind setup <hostname> <port> <password>"

      Eg. dxadmind setup WinXp 3123 mypassword

    3. Start dxadmind

      % dxadmind start

Environment

Release:
Component: ETRDIR