Still facing ECONNRESET  errors

I know there was an active incident the other day, but i’m still facing build issues with this error: error (ERR_SOCKET_TIMEOUT)
9 Replies
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
Ryan The Temp
Ryan The Temp2y ago
project id: 928aabc2-402b-4ae5-b8d3-11bc579afda5 i’m on mobile, I don’t think i can paste the logs here 😦
Unknown User
Unknown User2y ago
Message Not Public
Sign In & Join Server To View
jr
jr2y ago
Hmm this does look like an actual npmjs network error. Can you give it another deploy?
Ryan The Temp
Ryan The Temp2y ago
i just did it i tried a few times with no avail looks like it’s not timing out now any idea what the root cause could be? seems sporadic.
jr
jr2y ago
Unsure. It is always the same dependency that it is timing out with too
Ryan The Temp
Ryan The Temp2y ago
hmm.
Ryan The Temp
Ryan The Temp2y ago
Seems like the ECONNRESET is back:
#12 79.15  WARN  GET https://registry.npmjs.org/@prisma/debug/-/debug-4.3.1.tgz error (ERR_SOCKET_TIMEOUT). Will retry in 1 minute. 1 retries left.

#12 79.25  WARN  GET https://registry.npmjs.org/@next/swc-linux-x64-musl/-/swc-linux-x64-musl-12.2.5.tgz error (ECONNRESET). Will retry in 10 seconds. 2 retries left.
#12 79.33  WARN  GET https://registry.npmjs.org/@next/swc-linux-x64-gnu/-/swc-linux-x64-gnu-12.2.5.tgz error (ECONNRESET). Will retry in 10 seconds. 2 retries left.

#12 79.35 Progress: resolved 1639, reused 0, downloaded 789, added 799

#12 79.52  WARN  GET https://registry.npmjs.org/@dnd-kit/core/-/core-6.0.5.tgz error (ECONNRESET). Will retry in 10 seconds. 2 retries left.

#12 79.90  WARN  GET https://registry.npmjs.org/@dnd-kit/modifiers/-/modifiers-6.0.0.tgz error (ECONNRESET). Will retry in 10 seconds. 2 retries left.

#12 81.93  ECONNRESET  aborted
#12 81.93
#12 81.93 Error: aborted
#12 81.93 at connResetException (node:internal/errors:711:14)
#12 81.93 at TLSSocket.socketCloseListener (node:_http_client:454:19)
#12 81.93 at TLSSocket.emit (node:events:525:35)
#12 81.93 at node:net:313:12
#12 81.93 at TCP.done (node:_tls_wrap:587:7)

#12 ERROR: executor failed running [/bin/bash -ol pipefail -c pnpm i --frozen-lockfile]: exit code: 1

-----
> [stage-0 8/10] RUN --mount=type=cache,id=s/cca21fe5-169c-4aba-8611-3023f4d263ed-/root/cache/pnpm,target=/root/.cache/pnpm pnpm i --frozen-lockfile:
-----
executor failed running [/bin/bash -ol pipefail -c pnpm i --frozen-lockfile]: exit code: 1

Error: Docker build failed
#12 79.15  WARN  GET https://registry.npmjs.org/@prisma/debug/-/debug-4.3.1.tgz error (ERR_SOCKET_TIMEOUT). Will retry in 1 minute. 1 retries left.

#12 79.25  WARN  GET https://registry.npmjs.org/@next/swc-linux-x64-musl/-/swc-linux-x64-musl-12.2.5.tgz error (ECONNRESET). Will retry in 10 seconds. 2 retries left.
#12 79.33  WARN  GET https://registry.npmjs.org/@next/swc-linux-x64-gnu/-/swc-linux-x64-gnu-12.2.5.tgz error (ECONNRESET). Will retry in 10 seconds. 2 retries left.

#12 79.35 Progress: resolved 1639, reused 0, downloaded 789, added 799

#12 79.52  WARN  GET https://registry.npmjs.org/@dnd-kit/core/-/core-6.0.5.tgz error (ECONNRESET). Will retry in 10 seconds. 2 retries left.

#12 79.90  WARN  GET https://registry.npmjs.org/@dnd-kit/modifiers/-/modifiers-6.0.0.tgz error (ECONNRESET). Will retry in 10 seconds. 2 retries left.

#12 81.93  ECONNRESET  aborted
#12 81.93
#12 81.93 Error: aborted
#12 81.93 at connResetException (node:internal/errors:711:14)
#12 81.93 at TLSSocket.socketCloseListener (node:_http_client:454:19)
#12 81.93 at TLSSocket.emit (node:events:525:35)
#12 81.93 at node:net:313:12
#12 81.93 at TCP.done (node:_tls_wrap:587:7)

#12 ERROR: executor failed running [/bin/bash -ol pipefail -c pnpm i --frozen-lockfile]: exit code: 1

-----
> [stage-0 8/10] RUN --mount=type=cache,id=s/cca21fe5-169c-4aba-8611-3023f4d263ed-/root/cache/pnpm,target=/root/.cache/pnpm pnpm i --frozen-lockfile:
-----
executor failed running [/bin/bash -ol pipefail -c pnpm i --frozen-lockfile]: exit code: 1

Error: Docker build failed
jr
jr2y ago
Link to deployment? We are investigating the issue. Everything on our side looks okay and we suspect an upstream issue with either our GCP network or with NPM. But we will keep you updated if we find anything