Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Socket Hang up exception #377

Closed
subnetmarco opened this issue Mar 2, 2013 · 2 comments
Closed

Socket Hang up exception #377

subnetmarco opened this issue Mar 2, 2013 · 2 comments

Comments

@subnetmarco
Copy link
Contributor

I've found the following error in my logs. Unfortunately I cannot provide a meaningful context, and I'm not really sure why it happened, so just in case I report it here. Feel free to close this issue if it leads to nowhere.

at createHangUpError (http.js:1360:15)
at ServerResponse.OutgoingMessage._writeRaw (http.js:507:26)
at ServerResponse.OutgoingMessage._send (http.js:476:15)
at ServerResponse.OutgoingMessage.write (http.js:749:16)
at ServerResponse.module.exports.response.write (/usr/lib/node_modules/mashape-proxy/lib/middleware/response-headers.js:15:11)
at IncomingMessage.ondata (/usr/lib/node_modules/mashape-proxy/node_modules/http-proxy/lib/node-http-proxy/http-proxy.js:294:27)
at IncomingMessage.EventEmitter.emit (events.js:96:17)
at IncomingMessage._emitData (http.js:359:10)
at HTTPParser.parserOnBody [as onBody] (http.js:123:21)
at Socket.socketOnData [as ondata] (http.js:1472:20)
at TCP.onread (net.js:404:27)
@shimondoodkin
Copy link

look on squence of events from bottom up.
seems like it is write on a closed socket

@indexzero
Copy link
Contributor

The backend you are proxying to is not running.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants