node.js v0.10.0 Issues (CentOS 6.3) #400
Comments
|
This is related to flatiron/flatiron#99. |
|
Same issue in OSX 10.7.5. Also hangs on forever stopall |
|
"LATENCY AND IDLE GARBAGE COLLECTION One of the toughest things to get right in a garbage collected language is garbage collection. In order to try to avoid excessive memory usage, Node used to try to tell V8 to collect some garbage whenever the event loop was idle. However, knowing exactly when to do this is extremely difficult. There are different degrees of "idleness", and if you get it wrong, you can easily end up spending massive amounts of time collecting garbage when you'd least expect. In practice, disabling the IdleNotification call yields better performance without any excessive memory usage, because V8 is pretty good at knowing when it's the best time to run GC. So, in v0.10, we just ripped that feature out. (According to another point of view, we fixed the bug that it was ever there in the first place.) As a result, latency is much more predictable and stable. You won't see a difference in the benchmarks as a result of this, but you'll probably find that your app's response times are more reliable." -Isaac Schlueter |
|
same here, forever list/stop seems not working anymore, need an update since the last one was 8 month ago:{ |
|
v0.10 on ubuntu 12.04 gives us this stack trace below before hanging. I mentioned Isaac's quote above because both Isaac and my machine are kinda saying the same thing in different words, am I wrong? $ forever list |
|
v10 on ubuntu 12.10 gives me the same issue as above: (node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit. |
|
Same issue on my Ubuntu 12.04 server forever list |
|
Ubuntu 12, node 0.10.0 - DIFFERENT errors First - during install, got a warning re When trying to Im upgrading from node 0.6 looking inside I could see `daemon.v0.6.19.node', but not 0.8.x or 0.10.x anybody? UPDATED: I had a bad installation problem, I'm back with everybody now... |
|
+1 I also have the problem on a ubuntu 12.04 machine. |
|
+1 ubuntu 12.04 server |
|
+1 ubuntu 12.10 server |
|
It looks like the project is gone 👎 |
|
Guess ill be using monit. Crap. I wanted to avoid that.
|
|
same here on ubuntu 12.04 desktop and server, worked one day, broken the next (after the 0.10.0 automatic update), frustrating! following error given twice, and process doesn't return to command line for any command other than start or help, requiring me to kill it by pid: (node) warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit. |
|
@legomind this happens because node is v0.10, so use nvm and install node v0.8. It's the temporary solution I found till this issue gets fixed :) |
|
We haven't upgraded to 0.10 yet. Sorry. Big update coming in the next month or so. A PR would be very welcomed. The underlying issue appears to be in Lazy through nssocket |
|
There is a pull request for lazy that fixes the problem at https://github.com/Nathanaela/node-lazy/tree/Cleanup |
|
So... I got sick of waiting. I started tracking down the source of the problems. Implemented the changes from Lazy. While it suppressed the error messages, that alone doesn't fix it. It still hangs like it did before. |
|
@MikeWills - Hmm, I just did a "npm install forever", copied my fixed version of "lazy.js" manually into the forever/node_module/nssocket/node_module/lazy folder (overritting the broken copy) and forever appears to be now working correctly. I did a forever start myscript, then in another console connected to my linux box did a forever list and forever stop 0. You might try deleting your entire npm cache; & forever, then doing a re-install of forever and then grabbing the lazy.js from my repository and manually sticking it into the nssockets/node_module/lazy folder... |
|
@NathanaelA it works! Thank you man. I tried to pin down the problem as well but gave up after getting to nssocket. FYI I didn't even reinstall anything, simply replaced lazy.js. Hope your pull request gets accepted soon... this fragile dependency hierarchy kinda troubles me. |
|
I still can't get it to work, but maybe I need to shut down my forever processes first before uninstalling and reinstalling. I'll test that when I have time. My problem is that |
|
@MikeWills yep - you need to manually kill all the currently running forever processes before using forever again |
|
@MikeWills see @kimptoc's comment #370 (comment) |
|
I got it working. After changing that file. I just rebooted :-P |
|
@NathanaelA Worked for me ! Thank you :) |
|
Update: The issue in lazy was fixed in 1.0.9 (see pkrumins/node-lazy@7bf31b8 and pkrumins/node-lazy#33 (comment)). |
|
For the record, I'm seeing this issue on node v0.10.1 on CentOS 5.8. Even after patching lazy I haven't been able to get everything to work properly, so I'm not 100% sure the lazy patch will fix forever for me. |
|
@adambrod lazy recently got updated, supposedly if you do an |
|
Or just remove forever and reinstall. That did the trick for me.
|
|
That works for me - thought it hadn't but the old forever version was still running. Thanks all. |
|
Reinstalling forever got me lazy 1.0.9 and I can use forever again with node 0.10. Time to close the issue or should the engines element in package.json perhaps be updated to reflect that node 0.10 is ok? |
|
Reinstalling forever got me lazy 1.0.9 and I can use forever again with node 0.10.3 — works perfect on ubuntu 12.04 LTS |
|
Changes in lazy.js worked for me under debian squeeze with v10.0.3. Thanks a lot! |
|
Worked for me after removing and re-adding forever. Thanks! On Tue, Apr 9, 2013 at 9:12 AM, schlowmo [email protected] wrote:
|
and others
Does forever work with node.js v0.10.0? I am trying to use forever with node.js v0.10.0 on CentOS 6.3 however when I run the server via the CLI and then check
forever listit seems to hang and never return a response to the console. My setup is explained below:I see the read me states "Remark: As of [email protected] processes will not automatically be available in forever.list(). In order to get your processes into forever.list() or forever list you must instantiate the forever socket server:" but does this apply when using forever via. the CLI? If so how would the example script below be modified?
Cent OS 6.3 Install node.js Rackspace Cloud Server
yum install openssl-devel gcc-c++ make
cd /usr/local/src
wget http://nodejs.org/dist/node-latest.tar.gz
tar zxvf node-latest.tar.gz
cd node-v0.10.0
make
make install
Check Node.js version
node --version
Open default iptables firewall port 80
vi /etc/sysconfig/iptables
Open Port 80
/sbin/service iptables restart
/sbin/service iptables save
Install node.js forever
npm install forever -g
Create Example node.js server
var http = require('http');
http.createServer(function (req, res) {
res.writeHead(200, {'Content-Type': 'text/plain'});
res.end('Hello World\n');
}).listen(80);
console.log('Server running on port 80');
Run server using forever
forever start example.js
List forever instances
forever list
Seems to hang at this step
The text was updated successfully, but these errors were encountered: