-
Notifications
You must be signed in to change notification settings - Fork 30.6k
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 emit 'error' twice #20418
Comments
I agree, if Can you provide the information from the issue template? |
I don't have a reproducible case. Got this from the logs in our production servers. |
I think it´s a After |
This error does not occur in node 9. Just in node 10. |
Node 10: ERROR: upgrade failed
proxyName: "nxt"
req: {
"method": "GET",
"url": "/deepstream"
}
err: {
"type": "Error",
"message": "connect ECONNREFUSED 127.0.0.1:6020",
"stack":
Error: connect ECONNREFUSED 127.0.0.1:6020
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1161:14)
"errno": "ECONNREFUSED",
"code": "ECONNREFUSED",
"syscall": "connect",
"address": "127.0.0.1",
"port": 6020,
"statusCode": 503
}
ERROR: uncaught exception
err: {
"type": "Error",
"message": "read ECONNRESET",
"stack":
Error: read ECONNRESET
at TLSWrap.onread (net.js:659:25)
"errno": "ECONNRESET",
"code": "ECONNRESET",
"syscall": "read"
} Node 9: ERROR: session error
err: {
"type": "Error",
"message": "read ECONNRESET",
"stack":
Error: read ECONNRESET
at TLSWrap.onread (net.js:602:25)
"errno": "ECONNRESET",
"code": "ECONNRESET",
"syscall": "read"
}
ERROR: upgrade failed
proxyName: "nxt"
req: {
"method": "GET",
"url": "/deepstream"
}
err: {
"type": "Error",
"message": "connect ECONNREFUSED 127.0.0.1:6020",
"stack":
Error: connect ECONNREFUSED 127.0.0.1:6020
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1174:14)
"errno": "ECONNREFUSED",
"code": "ECONNREFUSED",
"syscall": "connect",
"address": "127.0.0.1",
"port": 6020,
"statusCode": 503
} |
@ronag what did you end up finding out? |
@apapirovski: the behaviour is different between node 9 and 10. Not quite sure how. I was basically doing things wrong. I didn't expect to get an |
I'm getting
error
emitted twice from the same object?Version: v10.0.0
Platform: Darwin Roberts-MacBook-Pro-2.local 17.5.0 Darwin Kernel Version 17.5.0: Mon Mar 5 22:24:32 PST 2018; root:xnu-4570.51.1~1/RELEASE_X86_64 x86_64
and
Seems like a bug?
The text was updated successfully, but these errors were encountered: