Uploaded image for project: 'OpenDJ'
  1. OpenDJ
  2. OPENDJ-7369

Calling dsconfig offline after setup without ever starting the server creates a server.lock

    Details

    • Type: Bug
    • Status: Done
    • Priority: Major
    • Resolution: Not a defect
    • Affects Version/s: 7.0.0
    • Fix Version/s: 7.0.0
    • Component/s: tools
    • Labels:
      None

      Description

      Found with M2020-10.1.

      We setup a server without starting it:

      /tmp/toto/opendj/setup -h openam.example.com -p 1394 -D "cn=myself" -w password --adminConnectorPort 4449 -Z 1641 --profile ds-user-data  --set ds-user-data/baseDn:dc=com --set ds-user-data/addBaseEntry:false   --acceptLicense --monitorUserDn uid=Monitor --monitorUserPassword password --deploymentKey AI1QLGYmsSzDRjKDmQZu7l9sAD10aA5CBVN1bkVDC24LTccCYcFwGw --deploymentKeyPassword keypassword --replicationPort 8994
      

      Then we list backends for checking, in offline mode:

      /tmp/toto/opendj/bin/dsconfig --offline list-backends --script-friendly -n
      adminRoot
      monitorUser
      rootUser
      userData
      
       ~/wks/pyforge (fix_full_encrypted $)$ find /tmp/toto -name '*lock*'
      /tmp/toto/opendj/locks
      /tmp/toto/opendj/locks/server.lock
      ...
      

      Not sure why this server.lock persists but it does not prevent the server from being started or any other operation.

        Attachments

          Activity

            People

            • Assignee:
              ludo Ludovic Poitou
              Reporter:
              cforel carole forel
              Dev Assignee:
              Ludovic Poitou
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: