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

forever hangs executing actions #370

Closed
inolen opened this issue Jan 6, 2013 · 22 comments
Closed

forever hangs executing actions #370

inolen opened this issue Jan 6, 2013 · 22 comments

Comments

@inolen
Copy link

inolen commented Jan 6, 2013

Chatted with coderarity in IRC earlier and he repro'd easily as well and asked I write up a report.

On node 0.9.5 (on Debian) I can start a script, however, every subsequent action (e.g. list, stopall) hangs indefinitely.

I thought it was perhaps due to me running forever as non-root, however he ran into the same problems as root.

@mmalecki
Copy link
Contributor

mmalecki commented Jan 8, 2013

This is most likely related to streams2.

@tylerdavis
Copy link

I'm also running in to this on Ubuntu 12.04.1 LTS.

Starting the script works fine, but forever list hangs indefinitely. Let me know if there is any other information I can provide.

@wasche
Copy link

wasche commented Feb 1, 2013

I am running into the same problem with node 0.9.8 and forever 0.10.0 on ubuntu 12.10. However, I installed node 0.8.18 and that seems to be working fine (after I killed all running instances of forever.)

@kemitchell
Copy link

Same problem:

  • forever 0.10.0
  • Debian 6.0.1
  • node 0.9.7

@nfour
Copy link

nfour commented Feb 16, 2013

Same issue. Can't really use Forever like this.

Node 0.9.10, CentOS 6.3 x64

@vanthome
Copy link
Contributor

Same on Gentoo with node 0.9.9

@cjroth
Copy link

cjroth commented Feb 18, 2013

Same with Ubuntu 12.10, Node.js v0.9.10-pre.

@guilala
Copy link

guilala commented Feb 18, 2013

Same here with node 0.9.9 and forever 0.10.0 on Gentoo amd64, also on Gentoo on Amazon elastic cloud. I wish someone got assigned to this issue :-/...

@pepve
Copy link

pepve commented Mar 8, 2013

Same issue here with Node 0.9.12 and Forever 0.10.0.

@jcw
Copy link

jcw commented Mar 13, 2013

Sounds like the same issue as #392.

@Southern
Copy link

Okay, guys. It seems that all of these errors are stemming from the flatiron CLI plugin, which has had problems with Node since version 0.9.5 was released with streams2 as @mmalecki mentioned above. The flatiron project is being worked on for compatibility with Node 0.10.0 and will be updated in this repository as soon as possible. Numerous things that Nodejitsu is based on (such as jitsu) use flatiron as well, so this CLI fix is on our priority list.

@tlhunter
Copy link

Bump: Debian Linode

forever 0.10.0
node 0.10.0

@legomind
Copy link

any workarounds?

@kimptoc
Copy link

kimptoc commented Mar 19, 2013

As a workaround - this works for me :)
stop node apps:

killall /usr/bin/nodejs

list running apps:

ps -leaf | grep node

Crude, I know.

@legomind
Copy link

Guess it will have to do. thnx.

@crshumate
Copy link

Still seeing this in node 0.10.32 and forever 0.11.1
MaxOSX

@twilco
Copy link

twilco commented Dec 12, 2014

I'm also having troubles with commands hanging. forever logs app.js -f hangs indefinitely. Forever also seems to be ending processes randomly, but that's besides this issue.

Lubuntu 14.04

@iMoses
Copy link

iMoses commented Jun 4, 2015

I'm suffering from the same problem on Ubuntu 14.04, using Forever 0.14.1 on nodejs 0.10.25
Forever will hang on stop commands

@EwanValentine
Copy link

Getting the same thing. It's unusable.

@1e4
Copy link

1e4 commented Nov 30, 2018

Just thought I would poke in and say I too have the same issue several years later on Ubuntu, I can run a script, but any other command simply hangs.

@iMoses
Copy link

iMoses commented Sep 25, 2020

It's 2020.. why is this still an issue?

I believe that if you are still using this library in 2020 you are definitely doing something wrong. The nodejs ecosystem has come a long way since then and this tool is pretty much obsolete when it comes to best practices in the industry, as well as effectivity as this issue suggests..

@kibertoad
Copy link
Contributor

Yes. Please consider using pm2 or nodemon.

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

No branches or pull requests