i have some problem with node V0.11.XX

[lonso]

i am run node in v0.11.XX and i use forever to run that.
i exec: forever start -a -e erro.log -o out.log -l log.log app.js
then the console display:
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: app.js

forever not return, it still on ---> info: Forever processing file: app.js .
not return command line.

[julianduque]

Try with forever v0.11.x and let me know if it works.

[ndhuanhuan]

I tried v0.11.x.
I execute: forever start test.js.
then the console display:
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: test.js

Then I execute: forever list
it displays: no forever processes running

By the way, I'm using windows 8 and nodejs version v0.10.28.

[tdhsmith]

I want to chime in that I have this exact issue as well... I've been using forever successfully on Mac OS X and Linux Mint, but I haven't for the life of me figured out how to run it on Windows. (I was using Win 7 and node v0.10.25 at the time. I'll check it out again tonight with everything updated.)

EDIT: Looks like this could be merged with #550

[kothapalli]

Any update on this? Have same issue in windows 8. Tried installing older forever version v0.10.0 and seems it could start app but not the latest version.

[tdhsmith]

I know nothing about the code base, but the silent failure issues (this, #550, #562, #512?) and the "unhandled error" issues (#564, #557) seem related, seeing as the former happens to daemons and the latter to foreground processes.

So something is probably buggy with the way processes are being spawned...

[tdhsmith]

OK! It seems this is caused by an issue with forever-monitor. (foreversd/forever-monitor/issues/38, foreversd/forever-monitor/issues/35, foreversd/forever-monitor/issues/34)

The process-spawning logic tries to be clever and separate compound commands, but the command defaults to the current process' path, which on many Windows installs will be in "C:\Program Files". This gets spliced, and monitor.js tries to spawn the command "C:\Program", which fails.

There is a pull request waiting over at foreversd/forever-monitor/pull/65 that should fix the issue. (I tested my own fix, and it definitely addressed the surface issues; apps do, at the very least, run again)

[indexzero]

Related to #549 I think.

[indexzero]

forever just got a big update for Windows with 0.12.0. Try it again :-D

[sgb-io]

I'm experiencing this after upgrading to 0.12.2 on Ubuntu 12.04. It seems my process has spawned and works (forever list shows it running), but forever never returns the command line. It's breaking my deployments because the script gets stuck in the foreground.

I use a deploy user who has their own npm bin, so forever is installed there. When i installed as root, things work as expected (using root user is not an option).