Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 3.18.1
-
Fix Version/s: 3.37.0
-
Component/s: Docker, Support Tools
-
Labels:
-
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
- is related to
-
NEXUS-19527 a docker connector port already in use prevents startup of repository manager
-
- Closed
-
- mentioned in
-
Page Loading...