When ENDPOINT_PORT is changed to value 6003, NooBaa services are continuously restarting with address in use PANIC.
Testcase is working well with different port. So suspecting that internally NooBaa is using 6003 for some other health fork and that might cause issue during NooBaa service startup.

logs- 
Jul 28 10:49:38 newbuild-21 node[978767]: PANIC: process uncaughtExceptionError: bind EADDRINUSE null:6003 Jul 28 10:49:38 newbuild-21 node[978767]: at listenOnPrimaryHandle (node:net:1988:18) Jul 28 10:49:38 newbuild-21 node[978767]: at rr (node:internal/cluster/child:163:12) Jul 28 10:49:38 newbuild-21 node[978767]: at Worker.<anonymous> (node:internal/cluster/child:113:7) Jul 28 10:49:38 newbuild-21 node[978767]: at process.onInternalMessage (node:internal/cluster/utils:49:5) Jul 28 10:49:38 newbuild-21 node[978767]: at process.emit (node:events:530:35) Jul 28 10:49:38 newbuild-21 node[978767]: at process.emit (node:domain:489:12) Jul 28 10:49:38 newbuild-21 node[978767]: at emit (node:internal/child_process:950:14) Jul 28 10:49:38 newbuild-21 node[978767]: at process.processTicksAndRejections (node:internal/process/task_queues:91:21)