search

arunoda / meteor-up-legacy

Production Quality Meteor Deployments
MIT License
2.26k stars 395 forks source link

wait-for-mongo: command not found #82

Open subhog opened 10 years ago

subhog commented 10 years ago

My deploy process failed today on the Invoking deployment process step. The STDERR message was

bash: line 54: wait-for-mongo: command not found

When accessing the page after deploy, I got error 503. After updating mup to the current version, the process still say it fails on that step (with line number 55 this time), though the app works fine now.

arunoda commented 10 years ago

Can you please do mup setup?

On Thursday, June 26, 2014, subhog notifications@github.com wrote:

My deploy process failed today on the Invoking deployment process step. The STDERR message was

bash: line 54: wait-for-mongo: command not found

When accessing the page after deploy, I got error 503. After updating mup to the current version, the process still say it fails on that step (with line number 55 this time), though the app works fine now.

— Reply to this email directly or view it on GitHub https://github.com/arunoda/meteor-up/issues/82.

Arunoda Susiripala I curate Meteor Weekly - Check it out! http://meteorhacks.com/meteor-weekly/?utm_source=email-footer&utm_medium=email&utm_campaign=meteorweekly

subhog commented 10 years ago

Didn't help. I ran it originally if I recall. There are five apps deployed on the server, others are working well.

subhog commented 10 years ago

Here's the whole output:

bocian:mup-brzoza hubert$ mup deploy

Meteor Up: Production Quality Meteor Deployments
------------------------------------------------

Bundling Started: ../toolaxy

Started TaskList: Deploy app 'toolaxy' (linux)
[80.240.133.200] - Uploading bundle
[80.240.133.200] ✔ Uploading bundle: SUCCESS
[80.240.133.200] - Setting up Environment Variables
[80.240.133.200] ✔ Setting up Environment Variables: SUCCESS
[80.240.133.200] - Invoking deployment process
[80.240.133.200] ✘ Invoking deployment process: FAILED

  -----------------------------------STDERR-----------------------------------
  Warning: Permanently added '80.240.133.200' (RSA) to the list of known hosts.
  npm http GET https://registry.npmjs.org/fibers
  npm http 304 https://registry.npmjs.org/fibers
  npm http GET https://registry.npmjs.org/bcrypt
  npm http 304 https://registry.npmjs.org/bcrypt
  npm http GET https://registry.npmjs.org/bindings
  npm http 304 https://registry.npmjs.org/bindings
  bash: line 55: wait-for-mongo: command not found
  -----------------------------------STDOUT-----------------------------------

  > fibers@1.0.1 install /opt/toolaxy/tmp/bundle/programs/server/node_modules/fibers
  > node ./build.js

  `linux-x64-v8-3.14` exists; testing
  Binary is fine; exiting
  fibers@1.0.1 node_modules/fibers

  > bcrypt@0.7.8 install /opt/toolaxy/tmp/bundle/programs/server/node_modules/bcrypt
  > node-gyp rebuild

  make: Entering directory `/opt/toolaxy/tmp/bundle/programs/server/node_modules/bcrypt/build'
    CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
    CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
    CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
    SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node
    SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node: Finished
    COPY Release/bcrypt_lib.node
  make: Leaving directory `/opt/toolaxy/tmp/bundle/programs/server/node_modules/bcrypt/build'
  bcrypt@0.7.8 node_modules/bcrypt
  └── bindings@1.0.0
  toolaxy stop/waiting
  toolaxy start/running, process 4929
  Waiting for MongoDB to initialize. (5 minutes)
  ----------------------------------------------------------------------------
Completed TaskList: Deploy app 'toolaxy' (linux)
arunoda commented 10 years ago

That's pretty weird. Can you please check wait-for-mongo installed on the server.

It's a npm module. Install it with.

npm install -g wait-for-mongo

On Thursday, June 26, 2014, subhog notifications@github.com wrote:

Here's the whole output:

bocian:mup-brzoza hubert$ mup deploy

Meteor Up: Production Quality Meteor Deployments

Bundling Started: ../toolaxy

Started TaskList: Deploy app 'toolaxy' (linux) [80.240.133.200] - Uploading bundle [80.240.133.200] ✔ Uploading bundle: SUCCESS [80.240.133.200] - Setting up Environment Variables [80.240.133.200] ✔ Setting up Environment Variables: SUCCESS [80.240.133.200] - Invoking deployment process [80.240.133.200] ✘ Invoking deployment process: FAILED

-----------------------------------STDERR----------------------------------- Warning: Permanently added '80.240.133.200' (RSA) to the list of known hosts. npm http GET https://registry.npmjs.org/fibers npm http 304 https://registry.npmjs.org/fibers npm http GET https://registry.npmjs.org/bcrypt npm http 304 https://registry.npmjs.org/bcrypt npm http GET https://registry.npmjs.org/bindings npm http 304 https://registry.npmjs.org/bindings bash: line 55: wait-for-mongo: command not found -----------------------------------STDOUT-----------------------------------

fibers@1.0.1 install /opt/toolaxy/tmp/bundle/programs/server/node_modules/fibers node ./build.js

linux-x64-v8-3.14 exists; testing Binary is fine; exiting fibers@1.0.1 node_modules/fibers

bcrypt@0.7.8 install /opt/toolaxy/tmp/bundle/programs/server/node_modules/bcrypt node-gyp rebuild

make: Entering directory /opt/toolaxy/tmp/bundle/programs/server/node_modules/bcrypt/build' CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node: Finished COPY Release/bcrypt_lib.node make: Leaving directory/opt/toolaxy/tmp/bundle/programs/server/node_modules/bcrypt/build' bcrypt@0.7.8 node_modules/bcrypt └── bindings@1.0.0 toolaxy stop/waiting toolaxy start/running, process 4929 Waiting for MongoDB to initialize. (5 minutes)

Completed TaskList: Deploy app 'toolaxy' (linux)

— Reply to this email directly or view it on GitHub https://github.com/arunoda/meteor-up/issues/82#issuecomment-47222414.

Arunoda Susiripala

@arunoda http://twitter.com/arunoda http://gplus.to/arunodahttps://github.com/arunoda http://www.linkedin.com/in/arunoda

subhog commented 10 years ago

After manually installing wait-for-mongo that particular problem went away. Now it cannot connect to the port, but this one seems like just some debris on the server side.

Still it's weird as wait-for-mongo didn't cause problems for the other apps.

But well, aren't all things here either weird or feature requests?

LeCoupa commented 9 years ago

I have exactly the same issue. After installing wait-for-mongo on the server, mup cannot connect to the specified port.

0curl: (7) Failed to connect to localhost port 58000: Connection refused

@subhog, did you find a solution?

EDIT: The problem was coming from my server (but may also come from your application). What you must do is check your logs with mup logs -n100. In my case, forever wasn't installed.

formspoint commented 7 years ago

@LeCoupa looks like I'm running into the same issue as you did back in `15. Had issue, installed wait-for-mongo, and fix it, but now got the forever issue. Did you do a npm install -g forever ?

LeCoupa commented 7 years ago

yes that's what I did if I remember.

luixal commented 4 years ago

Just hit this issue. If anyone getting here, just make sure that wait-for-mongo command is available to the ssh user. I had to make a symbolic link into /usr/bin or /usr/sbin not sure which one did the trick:

sudo ln -s /opt/nodejs/bin/wait-for-mongo /usr/sbin/