Downgrade *mongoose* due to production connection failure

[Martii]

• Hopefully this fixes this... not present in dev environment

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]

@sizzlemctwizzle
Please investigate this.

[Martii]

@sizzlemctwizzle
Please be advised that this may hose production from running due to a different failure of bson not being found... finally got it running after several retries with current dev GH HEAD

[sizzlemctwizzle]

Those error messages are from connect-mongo, not mongoose. I did upgrade the database to MongoDB v3.0.5

[Martii]

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.

[Martii]

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.

[sizzlemctwizzle]

connect-mongo shares the connection established by mongoose.
On Aug 17, 2015 12:05 PM, "Marti Martz" notifications@github.com wrote:

What's even more unusual is that I didn't do connect-mongo as a dep
migration. :\

—
Reply to this email directly or view it on GitHub
#712 (comment)
.