Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

read ETIMEDOUT at TCP #139

Open
hitesh83 opened this issue Nov 30, 2021 · 2 comments
Open

read ETIMEDOUT at TCP #139

hitesh83 opened this issue Nov 30, 2021 · 2 comments

Comments

@hitesh83
Copy link

Error: read ETIMEDOUT
at TCP.onStreamRead (internal/stream_base_commons.js:111:27)

Changed server today from Ubuntu 16 to 20.
Old server was on Mongo 3.4 & node 12 both from their own repo.

Using mongo 3.6 and node 10 both from Ubuntu 20 repo.

Servers goes offline with above error.

Is this related to Node?

Help please.

@hitesh83
Copy link
Author

hitesh83 commented Dec 1, 2021

Update -
Looks like this issue is not related to Node or Mongo,
the error basically shows communication between client and server dropped by time out.
In my case, this could be my reverse proxy and the node communication.

added below to my reverse proxy configuration (not a part of pisignage pacakge)

proxy_connect_timeout       300;
proxy_send_timeout          300;
proxy_read_timeout          300;
send_timeout                300;

@hitesh83
Copy link
Author

hitesh83 commented Dec 2, 2021

Update - none of the settings worked still getting same errors.

Server is running via pm2 so issue do not affect the functionality. pm2 restarts the process on error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant