Open hitesh83 opened 3 years ago
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;
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.
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.