Discussion:
[mongodb-user] Timeout on MongoDB Atlas connection
Pierrick
2018-10-23 11:06:50 UTC
Permalink
Hello,

Since yesterday (2018-10-22 at about 7PM UTC), we have a reachability issue
when trying to connect from a nodejs app : "error MongoNetworkError:
connection 104 to xxxxxxx.mongodb.net:27017 timed out".
It happens every 20 mins or more often sometimes (10, 5 or 2 minutes).

We didn't change anything in our side ? Is there something we can do ?

Cheers,
--
Pierrick
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/df355412-d062-4f07-98cb-5dda76610e0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
'Kevin Adistambha' via mongodb-user
2018-10-26 02:47:24 UTC
Permalink
Hi Pierrick,

Since yesterday (2018-10-22 at about 7PM UTC), we have a reachability issue
when trying to connect from a nodejs app : “error MongoNetworkError:
connection 104 to xxxxxxx.mongodb.net:27017 timed out”.

From the error message, it looks like there’s a network issue from the
machine that’s hosting your app to Atlas. Can you confirm that you can
connect using the mongo shell without any issue? Is the issue intermittent,
or are you consistently cannot connect to Atlas? What is your Atlas
instance type?

Please note that if you’re using Atlas, you can open a support ticket at MongoDB
support page <https://support.mongodb.com/>. If this issue is still
unresolved, I would encourage you to open a ticket.

Best regards,
Kevin
​
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/d5509faf-5d08-4a22-b587-ba8a0d62705b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Pierrick
2018-10-28 22:39:39 UTC
Permalink
Hi Kevin,

The issue seems to be resolved without any change on my side.
It was intermittent during about 2-3 days.
Mongo shell used to report : 'Dropping all pooled connections to
xxxx-shard-00-00-yyyy.gcp.mongodb.net:27017(with timeout of 5 seconds)'
Similarly, mongostat reported something like 'No data recieved' only for
the primary host
I use a free tier instance for the moment.

Regards,
--
Pierrick
--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user+***@googlegroups.com.
To post to this group, send email to mongodb-***@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/2f09f2cb-823d-4546-ac5d-803fc93a58ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Loading...