(node) Hit max file limit. Increase "ulimit - n"

[DaveM]

Ran into this error on os x snow leopard.
Problem was created by faulty browser logic with repeatedly connected.
Does raise a concern about the number of concurrent connections though.
(as osx default is 266 file descriptors, unless you increase with ulimit -n)

--------

(node) Hit max file limit. Increase "ulimit - n"

events.js:23
        throw arguments[1]; // Unhandled 'error' event
                       ^
Error: ECONNREFUSED, Could not contact DNS servers
    at dns.js:173:15
    at Object.lookup (dns.js:169:11)
    at Client.connect (net.js:689:20)
    at Client._ensureConnection (http.js:1596:10)
    at Client._cycle (http.js:1586:14)
    at Client.request (http.js:1620:8)
    at /usr/local/lib/node/.npm/pool/

0.4.1/package/main.js:55:26
    at Pool.getClient (/usr/local/lib/node/.npm/pool/0.4.1/package/
main.js:25:16)
    at Pool.request (/usr/local/lib/node/.npm/pool/0.4.1/package/
main.js:54:8)
    at Object.proxyRequest (/usr/local/lib/node/.npm/http-proxy/0.3.1/
package/lib/node-http-proxy.js:191:7)

[Steven Soroka]

Sure, but that wouldn't limit server-side connections, though, right?

[DaveM]

the ulimit error was thrown by node.js, ie the server.
(it's running on osx)