You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The application gets resets which lead to a ECONNRESET.
I couldn't locate the cause neither in the layer's nor in the agent's logs, so I think maybe the RSTs originate with the layer (the layer drops the connection early and a RST is sent to the app on the mirror stream).
Steps to Reproduce
It only reproduced on the CI, and only in twice out of thousands of outgoing requests.
Triggering the CI on this request #553 is almost guaranteed to lead to an error at some point, but you would probably have to try it a couple of times until you get this specific error (or change it in some way to keep running the test after one try has failed, like a simple way would be to duplicate the e2e job, so you get 1 error per job.)
Backtrace
Type A:
Error: Client network socket disconnected before secure TLS connection was established
at connResetException (internal/errors.js:639:14)
at TLSSocket.onConnectEnd (_tls_wrap.js:1570:19)
at TLSSocket.emit (events.js:412:35)
at endReadableNT (internal/streams/readable.js:1333:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21) {
code: 'ECONNRESET',
path: null,
host: 'www.youtube.com',
port: 443,
localAddress: undefined
}
Type B:
Error: socket hang up
at connResetException (internal/errors.js:639:14)
at TLSSocket.socketOnEnd (_http_client.js:499:23)
at TLSSocket.emit (events.js:412:35)
at endReadableNT (internal/streams/readable.js:1333:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21) {
code: 'ECONNRESET'
}
Bug Description
The application gets resets which lead to a
ECONNRESET
.I couldn't locate the cause neither in the layer's nor in the agent's logs, so I think maybe the RSTs originate with the layer (the layer drops the connection early and a RST is sent to the app on the mirror stream).
Steps to Reproduce
It only reproduced on the CI, and only in twice out of thousands of outgoing requests.
Triggering the CI on this request #553 is almost guaranteed to lead to an error at some point, but you would probably have to try it a couple of times until you get this specific error (or change it in some way to keep running the test after one try has failed, like a simple way would be to duplicate the e2e job, so you get 1 error per job.)
Backtrace
Type A:
Type B:
Error: socket hang up at connResetException (internal/errors.js:639:14) at TLSSocket.socketOnEnd (_http_client.js:499:23) at TLSSocket.emit (events.js:412:35) at endReadableNT (internal/streams/readable.js:1333:12) at processTicksAndRejections (internal/process/task_queues.js:82:21) { code: 'ECONNRESET' }
Relevant Logs
No response
Your operating system and version
Ubuntu 20.04.5 LTS
Local process
node
Local process version
14
Additional Info
No response
MET-11
The text was updated successfully, but these errors were encountered: