Error with cluster.js and dgram.js

86 views
Skip to first unread message

Jacob Alheid

unread,
Jun 11, 2014, 3:33:02 PM6/11/14
to nod...@googlegroups.com
So I'm getting the following error stack with v0.10.15:

TypeError
Cannot set property 'lookup' of undefined

dgram.js ? in replaceHandle at line 147
dgram.js ? in null.<anonymous> at line 198
cluster.js ? in Object.109:1002 at line 587
cluster.js ? in handleResponse at line 171
cluster.js ? in respond at line 192
cluster.js ? in handleMessage at line 202
events.js ? in process.EventEmitter.emit at line 117
child_process.js ? in handleMessage at line 318
child_process.js ? in null.<anonymous> at line 392
child_process.js ? in process.handleConversion.dgram.Native.got at line 171
child_process.js ? in process.<anonymous> at line 391
events.js ? in process.EventEmitter.emit at line 117
child_process.js ? in handleMessage at line 318
child_process.js ? in Pipe.channel.onread at line 343

As far as I can tell this is happening because in cluster.handleMessage (202), respond (192) is being called with empty arguments, which results in dgram.replaceHandle being called with an empty (null) handle further down the line.

It appears that in the master branch (and 0.11 releases) cluster.js has been totally rewritten - the offending code no longer exists - so my questions are: does anyone know if this has been fixed in 0.10.28? (I see a slight change between 0.10.15 and 0.10.28 but can't grok if it fixes this) Should I submit a bug report for the 0.10 line or just let it go? Is there any way to fix this so I don't keep getting errors? (Maybe a handler on an error event emitter somewhere? Not sure where to attach that though.)


Nick Payne

unread,
Aug 4, 2014, 12:10:39 PM8/4/14
to nod...@googlegroups.com
Hi Jacob,

I've just run into this error myself using node 0.10.26. Did you ever find a suitable solution, or the root cause? Yours is the only mention I can find of this issue occurring other than the issue I've just experienced. For what it's worth in my situation it appears to be related to excessive load (which also triggered other errors, e.g. EMFILE) although investigations are in the very early stages at the moment.

Nick
Reply all
Reply to author
Forward
0 new messages