-
Notifications
You must be signed in to change notification settings - Fork 947
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
forever@0.7.4 / fails to start #179
Comments
i'm seeing this issue also. can't workaround it by using an older version because of #172 |
I'm receiving the same errors on OS X 10.7: https://gist.github.com/1403426 |
I have the same issue on amazon linux instance, running node 0.6.3 - also no workaround available because of #172. |
Same here on Ubuntu. Tried on node 0.6.3 and 0.4.12 |
Same issue here (Ubuntu Server 10.04 on Amazon EC2). |
+1 node v0.6.2, OS X 10.7 |
I managed to pull together a (partial) workaround. For anyone who is desperate try the following: npm install forever@0.7.3 -g
cd /usr/local/lib/node_modules/forever
rm -rf node_modules Now modify the package.json file to use nconf 0.4, then run The test suite yields the following result: https://gist.github.com/1406726 **Note: It's probably worth noting that I've been able to start, stop and list using the CLI with this workaround. |
same issue, Ubuntu 10.10 |
if you need to automate the installation of forever, i've created a fix against 0.7.1. you can get it with |
It appears as though this commit (7cdca07) addresses this issue. If you're interested in giving it a go, run this:
|
Yes, @JCBarry is right. Sorry, I forgot to mention it here. |
Def. I'll do so tonight |
After fresh installing forever by following @JCBarry 's comment, Is there anyway that I can see which processes are running without using 'forever list' command? |
Same issue as @cielo. I can spin up a node instance with forever but if I want to kill it, I have to do so through another means of killing the node process(es). Also, @cielo, you can do |
Sorry for the delayed replies. I found similar instability in using forever from master over the past couple days. I'm on a deadline for deploy and had to go in another direction to make sure I could start/stop instances using capistrano. The commit I referenced solves only part of this problem, apparently. I also noticed inconsistent I also noticed that forever CLI was ignoring some option parameters. Specifically, it was ignoring the log file option when passing it a custom log file path. Like I said, I had to go in another direction due to this instability. I wish I didn't. Forever would have saved me a lot of headache. +1 for making this a higher priority. |
@JCBarry Have you tried rolling back to I'm looking into it. |
Same here on a deployment, rolling back no dice |
This is fixed in |
Didn't see your previous messages @indexzero. Great to hear it's all straightened out -- I'll check it out as soon as I can. Thanks for the quick fix, bud. |
Not sure if this means anything, but it worked for me when I install from git like JCBarry metnion above, plus I used the "append" option: if I dont' use the append option (forever start app.js), I get: |
https://gist.github.com/1402515
On a fresh install of node v0.4.12 / ubuntu 11.10. All seems to be working fine on osx.
The text was updated successfully, but these errors were encountered: