MongoError: connection 0 to localhost:27017 timed out

Question

events.js:141 throw er; // Unhandled 'error' event MongoError: connection 0 to localhost:27017 timed out at Function.MongoError.create (/home/ubuntu/scripts/node_modules/mongodb-core/lib/error.js:29:11) at Socket.<anonymous> (/home/ubuntu/scripts/node_modules/mongodb-core/lib/connection/connection.js:184:20) at Socket.g (events.js:260:16) at emitNone (events.js:67:13) at Socket.emit (events.js:166:7) at Socket._onTimeout (net.js:318:8) at _runOnTimeout (timers.js:524:11) at _makeTimerTimeout (timers.js:515:3) at Timer.unrefTimeout (timers.js:584:5)

Well there is no error during connection, but when try to save some models/collections it runs for a while and then it throws this error. BTW I also have another node process connected to the same mongodb server. Any help is highly appreciated.

I think it is the nodejs built in events.js (eventEmitter class). I dont know where it is. — Prata
– Prata, Commented Dec 30, 2016 at 10:50
If your query is taking a long time that is seconds, then there is some serious flaw in your system or you are doing more things an usual API is meant to do. Try using indexing in mongo collection to improve performance. — shijin
– shijin, Commented Oct 13, 2017 at 5:12
Some people get this error when the query is “long/heavy” (2s-5s) but not long enough that it should actually trigger the default timeout of 30s. For me, this went away when I switched to useMongoClient: true from ≥mongoose-4.11. — binki
– binki, Commented Aug 3, 2018 at 3:12

Prata · Accepted Answer · 2018-03-27 07:35:07Z

18

const mongoose = require('mongoose'); const option = { socketTimeoutMS: 30000, keepAlive: true, reconnectTries: 30000 }; const mongoURI = process.env.MONGODB_URI; mongoose.connect(mongoURI, option).then(function(){ //connected successfully }, function(err) { //err handle });

edited Mar 27, 2018 at 7:35

answered Jun 20, 2017 at 19:26

Prata

1,3202 gold badges16 silver badges37 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Maxim Over a year ago

They are deprecated as in mongoose 5.x, you can now put them at the top level of the option map. const options = { keepAlive: 300000, connectTimeoutMS: 30000 };

Rishul Matta Over a year ago

For me none of the above worked so had to downgrade and this one worked out: stackoverflow.com/a/46699144/2427266

user7075574 Over a year ago

The options available if you want to check if it stills supported

Shreya Batra · Accepted Answer · 2016-12-30 10:49:22Z

Your query is taking a long time. And mongo itself has a default time out set. So it times out, if the query takes longer than the timeout time.

Lucas Assmann · Accepted Answer · 2017-05-12 18:52:36Z

3

you have to use this configs on your connection: keepAlive: 300000, connectTimeoutMS: 30000

answered May 12, 2017 at 18:52

Lucas Assmann

411 silver badge8 bronze badges

1 Comment

harryfeng Over a year ago

how do I do it with nodejs driver?like this? MongoClient.connect("mongodb://localhost:27017/articledb", { keepAlive: 30000, connectTimeoutMS: 30000, }, function(err, db) {})

Daniel Staleiny · Accepted Answer · 2018-12-06 11:16:11Z

If you are sure that you exported port -p 27017:2017 and it still doesn't work.

Check your VPN if it is not blocking Local Network sharing.

Collectives™ on Stack Overflow

MongoError: connection 0 to localhost:27017 timed out

4 Answers 4

3 Comments

Comments

1 Comment

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

3 Comments

Comments

1 Comment

Comments

Linked

Related