Downgrade *mongoose* due to production connection failure #712
Conversation
Martii
commented
Aug 17, 2015
Martii
commented
- Hopefully this fixes this... not present in dev environment
* Hopefully this fixes this... not present in dev environment
``` sh-session
connection error: { [MongoError: no valid seed servers in list] name: 'MongoError', message: 'no valid seed servers in list' }
.write(string, encoding, offset, length) is deprecated. Use write(string[, offset[, length]][, encoding]) instead.
(node) warning: possible EventEmitter memory leak detected. 11 connected listeners added. Use emitter.setMaxListeners() to increase limit.
Trace
at MongoStore.addListener (events.js:179:15)
at MongoStore.once (events.js:204:8)
at MongoStore.getCollection (/home/oujs/OpenUserJS.org/node_modules/connect-mongo/lib/connect-mongo.js:219:16)
at MongoStore.get (/home/oujs/OpenUserJS.org/node_modules/connect-mongo/lib/connect-mongo.js:285:10)
at session (/home/oujs/OpenUserJS.org/node_modules/express-session/index.js:404:11)
at Layer.handle [as handle_request] (/home/oujs/OpenUserJS.org/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/home/oujs/OpenUserJS.org/node_modules/express/lib/router/index.js:312:13)
at /home/oujs/OpenUserJS.org/node_modules/express/lib/router/index.js:280:7
at Function.process_params (/home/oujs/OpenUserJS.org/node_modules/express/lib/router/index.js:330:12)
at next (/home/oujs/OpenUserJS.org/node_modules/express/lib/router/index.js:271:10)
at initialize (/home/oujs/OpenUserJS.org/node_modules/passport/lib/middleware/initialize.js:62:5)
at Layer.handle [as handle_request] (/home/oujs/OpenUserJS.org/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/home/oujs/OpenUserJS.org/node_modules/express/lib/router/index.js:312:13)
at /home/oujs/OpenUserJS.org/node_modules/express/lib/router/index.js:280:7
at Function.process_params (/home/oujs/OpenUserJS.org/node_modules/express/lib/router/index.js:330:12)
at next (/home/oujs/OpenUserJS.org/node_modules/express/lib/router/index.js:271:10)
```
Martii
added
migration
Downgrade *mongoose* due to production connection failure Auto-merge
|
@sizzlemctwizzle |
|
@sizzlemctwizzle |
|
Those error messages are from connect-mongo, not mongoose. I did upgrade the database to MongoDB v3.0.5 |
Does this mean this shouldn't happen again on this specific versioning? We were (unscheduled) down for about 25 minutes and I got several bson errors. |
|
What's even more unusual is that I didn't do connect-mongo as a dep migration. :\ ... mongoose doesn't appear to have this as one of their deps... however connect-mongo has a devDep with mongoose in it. |
|
connect-mongo shares the connection established by mongoose.
|
