Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

DC/OS package doesn't start with a network error (connection refused)

See original GitHub issue

Describe the bug Package available on DC/OS Catalog doesn’t start with a network error (connection refused to internal address during startup).

To Reproduce Steps to reproduce the behavior:

Go to ‘Catalog’ and install "predator’ package
Select appropriate backend (SQLITE doesn’t seem to work, I used MySQL and it is OK)
Look at logs during startup of container

Expected behavior Predator service starts automatically and I’m able connect to Web UI

Logs {"level":30,"time":1603874944320,"pid":1,"hostname":"coll-dcos9","name":"predator","msg":"Predator listening on port 1884"} {"level":30,"time":1603874944323,"pid":1,"hostname":"coll-dcos9","name":"predator","msg":"Checking http://predator.marathon.l4lb.thisdcos.directory:80/config to verify predator-runners will be able connect to Predator"} {"level":50,"time":1603874945398,"pid":1,"hostname":"coll-dcos9","name":"predator","name":"RequestError","message":"Error: connect ECONNREFUSED 11.31.104.67:80","cause":{"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"11.31.104.67","port":80},"error":{"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"11.31.104.67","port":80},"options":{"json":true,"simple":false,"resolveWithFullResponse":true,"timeout":5000,"uri":"http://predator.marathon.l4lb.thisdcos.directory:80/config","method":"GET","transform2xxOnly":false},"stack":"RequestError: Error: connect ECONNREFUSED 11.31.104.67:80\n at new RequestError (/usr/node_modules/request-promise-core/lib/errors.js:14:15)\n at Request.plumbing.callback (/usr/node_modules/request-promise-core/lib/plumbing.js:87:29)\n at Request.RP$callback [as _callback] (/usr/node_modules/request-promise-core/lib/plumbing.js:46:31)\n at self.callback (/usr/node_modules/request/request.js:185:22)\n at Request.emit (events.js:310:20)\n at Request.onRequestError (/usr/node_modules/request/request.js:877:8)\n at ClientRequest.emit (events.js:322:22)\n at Socket.socketErrorListener (_http_client.js:426:9)\n at Socket.emit (events.js:310:20)\n at emitErrorNT (internal/streams/destroy.js:92:8)\n at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)\n at processTicksAndRejections (internal/process/task_queues.js:84:21)","type":"Error","msg":"Encountered an error during start up"}

Version:

Predator DC/OS package: [e.g. 1.0.0]
Database [e.g. MySQL]

Additional context I know that DC/OS does not have a large use but it is actually our container orchestration platform. I have some in-depth knowledge of this product but I was not able to find a workaround.