Shiny server throws Econnreset

I am running a shiny application in a docker container inside Openshift. I am using the rocker/shiny-4.0.3.

After working a but with the application 30 seconds/1min Shiny server crashes with the following error:

shiny-server - Uncaught exception: Error: read ECONNRESET

Listening on http://127.0.0.1:43876
[2021-02-02T15:45:45.600] [ERROR] shiny-server - Uncaught exception: Error: read ECONNRESET
[2021-02-02T15:45:45.601] [ERROR] shiny-server - Error: read ECONNRESET
at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
[2021-02-02T15:45:45.601] [INFO] shiny-server - Stopping listener on http://[::]:3838
[2021-02-02T15:45:45.601] [INFO] shiny-server - Shutting down worker processes (with notification)
/opt/shiny-server/lib/main.js:387
throw err;
^

Error: read ECONNRESET
at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
Emitted 'error' event on Socket instance at:
at emitErrorNT (internal/streams/destroy.js:92:8)
at emitErrorAndCloseNT (internal/streams/destroy.js:60:3)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
errno: 'ECONNRESET',
code: 'ECONNRESET',
syscall: 'read'
}

Other applications seem to work fine.

I have checked stack and the community but I have found no information about what the possible issue can be.

Thanks a lot for your help.

The solution to this problem was really simple, I have left some developing lines inside the production code, so exclusively my bad

shiny.autoreload was set to true and shiny.port was also defined in options. This produced a conflict with Shiny server configuration and of course the server and the application crashed.

Thanks a lot for your help.

Luis

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.