EINVAL error

[yjh0502]

I'm now building nodejs socket server, and this error kills my server.

node.js:116
        throw e; // process.nextTick error, or 'error' event on first tick
        ^
Error: EINVAL, Invalid argument
    at doConnect (net.js:530:19)
    at net.js:696:9
    at dns.js:175:34
    at IOWatcher.callback (dns.js:53:15)

I also added 'error' handler to my server, but it doesn't works for me.

[tj]

ubuntu? (curious)

[yjh0502]

Yes. Ubuntu 10.10.
On Mar 19, 2011 12:28 AM, "visionmedia" <
reply@reply.github.com>
wrote:

ubuntu? (curious)

Reply to this email directly or view it on GitHub:
#804 (comment)

[tj]

interesting... people keep having this with issue with cluster on Ubuntu, perhaps it really is not cluster's fault, I still haven't had time to look. Can you post a gist of your code? or at least enough to reproduce this error

[yjh0502]

var tls = require('tls'),
    fs = require('fs'),
    crypto = require('crypto');

var options = {
    key: fs.readFileSync('cert/key.pem'),
    cert: fs.readFileSync('cert/cert.pem')
};

var server = tls.createServer(options, function(s) {
});

server.on('error', function(e) {
    console.log('server down suddenly: ' + e);
    server.close();
    server.listen(port);
});

server.listen(10000);

[bkw]

closed by accident? Please reopen. Also see LearnBoost/cluster#47

[nergal]

same problem on:
Linux dev.omg.local 2.6.18-164.15.1.el5.028stab068.9 #1 SMP Tue Mar 30 18:07:38 MSD 2010 x86_64 x86_64 x86_64 GNU/Linux

node v0.4.6, no any server features used

[curtisc]

I'm seeing the same issue intermittently on 0.4.6 on Ubuntu 10.04.2. I haven't found the exact conditions that cause it, I just see it in my logs occasionally. I'm not using cluster, so I don't think it's a cluster issue. Will post if I can catch exactly why it happens

[demian85]

Similar problem here

net.js:730
          bind(self.fd, 0, local);
          ^
Error: EINVAL, Invalid argument
    at net.js:730:11
    at dns.js:196:34
    at IOWatcher.callback (dns.js:74:15)

Node 0.4.9 / Debian

[bnoordhuis]

Can anyone confirm / deny this happening on master?

Note to self: possibly a race between listen() and accept().

[yjh0502]

Just a workaround, but sometimes (not always) sudden death of a process can be prevent by adding 'error' handler before opening socket. If there is no error handler, nodejs process dies without recover, but if a error handler is attached, the error is caught by handler and could be handled safely. It could be applied to not only a socket connection, but all kinds of network-related functions like TLS or HTTP.

[Somebi]

Same error here on Virtual Machine Ubuntu OS while crawling websites

[trevnorris]

I haven't been able to reproduce this issue on v0.8.15.

[bnoordhuis]

I can't find the commit but this was fixed late in v0.4's life cycle. Closing.

[vikrama]

net.js:157
    this._handle.open(options.fd);
                 ^
Error: EINVAL, invalid argument

v0.10.20 on cygwin

[trevnorris]

@vikrama Have a reproducible test case? Also, I don't think we officially support cygwin anymore now that Node has native Windows support.