Meteor.com MongoDB replication down?


#1

Can it be that Meteor.com hosting is currently down? I also can not connect to mongodb of my applications?

This is in the logs of my application(s)

at [object Object].ReplSet.checkoutReader
(/meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/connection/repl_set/repl_set.js:613:14)
at Cursor.nextObject
(/meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/cursor.js:748:48)
at Cursor.toArray
(/meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/cursor.js:169:10)
at Db.indexInformation
(/meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/db.js:1629:39)
at Db.ensureIndex
(/meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/db.js:1496:8)
at Collection.ensureIndex
(/meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/collection/index.js:68:11)
at [object Object].MongoConnection._ensureIndex (packages/mongo/mongo_driver.js:732:1)
at [object Object].Mongo.Collection._ensureIndex (packages/mongo/collection.js:620:1)
at Accounts.urls (packages/accounts-base/accounts_server.js:1309:1)
at /meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/packages/accounts-base.js:1616:4
[Mon May 11 2015 22:32:55 GMT+0000 (UTC)] ERROR Application crashed with code: 8
[Mon May 11 2015 22:32:55 GMT+0000 (UTC)] NOTICE Starting application on port 30609
[Mon May 11 2015 22:32:55 GMT+0000 (UTC)] INFO STATUS running -> starting
[Mon May 11 2015 22:32:55 GMT+0000 (UTC)] INFO STATUS starting -> running
[Mon May 11 2015 22:33:44 GMT+0000 (UTC)] INFO HIT / 71.198.37.65
[Mon May 11 2015 22:33:55 GMT+0000 (UTC)] WARNING 
/meteor/dev_bundles/0.4.18/lib/node_modules/fibers/future.js:245
throw(ex);
^
[Mon May 11 2015 22:33:55 GMT+0000 (UTC)] WARNING Error: No replica set primary available for query with ReadPreference PRIMARY
at Object.Future.wait (/meteor/dev_bundles/0.4.18/lib/node_modules/fibers/future.js:395:16)
at [object Object].MongoConnection._ensureIndex (packages/mongo/mongo_driver.js:733:1)
at [object Object].Mongo.Collection._ensureIndex (packages/mongo/collection.js:620:1)
at Accounts.urls (packages/accounts-base/accounts_server.js:1309:1)
at /meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/packages/accounts-base.js:1616:4
at /meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/packages/accounts-base.js:1659:3
at /meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/boot.js:222:10
at Array.forEach (native)
at Function._.each._.forEach (/meteor/dev_bundles/0.4.18/lib/node_modules/underscore/underscore.js:79:11)
at /meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/boot.js:117:5
- - - - -
at [object Object].ReplSet.checkoutReader
(/meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/connection/repl_set/repl_set.js:613:14)
at Cursor.nextObject
(/meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/cursor.js:748:48)
at Cursor.toArray
(/meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/cursor.js:169:10)
at Db.indexInformation
(/meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/db.js:1629:39)
at Db.ensureIndex
(/meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/db.js:1496:8)
at Collection.ensureIndex
(/meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/npm/mongo/node_modules/mongodb/lib/mongodb/collection/index.js:68:11)
at [object Object].MongoConnection._ensureIndex (packages/mongo/mongo_driver.js:732:1)
at [object Object].Mongo.Collection._ensureIndex (packages/mongo/collection.js:620:1)
at Accounts.urls (packages/accounts-base/accounts_server.js:1309:1)
at /meteor/containers/f2c399fe-caa6-2052-ca83-955e576be00f/bundle/programs/server/packages/accounts-base.js:1616:4
[Mon May 11 2015 22:33:55 GMT+0000 (UTC)] INFO STATUS running -> starting
[Mon May 11 2015 22:33:55 GMT+0000 (UTC)] ERROR Application crashed with code: 8
[Mon May 11 2015 22:33:55 GMT+0000 (UTC)] NOTICE Starting application on port 30609
[Mon May 11 2015 22:33:56 GMT+0000 (UTC)] INFO STATUS starting -> running
[Mon May 11 2015 22:34:06 GMT+0000 (UTC)] INFO HIT / 71.198.37.65

#2

This is happening to me as well.


#3

Yep, for me, too. Anyone have a direct line to someone on ops? I don’t see anything on their Twitter account.


#4

Looks like they have screwed DB (again)
I have deleted and redeployed, now it works


#5

Thanks for the tip. I deleted and redeployed as well and now my app is working again.


#6

Indeed, that did the trick. Thanks


#7

Is it possible to backup the database before deleting and redeploying ?


#8

It seems the problem is the database for the site(s) to be down (at least I was not able to access any of my data).


#9

tunifight, sure it is. It just needs to be done before the DB is screwed.

Speaking of which, I am seriously looking for some backup solution


#10

Doesn’t seem to be any way to recover the existing db until this problem is fixed…
Is that even likely?
I know this is not a production environment - and we should follow good backup procedures in any case - but is there a chance this will be corrected?


#11

All my sites that were down are back up


#12

Yes, my app is working again too, data backup done to avoid future surprises :smiley: