arunoda / meteor-up-legacy

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

Uploading bundle FAILED - No such file #471

Open iwanjunaid opened 9 years ago

iwanjunaid commented 9 years ago

DEBUG=* mup setup run successfuly

Started TaskList: Setup (linux)
[localhost] - Setting up Environment
[localhost] - Setting up Environment: SUCCESS
[localhost] - Configuring upstart
  nodemiral:sess:localhost copy file - src: /usr/local/lib/node_modules/mup/templates/linux/meteor.conf, dest: /etc/init/mymup.conf, vars: {"appName":"mymup"} +0ms
[localhost] - Configuring upstart: SUCCESS

DEBUG=* mup deploy resulting error as follow

Started TaskList: Deploy app 'mymup' (linux)
[localhost] - Uploading bundle
  nodemiral:sess:localhost copy file - src: /tmp/cb6561b6-9458-4836-8823-56f8f8a256ac/bundle.tar.gz, dest: /opt/mymup/tmp/bundle.tar.gz, vars: undefined +0ms
[localhost] x Uploading bundle: FAILED
    No such file
arunoda commented 9 years ago

Have you done mup setup ? On 2015 ජූනි 11, බ්‍රහස් at ප.ව. 1.06 Iwan Junaid notifications@github.com wrote:

DEBUG=* mup setup run successfuly

Started TaskList: Setup (linux) [localhost] - Setting up Environment [localhost] - Setting up Environment: SUCCESS [localhost] - Configuring upstart nodemiral:sess:localhost copy file - src: /usr/local/lib/node_modules/mup/templates/linux/meteor.conf, dest: /etc/init/mymup.conf, vars: {"appName":"mymup"} +0ms [localhost] - Configuring upstart: SUCCESS

DEBUG=* mup deploy resulting error as follow

Started TaskList: Deploy app 'mymup' (linux) [localhost] - Uploading bundle nodemiral:sess:localhost copy file - src: /tmp/cb6561b6-9458-4836-8823-56f8f8a256ac/bundle.tar.gz, dest: /opt/mymup/tmp/bundle.tar.gz, vars: undefined +0ms [localhost] x Uploading bundle: FAILED No such file

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

iwanjunaid commented 9 years ago

hi @arunoda

yes, i have already run mup setup in the beginning step just as shown in my first comment

arunoda commented 9 years ago

Hmm. Could you check the file system on /opt and seems like it's not created properly.

Also try to use Ubuntu 14.04. If that's doesn't help, try to use mupx. On 2015 ජූනි 11, බ්‍රහස් at ප.ව. 1.13 Iwan Junaid notifications@github.com wrote:

hi @arunoda https://github.com/arunoda

yes, i have already run mup setup in the beginning step just as shown in my first comment

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

gdespirito commented 9 years ago

For me was the nodejs version.

From "nodeVersion": "0.10.36" To: "nodeVersion": "0.10.37",

richsilv commented 9 years ago

For me it was leaving spaces in my appName (even though the config file tells you not to...)

nitinja commented 9 years ago

I had this issue. I fixed it by changing node version to "0.10.37".

MichaelJCole commented 9 years ago

The node version worked once, then didn't for me.

From what I can tell before deploying with a new 'appname', you have to do a mup setup. Once for each app if you have multiple apps, and also if you change the appname.

(mup setup doesn't show the appname, so I initially assumed it was for the "whole server")

There were a couple times I needed to wipe the server and start over, but luckily with stateless servers that's super easy. Hosting your DB on a service really helps here (mongohq, compose.io, whatever)

Anyways, mup saved me bunches of time. Can't wait for mupx!

StephanGeorg commented 9 years ago

For me it was also a space in appName. After changing don't forget to run mup setup again and then mup deploy.

nilsi commented 8 years ago

Same for me. Thanks @StephanGeorg for pointing out that I needed to run setup again after changing name.

musemind commented 8 years ago

same problem, raised from 0.10.36 to 0.10.37, mup setup again, mup deploy again => works