-
Notifications
You must be signed in to change notification settings - Fork 946
-
Notifications
You must be signed in to change notification settings - Fork 946
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
Comments
This is most likely related to |
I'm also running in to this on Ubuntu 12.04.1 LTS. Starting the script works fine, but |
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.) |
Same problem:
|
Same issue. Can't really use Forever like this. Node 0.9.10, CentOS 6.3 x64 |
Same on Gentoo with node 0.9.9 |
Same with Ubuntu 12.10, Node.js v0.9.10-pre. |
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 :-/... |
Same issue here with Node 0.9.12 and Forever 0.10.0. |
Sounds like the same issue as #392. |
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 |
Bump: Debian Linode
|
any workarounds? |
As a workaround - this works for me :)
list running apps:
Crude, I know. |
Guess it will have to do. thnx. |
Still seeing this in node 0.10.32 and forever 0.11.1 |
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 |
I'm suffering from the same problem on Ubuntu 14.04, using Forever 0.14.1 on nodejs 0.10.25 |
Getting the same thing. It's unusable. |
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. |
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.. |
Yes. Please consider using pm2 or nodemon. |
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.
The text was updated successfully, but these errors were encountered: