Skip to content
Latchkey LogoLatchkey home
EnglishPortuguês日本語
Start Free

Latchkey Learn

Runner failures Latchkey repairs

The failures that are about the runner and the network, not your code. Each page reproduces the failure on a Latchkey runner and shows what the runner does about it.

Start here four stops, in order

  1. 01Exit code 143Out of memory
  2. 02Free disk space on a runnerDisk full
  3. 03"command not found", exit 127Missing tools
  4. 04Pull-through cache for CIRegistries and networks

Contents 6 sections · 54 entries

Out of memory 5 entries

Exit 137, heap limits, kernel OOM.

  1. 1.1Exit code 143
  2. 1.2Exit code 137
  3. 1.3"JavaScript heap out of memory"
  4. 1.4"OutOfMemoryError: Java heap space"
  5. 1.5"MemoryError"

Disk full 2 entries

ENOSPC, inodes, freeing space.

  1. 2.1Free disk space on a runner
  2. 2.2"No space left on device"

Missing tools 2 entries

Exit 127, shared libraries.

  1. 3.1"command not found", exit 127
  2. 3.2"error while loading shared libraries"

Registries and networks 31 entries

Timeouts, 5xx, rate limits, DNS.

  1. 4.1Pull-through cache for CI
  2. 4.2"Hash Sum mismatch"
  3. 4.3"ThrottlingException"
  4. 4.4"Could not fetch specs from"
  5. 4.5"Cache service responded with 503"
  6. 4.6"spurious network error (3 tries remaining)"
  7. 4.7"curl error 6 while downloading"
  8. 4.8"Could not get lock /var/lib/dpkg/lock"
  9. 4.9"toomanyrequests"
  10. 4.10"net/http: TLS handshake timeout"
  11. 4.11"EAI_AGAIN"
  12. 4.12"Connection reset by peer"
  13. 4.13"ERR_PNPM_FETCH_503"
  14. 4.14"failed to reserve cache"
  15. 4.15"RESOURCE_EXHAUSTED" from gcloud
  16. 4.16"TOOMANYREQUESTS" from ghcr.io
  17. 4.17"API rate limit exceeded"
  18. 4.18"i/o timeout" from GOPROXY
  19. 4.19"another operation (install/upgrade/rollback) is in progress"
  20. 4.20"Unable to connect to the server"
  21. 4.21"Could not transfer artifact"
  22. 4.22"npm ERR! network"
  23. 4.23"error NU1301"
  24. 4.24"ReadTimeoutError: HTTPSConnectionPool"
  25. 4.25"Failed to download Chrome for Testing"
  26. 4.26"All attempts to connect" and "HTTP 000"
  27. 4.27"RPC failed; curl 56"
  28. 4.28"Failed to query available provider packages"
  29. 4.29"the Cypress binary is missing"
  30. 4.30"Failed to fetch" and "Request failed after"
  31. 4.31"There appears to be trouble"
Explore other topics
GitHub Actions runners comparedEvery managed runner vendor, priced and benchmarked side by side. GitHub Actions costWhat Actions really costs, and how to cut it. GitHub Actions workflow errorsWorkflow, YAML, permissions and artifact errors, diagnosed and fixed. Docker in CI: Registry, Build & RuntimeRegistry, runtime and build errors on CI runners. Faster GitHub ActionsCaching, parallelism and cold starts, measured. CI for coding agentsGive your coding agent a runner.