Backendless Pro Keeps crashing

General
1

Services keep crashing on server and requiring a restart of all the services. After restart of services this is displayed in the SSH console

/backendless/apps/backendless/scripts/ctl_js_coderunner.sh : JS Coderunner started
14:52:10.160 - [8027] Error: connect ECONNREFUSED 127.0.0.1:443
at Object._errnoException (util.js:1019:11)
at _exceptionWithHostPort (util.js:1041:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1175:14)
14:52:10.170 - [8027] Error during logs flushing connect ECONNREFUSED 127.0.0.1:443
14:52:10.429 - [8026] Error: connect ECONNREFUSED 127.0.0.1:443
at Object._errnoException (util.js:1019:11)
at _exceptionWithHostPort (util.js:1041:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1175:14)
14:52:10.465 - [8026] Error during logs flushing connect ECONNREFUSED 127.0.0.1:443
/backendless/apps/backendless/scripts/ctl_console.sh : Console started
Syntax OK
14:52:12.051 - [8090] Error: connect ECONNREFUSED 127.0.0.1:443
at Object._errnoException (util.js:1019:11)
at _exceptionWithHostPort (util.js:1041:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1175:14)
14:52:12.072 - [8090] Error during logs flushing connect ECONNREFUSED 127.0.0.1:443
/backendless/apache2/scripts/ctl.sh : httpd started at port 80

Please advise

2

Also getting these:

[11539] Error: No connection with server
at new ResponseError (/backendless/apps/backendless/modules/js_coderunner/node_modules/backendless-request/lib/index.js:38:116)
at checkStatus (/backendless/apps/backendless/modules/js_coderunner/node_modules/backendless-request/lib/index.js:229:23)
at
at process._tickDomainCallback (internal/process/next_tick.js:228:7)

Attached are the logs from the <install dir>/apps/backendless/logs directory

taskmanager.zip (12.01MB)

3

All services keep crashing or some of them? If some, which ones?
Do they crash intermittently, under load or some other conditions?

Please check how much memory/CPU is allocated to each process and ensure they have plenty at all times.

Regards,
Mark

4

Well its funny because none of the services are in a stopped state when this happens. Basically all API calls start to fail, you are unable to get to console, just comes up with splash screen background, says backendless and little scroll bar goes across the screen and then you get “No Connection to Server” error.

5

Sounds like a problem when the system runs out of threads or sockets or file handles. Have you checked that?