Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

failing meteoric deploy #20

Closed
bd opened this issue Feb 14, 2014 · 4 comments
Closed

failing meteoric deploy #20

bd opened this issue Feb 14, 2014 · 4 comments

Comments

@bd
Copy link
Contributor

bd commented Feb 14, 2014

I followed the instructions as closely as possible but meteoric deploy fails in the following manner:

Starting forever
error:   Error restarting process: bundle/main.js
error:   Cannot find forever process: bundle/main.js
warn:    --minUptime not set. Defaulting to: 1000ms
warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info:    Forever processing file: bundle/main.js

fs.js:427
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^
Error: EACCES, permission denied '/home/ubuntu/.forever/fzyu.log'
    at Object.fs.openSync (fs.js:427:18)
    at Object.forever.startDaemon (/usr/lib/node_modules/forever/lib/forever.js:406:14)
    at /usr/lib/node_modules/forever/lib/forever/cli.js:257:13
    at /usr/lib/node_modules/forever/lib/forever/cli.js:144:5
    at /usr/lib/node_modules/forever/lib/forever.js:358:11
    at Object.oncomplete (fs.js:107:15)

running forever list as ubuntu and su user shows no running forever processes.
following the instructions here: https://github.com/joyent/node/wiki/Installing-Node.js-via-package-manager, I updated node to v0.10.25 (was originally v0.8.12 after running meteoric setup) but failed in the same manner. I was looking at issue #18, but closer inspection makes me think they're unrelated.

I am able to start my app with sudo PORT=80 MONGO_URL=mongodb://uzr:[email protected]:10097/ways ROOT_URL=mypublicdns.ec2.amazonaws.com nohup node bundle/main.js &

just spitballing at this point, but here's the permissions for the path mentioned above drwxr-xr-x 4 root root 4096 Feb 14 19:23 .forever/. chmod u+w .forever/ doesn't help...

Let me know what else I can do to investigate or help out with this, and thanks for putting meteoric together in the first place.

@julien-c
Copy link
Owner

Shot in the dark, but have you tried chmod +w /home/ubuntu/.forever/?
Also, you can always run supervisord instead.
Let me know if it helps.

@bd
Copy link
Contributor Author

bd commented Feb 14, 2014

changing the directory write permissions doesn't seem to do anything. supervisord instead of what? forever?

@bd
Copy link
Contributor Author

bd commented Feb 14, 2014

I got deploy working by changing line 118 to
sudo -E forever restart bundle/main.js || sudo -E forever start bundle/main.js;

@julien-c
Copy link
Owner

Ah, yeah. PITA that forever still doesn't support conditional restarts.

Care to submit a pull request?

Thanks!

bd added a commit to bd/meteoric.sh that referenced this issue Feb 15, 2014
julien-c added a commit that referenced this issue Feb 15, 2014
Fix for issue #20--forever unable to open log file
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants