forever@0.7.4 / fails to start #179

Closed
bradleyg opened this Issue Nov 29, 2011 · 21 comments

Projects

None yet

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.

ssoria commented Nov 29, 2011

i'm seeing this issue also. can't workaround it by using an older version because of #172

JCBarry commented Nov 29, 2011

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.

thiromi commented Nov 29, 2011

Same here on Ubuntu.

Tried on node 0.6.3 and 0.4.12

aarong commented Nov 29, 2011

Same issue here (Ubuntu Server 10.04 on Amazon EC2).

+1

node v0.6.2, OS X 10.7

JCBarry commented Nov 29, 2011

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 npm install while still inside /usr/local/lib/node_modules/forever

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.

wavded commented Nov 29, 2011

same issue, Ubuntu 10.10

ssoria commented Nov 30, 2011

if you need to automate the installation of forever, i've created a fix against 0.7.1. you can get it with
npm install git://github.com/ssoria/forever.git#fix-nconf

JCBarry commented Nov 30, 2011

It appears as though this commit (7cdca07) addresses this issue.
Installing forever from the Github master branch seems to also have resolved the issue.

If you're interested in giving it a go, run this:

npm install git://github.com/nodejitsu/forever.git -g
Contributor

Yes, @JCBarry is right. Sorry, I forgot to mention it here.
@indexzero Can you bump and npm publish?

Owner

Def. I'll do so tonight

cielo commented Dec 2, 2011

After fresh installing forever by following @JCBarry 's comment, forever list does not seem to list processes that are started by forever. It is weird cause it successfully started, and I can actually connect to the node server, but forever does not list any processes. I am using node v6.3.

Is there anyway that I can see which processes are running without using 'forever list' command?

MrOwen commented Dec 2, 2011

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 ps aux | grep node to list node processes but I found that the PID change constantly which is something that is beyond my scope of knowledge but it leads me to believe that it is near impossible to kill by PID. Check out How-To Geek's article on how to kill process by name rather than PID.

I have the same issues as @cielo and have had to kill node processes manually after forever fails to see them, following @JCBarry's suggestion.

The best workaround above for me has been from @ssoria above.

Could I vote for this issue to be prioritized higher than medium-priority?

JCBarry commented Dec 2, 2011

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 forever list commands: sometimes my processes would be there sometimes they wouldn't -- similar to what others are reporting.

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.

Owner

@jcbarry Have you tried rolling back to >= forever@0.7.4 (say 0.7.2?). We are in the process of refactoring forever to use flatironjs, so I suspect this may related to a dependency there.

I'm looking into it.

Same here on a deployment, rolling back no dice

@indexzero indexzero closed this in dcbfc70 Dec 2, 2011
Owner

This is fixed in forever@0.7.5

JCBarry commented Dec 5, 2011

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:
forever -a start app.js

if I dont' use the append option (forever start app.js), I get:
info: Forever processing file: app.js
error: Cannot start forever
error: log file /root/.forever/forever.log exists. Use the -a or --append option to append log.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment