When using multi-node with node v0.5.10, I receive the following error:
throw e; // process.nextTick error, or 'error' event on first tick
Error: No such module
at Object. (/lib/multi-node/multi-node.js:5:23)
at Module._compile (module.js:432:26)
at Object..js (module.js:450:10)
at Module.load (module.js:351:31)
at Function._load (module.js:310:12)
at Array. (module.js:470:10)
at EventEmitter._tickCallback (node.js:194:26)
Which is referring to netBinding = process.binding("net");
netBinding = process.binding("net");
I get this too.
I found this thread: joyent/node#1373.
As one of the commenters said "The error is actually just from attempting process.binding('net'), a builtin only available on posix atm.".
So probably you are trying to use this module on windows as me, thats why it pops up.
As far as I am aware, binding("net") was actually removed in v0.5 and later. Anyway, I'm using the cluster module that is included with the node core to do the things that multi-node did. If you need a solution, I have posted a gist of my SimpleCluster module: https://gist.github.com/1510680
is there any solution for this?
The solution I went with was to use node's cluster module (http://nodejs.org/docs/latest/api/cluster.html). I created an easy to use wrapper as seen in https://gist.github.com/1510680. But as for a solution to fixing multi-node, I don't know. Sorry.
Thank you, but I'm looking for the fix in multi-node.
I have also the same problem, but I am new to this and I do not know how to install the simplecluster solution which is at #14
I am very new unfortunately, and it would mean so much to me if someone could give me a dummy-prove step by step guide to 'install' this module ( I have never installed any module before, only recently stumbled into the world of node js and still exploring ) Help is appreciated and thanks so much
@bendy00123 : I just replaced the code in node_modules/webworker/lib/webworker.js with the code from wankdanker https://gist.github.com/1510680. (I kept the name webworker.js). Worked for me, but i think this is not a waterproof solution. Maybe you have to change more in your code...
@wankdanker Thanks man.
I also had the issue when I first tried with it with current latest nodejs version. So, as there isn't any alternative around, I have created my own. I just recently published in github here: clustered-node , which work pretty much same way as this. Hope that may help you. Thanks.
still having this issue in 2015