Databases
StackOverflow2013
Postsdbo
PONode.js, Cygwin and Socket.io walk into a bar... Node.js throws ENOBUFS and everyone dies
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PONode.js, Cygwin and Socket.io walk into a bar... Node.js throws ENOBUFS and everyone dies
    primarykey
    data
    text
    <p>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 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). </p> <p>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 <code>nameserver x.x.x.x</code> in my <code>/etc/resolv.conf</code> to the internal DNS. I've also added <code>nameserver 8.8.8.8</code> in addition. I'm not sure what else to check, but would be grateful of any help.</p> <h1>In <code>node.exe.stackdump</code></h1> <pre><code>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 </code></pre> <h1>Node Output:</h1> <pre><code> 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) </code></pre> <h1>EDIT</h1> <p>I'm hitting an LDAP server using <code>http.createClient</code> 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 <a href="https://github.com/ry/node/blob/v0.3.1/src/node_net.cc#L368" rel="noreferrer">to include <code>&amp;&amp; errno != ENOBUFS</code></a> 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 <code>/etc/resolv.conf</code> to the DNS servers that are being applied to the host machine. Not sure if this is part of the issue?</p> <h1>EDIT 2</h1> <p>Here's some output from <code>gdb --args ./node_g --debug ../myscript.js</code>. I'm not sure if this is related to ENOBUFS, however, as it seems to be disconnecting immediately after connection with Socket.io</p> <pre><code> [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&lt;v8::Value&gt;, 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) </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USA Wizard Did It
    1. USA Wizard Did It
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PONode.js, Cygwin and Socket.io walk into a bar... Node.js throws ENOBUFS and everyone dies
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PONode.js, Cygwin and Socket.io walk into a bar... Node.js throws ENOBUFS and everyone dies
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PONode.js, Cygwin and Socket.io walk into a bar... Node.js throws ENOBUFS and everyone dies
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf you don't post the code itself, well, it might be a little hard to guess what the problem is.
      singulars
      1. PONode.js, Cygwin and Socket.io walk into a bar... Node.js throws ENOBUFS and everyone dies
      1. USPointy
    2. COCode isn't the problem. I'm updating the question with more info.
      singulars
      1. PONode.js, Cygwin and Socket.io walk into a bar... Node.js throws ENOBUFS and everyone dies
      1. USA Wizard Did It
    3. COThe stack trace isn't too useful without symbol names. Maybe run node under gdb and get a meaningful stack trace?
      singulars
      1. PONode.js, Cygwin and Socket.io walk into a bar... Node.js throws ENOBUFS and everyone dies
      1. USohmantics
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload