This repository has been archived by the owner. It is now read-only.

Resource temporarily unavailable when connecting to net.Server #4425

Closed
kurteknikk opened this Issue Dec 17, 2012 · 4 comments

Comments

Projects
None yet
3 participants

I have a net.Server listening on a UNIX socket handling 100+ connections per second.
Sometimes the client gets a "Resource temporarily unavailable" error.

Running linux 3.0.0-16-server with:
net.unix.max_dgram_qlen=1024
net.core.somaxconn=1024

Maybe its relevant... If it happens it happens for a second or so, and then for a whole hour it doesn't happen anymore.

I don't expect this error since node is non-blocking.

Member

bnoordhuis commented Dec 17, 2012

Sometimes the client gets a "Resource temporarily unavailable" error.

That's EAGAIN. Is that when connecting, reading or writing? If you have a test case, that would help.

This is happening on connect, the client is written in PHP this is a sample code:

$mySocket = stream_socket_client("/tmp/myServer", $errno, $errstr, 1);
if ($errno || !$mySocket) print "mySocket start error: $errno $errstr";

#Result is: "mySocket start error: 32 Resource temporarily unavailable"

Member

bnoordhuis commented Dec 18, 2012

What makes you think the issue is on the side of node.js when it's PHP that's reporting the error?

no update. considering non-issue.

@trevnorris trevnorris closed this Jul 26, 2013

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.