Geek Answers Handbook

Problems since the last update (0.5.3) of Meteor?

I just updated Meteor, and now all of my applications suddenly cause the following error when trying to start them:

app/packages/mongo-livedata/mongo_driver.js:32 throw err; ^ Error: failed to connect to [127.0.0.1:3002] at Server.connect.connectionPool.on.server._serverState (/usr/local/meteor/lib/node_modules/mongodb/lib/mongodb/connection/server.js:482:73) at EventEmitter.emit (events.js:123:20) at connection.on._self._poolState (/usr/local/meteor/lib/node_modules/mongodb/lib/mongodb/connection/connection_pool.js:96:15) at EventEmitter.emit (events.js:96:17) at Socket.errorHandler (/usr/local/meteor/lib/node_modules/mongodb/lib/mongodb/connection/connection.js:411:10) at Socket.EventEmitter.emit (events.js:93:17) at Socket._destroy.self.errorEmitted (net.js:328:14) at process.startup.processNextTick.process._tickCallback (node.js:244:9) Exited with code: 1

Any advice is appreciated! Thanks

+4
source share
2 answers

Run meteor update to upgrade to 0.5.4 , which should fix it. See below to understand what is wrong.

It was a regression in Meteor 0.5.3. In development mode, Meteor executes ps to find out if there is an existing mongod to kill before launching the new mongod . When creating an unrelated patch, I added some erroneous error checking to see that ps printing something standard error. Unfortunately, in OSX Mountain Lion, if DYLD_LIBRARY_PATH (or several other environment variables starting with DYLD or LD_LIBRARY_PATH ), then running ps displays a warning on stderr, as a result of which Meteor 0.5.3 considers ps . I fixed this and released a fix in Meteor 0.5.4, thanks to this stack overflow question.

+8
source

I found a problem, I had to use sudo to start the meteorite server. I didn’t have to do this before.

+2
source

More articles:


All Articles