Meteor 1.3 deploying error with the fibers


#1

Until 1.3, I deployed meteor app by using AWS + Passenger + Nginx.

I already know the bug about npm-bcrypt.

Then, after I made new meteor app with 1.3, below error occurs.

Raw process output:

/var/www/pengyou/programs/server/node_modules/fibers/future.js:300
throw(ex);
^
Error: failed to connect to [localhost:27017]
at Object.Future.wait (/var/www/pengyou/programs/server/node_modules/fibers/future.js:420:15)
at new MongoConnection (packages/mongo/mongo_driver.js:213:27)
at new MongoInternals.RemoteCollectionDriver (packages/mongo/remote_collection_driver.js:4:16)
at Object. (packages/mongo/remote_collection_driver.js:38:10)
at Object.defaultRemoteCollectionDriver (packages/underscore.js:784:19)
at new Mongo.Collection (packages/mongo/collection.js:102:40)
at AccountsServer.AccountsCommon (packages/accounts-base/accounts_common.js:23:18)
at new AccountsServer (packages/accounts-base/accounts_server.js:18:5)
at meteorInstall.node_modules.meteor.accounts-base.server_main.js (packages/accounts-base/server_main.js:9:12)
at fileEvaluate (packages/modules-runtime.js:158:9)
- - - - -
at [object Object]. (/var/www/pengyou/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/mongodb/connection/server.js:556:74)
at [object Object].emit (events.js:106:17)
at [object Object]. (/var/www/pengyou/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:156:15)
at [object Object].emit (events.js:98:17)
at Socket. (/var/www/pengyou/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/mongodb/connection/connection.js:534:10)
at Socket.emit (events.js:95:17)
at net.js:441:14
at process._tickCallback (node.js:448:13)

Now I’m using node v0.10.41 with NVM (and also set it at nginx.conf)
AWS EC2 with ubuntu 14.04

help me please. it drives me crazy :frowning:


#2

I know this is an old topic but I had the exact same problem on Apache + Passenger + Meteor 1.3 and in case someone ask the question again.

There is my solution :
To fix it, I’ve installed mongodb 3.2.7 and made sure that mongod was running.