Error: ENOBUFS, No buffer space available

[Robert]

I'm hoping someone here can help me out, I'm not having much luck
figuring this out myself. I'm running node.js version 0.3.1 (I get
ENOBUFS on v0.2.6 as well) on Cygwin. I'm using Connect and Socket.io.
I seem to be having some random problems with DNS or something, I
haven't quite figured it out. The end result is that I the server is
running fine, but when a browser attempts to connect to it the initial
HTTP Request works, Socket.io connects, and then the server dies
(output below).

I don't think it has anything to do with the HTTP request because the
server gets a lot data posted to it, and it was receiving requests and
responding up until my connection that killed it. I've googled around
and the closest thing I've found is DNS being set improperly. It's a
network program meant to run only on an internal network, so I've set
the nameserver x.x.x.x in my /etc/resolv.conf to the internal DNS.
I've also added nameserver 8.8.8.8 in addition. I'm not sure what else
to check, but would be grateful of any help.

In node.exe.stackdump

Exception: STATUS_ACCESS_VIOLATION at eip=610C51B9
eax=00000000 ebx=00000001 ecx=00000000 edx=00000308 esi=00000000
edi=010FCCB0
ebp=010FCAEC esp=010FCAC4 program=\\?\E:\cygwin\usr\local\bin
\node.exe, pid 3296, thread unknown (0xBEC)
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
010FCAEC 610C51B9 (00000000, 00000000, 00000000, 00000000)
010FCBFC 610C5B55 (00000000, 00000000, 00000000, 00000000)
010FCCBC 610C693A (FFFFFFFF, FFFFFFFF, 750334F3, FFFFFFFE)
010FCD0C 61027CB2 (00000002, F4B994D5, 010FCE64, 00000002)
010FCD98 76306B59 (00000002, 010FCDD4, 763069A4, 00000002)
End of stack trace
Node Output:

node.js:50
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: ENOBUFS, No buffer space available
at doConnect (net.js:642:19)
at net.js:803:9
at dns.js:166:30
at IOWatcher.callback (dns.js:48:15)

I'm hitting an LDAP server using http.createClient immediately after a
client connects to get information, and that seems to be where the
problem is that is causing ENOBUFS. I've edited the source to include
&& errno != ENOBUFS which now prevents the server from dying, however
now the LDAP request isn't working. I'm not sure what the problem is
that would cause that though. As I mentioned this is an internal only
application, so I set the DNS servers in /etc/resolv.conf to the DNS
servers that are being applied to the host machine. Not sure if this
is part of the issue?


Here's some output from gdb --args ./node_g --debug ../myscript.js.
I'm not sure if this is related to ENOBUFS, however, as it seems to be
disconnecting immediately after connection with Socket.io

[New thread 672.0x100]
Error: dll starting at 0x76e30000 not found.
Error: dll starting at 0x76250000 not found.
Error: dll starting at 0x76e30000 not found.
Error: dll starting at 0x76f50000 not found.
[New thread 672.0xc90]
[New thread 672.0x448]
debugger listening on port 5858
[New thread 672.0xbf4]
14 Jan 18:48:57 - socket.io ready - accepting connections
[New thread 672.0xed4]
[New thread 672.0xd68]
[New thread 672.0x1244]
[New thread 672.0xf14]
14 Jan 18:49:02 - Initializing client with transport "websocket"
assertion "b[1] == 0" failed: file "../src/node.cc", line 933,
function: ssize_t
node::DecodeWrite(char*, size_t, v8::Handle<v8::Value>,
node::encoding)

Program received signal SIGABRT, Aborted.
0x7724f861 in ntdll!RtlUpdateClonedSRWLock ()
from /cygdrive/c/Windows/system32/ntdll.dll
(gdb) backtrace
#0 0x7724f861 in ntdll!RtlUpdateClonedSRWLock ()
from /cygdrive/c/Windows/system32/ntdll.dll
#1 0x7724f861 in ntdll!RtlUpdateClonedSRWLock ()
from /cygdrive/c/Windows/system32/ntdll.dll
#2 0x75030816 in WaitForSingleObjectEx ()
from /cygdrive/c/Windows/syswow64/KernelBase.dll
#3 0x0000035c in ?? ()
#4 0x00000000 in ?? ()
(gdb)


I posted this on stackoverflow as well (
http://stackoverflow.com/questions/4658104/node-js-cygwin-and-socket-io-walk-into-a-bar-node-js-throws-enobufs-and-every
)

[Guido Tapia]

I'm getting this also with v0.3.1 on cygwin / Win 7 Enterprise.

This started just when I started using fs.readdirSync but now I cannot
run any node code at all. Here is the dump contents:

Exception: STATUS_ACCESS_VIOLATION at eip=610C51B9
eax=00000000 ebx=00000001 ecx=00000000 edx=0000016C esi=00000000
edi=1A3FCCB0
ebp=1A3FCAEC esp=1A3FCAC4 program=\\?\C:\dev\cygwin\Cygwin.bat, pid
2528, thread unknown (0x884)

cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args

1A3FCAEC 610C51B9 (00000000, 00000000, 00000000, 00000000)
1A3FCBFC 610C5B55 (00000000, 00000000, 00000000, 00000000)
1A3FCCBC 610C693A (FFFFFFFF, FFFFFFFF, 75D734F3, FFFFFFFE)
1A3FCD0C 61027CB2 (00000002, C4A295F5, 1A3FCE64, 00000002)
1A3FCD98 766F6B59 (00000002, 1A3FCDD4, 766F69A4, 00000002)
End of stack trace


Did you have any luck fixing this Robert?

Thanks All

Guido

> I posted this on stackoverflow as well (http://stackoverflow.com/questions/4658104/node-js-cygwin-and-socket-...
> )