Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-21878

failing to start one docker connector on startup prevents all other not started docker connectors from starting

    XMLWordPrintable

    Details

    • Release Note:
      Yes
    • Notability:
      3

      Description

      Configure (at least 3 for ease of reproduce) Docker repos with connector ports. All should be running and started after each repo is added.

      Stop NXRM.

      Start another process on the same host listening on one of the docker connector ports.

      Start NXRM. The port that is in use by another process will prevent start of the docker repo connector using the same port. Any docker connector which has not yet been started before that failure will not be attempted to start during NXRM startup after that failure.

      Expected

      Attempt to start each and every Docker connector on NXRM startup. If any one fails to start, that should not prevent NXRM from trying to start all others, which may succeed.

      Add a system status check that makes sure all docker connectors are started?

      Workaround

      Identify a Docker repo that is configured with a connector, but is not running. Make a small change to its settings such as changing the Not Found Cache TTL by one number. Save the settings change. On Save the docker connector will attempt to start on the port it is configured with.

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dbradicich Damian Bradicich
              Reporter:
              plynch Peter Lynch
              Last Updated By:
              Lisa Durant Lisa Durant
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title