Closed brettkiefer closed 13 years ago
Reproduced on Ubuntu Linux and FreeBSD 8.2
still an issue? I had this with the tests if I had old socket files laying around, but I'm pretty sure node unlink()s them first anyway
oh my bad I think I know what it is
Yes, I'm still seeing this in 0.6.7.
the workers were trying to bind to the same client path due to a typo using the master's PID. Though that should be irrelevant now because I just removed the client socket all together it's not needed right now
That does the trick for me.
Actually, wait, when I install 0.6.8 clean and run 'node test.js' , I get this error:
Error in unix_dgram bind of test/cluster.51810.server.sock
Error: ENOENT, No such file or directory
at dgram.js:125:19
warning - kill(SIGKILL)
Error: ENOENT, No such file or directory
at dgram.js:125:19
ignore test.js
, it should be npmignored, it's just a file I use to test arbitrary things, try make test
(or just make
)
Ok. Yep, looks good in actual use. Thanks!
Since checkin b72287be98a7e32394533525b9f2f91cc78ece03 (to close #126), it looks like starting Cluster with more than a few workers causes some to die and restart.
Repro: npm install cluster cd node_modules/cluster edit test.js to start 20 workers instead of 4 node test.js
Expected: 20 workers start
Observed: Several workers start, then a bunch fail, and the server shuts down: