Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

cache service responded with 503

See original GitHub issue

Post job cleanup.
/bin/tar --posix --use-compress-program zstd -T0 -cf cache.tzst -P -C /home/runner/work/enroll/enroll --files-from manifest.txt
Warning: uploadChunk (start: 67108864, end: 100663295) failed: Cache service responded with 503
/home/runner/work/_actions/actions/cache/v2/dist/save/index.js:3136
                        throw new Error(`Cache upload failed because file read failed with ${error.message}`);
                        ^

Error: Cache upload failed because file read failed with ESPIPE: invalid seek, read
    at ReadStream.<anonymous> (/home/runner/work/_actions/actions/cache/v2/dist/save/index.js:3136:31)
    at ReadStream.emit (events.js:210:5)
    at internal/fs/streams.js:167:12
    at FSReqCallback.wrapper [as oncomplete] (fs.js:470:5)

Issue Analytics

State:
Created 3 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

ntrifunoviccommented, Oct 30, 2020

I have managed to get this to work by adding upload-chunk-size: 1000000.

upload-chunk-size should have better documentation and error message might refer to it 😃

0reactions

dhadkacommented, Oct 30, 2020

@ntrifunovic Filed https://github.com/actions/cache/issues/447 with your suggestion to improve the documentation and/or error message.

Top Results From Across the Web

getCacheEntry failed: Cache service responded with 503 ...

Just got this error now: Error: getCacheEntry failed: Cache service responded with 503 from the setup-java@v2 action. Failed again when I retried. 503...

getCacheEntry failed: Cache service responded with 503

It is because of the cache server not responding that includes internal server error or any other. You can use actions/cache@v3 instead of ......

Common 503 errors on Fastly | Fastly Help Guides

This error typically appears if a timeout error occurs when Fastly cache servers attempt to fetch content from your origins. It can also...

Troubleshooting Varnish Cache 503 Guru Meditation Error

A 503 error means that the web server trying to be reached is unavailable - this could be because it is overloaded, down...

HTTP 503 status code (Service Unavailable)

An HTTP 503 status code (Service Unavailable) typically indicates a performance issue on the origin server. In rare cases, it indicates that CloudFront ......