-
Notifications
You must be signed in to change notification settings - Fork 42
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
Comments
Shot in the dark, but have you tried |
changing the directory write permissions doesn't seem to do anything. |
I got deploy working by changing line 118 to |
Ah, yeah. PITA that forever still doesn't support conditional restarts. Care to submit a pull request? Thanks! |
Fix for issue #20--forever unable to open log file
I followed the instructions as closely as possible but meteoric deploy fails in the following manner:
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.
The text was updated successfully, but these errors were encountered: