Error: getCacheEntry failed: Cache service responded with 503 #80

gr2m · 2021-01-21T22:13:10Z

I have seen this error pop up several times in the past few days

The error seems to originate from this code, which does not seem to be part of this repository

function retry(name, method, getStatusCode, maxAttempts = constants_1.DefaultRetryAttempts, delay = constants_1.DefaultRetryDelay, onError = undefined) {
    return __awaiter(this, void 0, void 0, function* () {
        let errorMessage = '';
        let attempt = 1;
        while (attempt <= maxAttempts) {
            let response = undefined;
            let statusCode = undefined;
            let isRetryable = false;
            try {
                response = yield method();
            }
            catch (error) {
                if (onError) {
                    response = onError(error);
                }
                isRetryable = true;
                errorMessage = error.message;
            }
            if (response) {
                statusCode = getStatusCode(response);
                if (!isServerErrorStatusCode(statusCode)) {
                    return response;
                }
            }
            if (statusCode) {
                isRetryable = isRetryableStatusCode(statusCode);
                errorMessage = `Cache service responded with ${statusCode}`;
            }
            core.debug(`${name} - Attempt ${attempt} of ${maxAttempts} failed with error: ${errorMessage}`);
            if (!isRetryable) {
                core.debug(`${name} - Error is not retryable`);
                break;
            }
            yield sleep(delay);
            attempt++;
        }
        throw Error(`${name} failed: ${errorMessage}`);
    });
}

I've set ACTIONS_STEP_DEBUG to true for future runs and will let you know if that yields any helpful information.

The source code above suggests that maxAttempts might be configurable? Is there an option I can set to retry requests in case of a 503?

The text was updated successfully, but these errors were encountered:

bitttttten · 2021-02-08T13:30:16Z

I'm getting a similar error but with 403:

Run bahmutov/npm-install@v1
running npm-install GitHub Action
trying to restore cached NPM modules
Error: Cache service responded with 403
    at Object.<anonymous> (/home/runner/work/_actions/bahmutov/npm-install/v1/dist/index.js:3503:19)
    at Generator.next (<anonymous>)
    at fulfilled (/home/runner/work/_actions/bahmutov/npm-install/v1/dist/index.js:3427:58)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
Error: Cache service responded with 403

jgoux · 2021-03-10T23:31:07Z

I have the same error as @bitttttten when trying to run my action on a pull_request closed event

aryella-lacerda · 2021-04-03T14:19:06Z

I'm getting the 403 error on pull_request closed too 👍🏼

Run bahmutov/npm-install@v1
running npm-install GitHub Action
trying to restore cached NPM modules
Error: Cache service responded with 403
    at Object.<anonymous> (/home/runner/work/_actions/bahmutov/npm-install/v1/dist/index.js:3503:19)
    at Generator.next (<anonymous>)
    at fulfilled (/home/runner/work/_actions/bahmutov/npm-install/v1/dist/index.js:3427:58)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
Error: Cache service responded with 403

If it makes any difference, I'm checking out the HEAD branch of the pull_request:

      - name: Checkout repository
        uses: actions/checkout@v2
        with:
          fetch-depth: 0
          ref: ${{ github.head_ref }}

hhimanshu · 2021-04-17T19:37:01Z

I am hitting the same issue today on one of the jobs, but not deployment_status

pjakubczyk · 2021-04-21T08:35:11Z

I'm doing transition to Github Actions and this error

Run bahmutov/npm-install@v1
running npm-install GitHub Action
trying to restore cached NPM modules
Error: Cache service responded with 429
    at Object.<anonymous> (/home/runner/work/_actions/bahmutov/npm-install/v1/dist/index.js:3503:19)
    at Generator.next (<anonymous>)
    at fulfilled (/home/runner/work/_actions/bahmutov/npm-install/v1/dist/index.js:3427:58)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
Error: Cache service responded with 429

shows up more than often. I feel that in case of reading the cache it should fallback with installing the dependency, not fail the build, right?

anshulsahni · 2021-11-17T13:45:05Z

I'm getting this error when the event is deployment, is this is because in some events because of the absence of some parameter retrieving cache is not possible? 🤔

nickofthyme · 2022-01-27T16:04:22Z

@anshulsahni I'm hitting the same thing as you in a deployment workflow. I think you are correct, it's not meant for that flow and likely something is missing. I'd say it's best to just run the install manually until then.

fransf-wtax · 2022-06-13T07:53:38Z

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 suggests this is a problem with GitHub Actions, not with my workflow.

nbonavia · 2022-06-13T07:59:27Z

Can there be a failover so that if the Cache fails to be retrieved, the standard npm install command gets executed instead. This will be able to still run the job if github actions have issues with caches.

afrokick · 2022-06-13T08:01:33Z

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 suggests this is a problem with GitHub Actions, not with my workflow.

Me too, but with setup-node@v2 for 16.x

Found in cache @ /opt/hostedtoolcache/node/16.15.1/x64
/opt/hostedtoolcache/node/16.15.1/x64/bin/npm config get cache
/home/runner/.npm
Error: getCacheEntry failed: Cache service responded with 503

14.x works great:
Found in cache @ /home/ghrunner/actions-runner/_work/_tool/node/14.18.2/x64

UPD: See a workaround below: #80 (comment)

perrin4869 · 2022-06-13T08:02:46Z

Yeah all my actions are failing now, too...

dannyk03 · 2022-06-13T08:05:22Z

Same here What's going on? We have production build failed, which is critical

Ginxo · 2022-06-13T08:05:54Z

same here https://github.com/kiegroup/kogito-docs/runs/6857322733?check_suite_focus=true

afrokick · 2022-06-13T08:10:13Z

Me too, but with setup-node@v2 for 16.x
Found in cache @ /opt/hostedtoolcache/node/16.15.1/x64
/opt/hostedtoolcache/node/16.15.1/x64/bin/npm config get cache
/home/runner/.npm
Error: getCacheEntry failed: Cache service responded with 503
14.x works great: Found in cache @ /home/ghrunner/actions-runner/_work/_tool/node/14.18.2/x64

[For NodeJS] So, I had an investigation. It doesn't work if cache was enabled. Try to disable cache by commenting cache key in your job.

Warning: It'll slowdown your action. It is just temporary solution!!!

jobs:
  check-format:
    runs-on: self-hosted
    steps:
      - uses: actions/checkout@v2
      - name: Use Node.js 16.x
        uses: actions/setup-node@v2
        with:
          node-version: 16.x
#          cache: 'npm'   <--- Action works only if cache disabled.
      - run: npm i
      - name: Check format
        run: npm run check-format
      - name: Linting
        run: npm run lint

Tonio-lavanda · 2022-06-13T08:21:01Z

It wasn't working for me 5min ago (503 error), I retried now and it's working

yatuvy · 2022-06-13T08:24:15Z

same here, looks like a github failure ...

mnicol93 · 2022-06-13T08:26:11Z

Me too, but with setup-node@v2 for 16.x
Found in cache @ /opt/hostedtoolcache/node/16.15.1/x64
/opt/hostedtoolcache/node/16.15.1/x64/bin/npm config get cache
/home/runner/.npm
Error: getCacheEntry failed: Cache service responded with 503
14.x works great: Found in cache @ /home/ghrunner/actions-runner/_work/_tool/node/14.18.2/x64

[For NodeJS] So, I had an investigation. It doesn't work if cache was enabled. Try to disable cache by commenting cache key.

Warning: It'll slowdown your action. It is just temporary solution!!!

jobs:
  check-format:
    runs-on: self-hosted
    steps:
      - uses: actions/checkout@v2
      - name: Use Node.js 16.x
        uses: actions/setup-node@v2
        with:
          node-version: 16.x
#          cache: 'npm'   <--- Action works only if cache disabled.
      - run: npm i
      - name: Check format
        run: npm run check-format
      - name: Linting
        run: npm run lint

This worked for me, thanks @afrokick

IamViditAgarwal · 2022-06-13T08:27:22Z

I was also facing the same issue , I checked the github repo for the actions/setup-node and found out they have release a v3 upgrade .
So i changed my code to use
actions/setup-node@v3

and now its working 👍🏻 ..

May be you guys also try this method . And also its good practice to keep upgrading the version of the github action step

afrokick · 2022-06-13T08:28:58Z

I was also facing the same issue , I checked the github repo for the actions/setup-node and found out they have release a v3 upgrade . So i changed my code to use actions/setup-node@v3

and now its working 👍🏻 ..

May be you guys also try this method . And also its good practice to keep upgrading the version of the github action step

Run actions/setup-node@v3
Found in cache @ /home/ghrunner/actions-runner/_work/_tool/node/16.15.1/x64
/home/ghrunner/actions-runner/_work/_tool/node/16.15.1/x64/bin/npm config get cache
/home/ghrunner/.npm
Error: getCacheEntry failed: Cache service responded with 503

Just tried, doesn't work for v3. Only works with disabled cache.

vinayakkulkarni · 2022-06-13T08:32:48Z

Yep, facing issue with cache: 'npm' but removing it fixes it...

      ....
      - name: Setup node env 📦
        uses: actions/setup-node@v3
        with:
          node-version: ${{ matrix.node }}
          check-latest: true
-          cache: 'npm' 
      ....

TaenFN · 2022-06-13T08:58:52Z

We're facing the same issue.

Error: getCacheEntry failed: Cache service responded with 503

- name: Install Node Deps
  uses: bahmutov/npm-install@v1

No cache key is specified.

Ulset · 2022-06-13T09:01:03Z

Same issue here

Run actions/setup-node@v2
Found in cache @ /opt/hostedtoolcache/node/16.15.1/x64
/opt/hostedtoolcache/node/16.15.1/x64/bin/npm config get cache
/home/runner/.npm
Error: getCacheEntry failed: Cache service responded with 503

lossless1 · 2022-06-13T09:03:02Z

I added the following to my package.json
"resolutions": {
    "@types/react": "17.0.14",
    "@types/react-dom": "17.0.14"
  }
worked for me :)))

how is it related to cache issue?

riffraff · 2022-06-13T09:04:32Z

@lossless1 it's probably invalidating the cache

ChristianBell1995 · 2022-06-13T10:11:37Z

Getting the same error here for actions/setup-node@v2

sdsa-cci · 2022-06-13T10:12:31Z

##[debug]getCacheEntry - Attempt 2 of 2 failed with error: Cache service responded with 503
Error: getCacheEntry failed: Cache service responded with 503

Getting this issue from past 10 mins now.

kimjngyun · 2022-06-13T10:14:48Z

Getting the same error here for actions/setup-node@v3

Attempting to download 17.x...
Not found in manifest.  Falling back to download directly from Node
Acquiring 17.[9](https://github.com/kimjngyun/kimjngyun.github.io/runs/6859207416?check_suite_focus=true#step:3:10).1 - x64 from https://nodejs.org/dist/v17.9.1/node-v17.9.1-linux-x64.tar.gz
Extracting ...
/usr/bin/tar xz --strip 1 --warning=no-unknown-keyword -C /home/runner/work/_temp/42346de7-0551-426c-8ac4-088aec477c41 -f /home/runner/work/_temp/171d2419-fa2c-464b-8235-cca6d234c4bc
Adding to the cache ...
Done
/usr/local/bin/yarn --version
1.22.18
/usr/local/bin/yarn cache dir
/home/runner/.cache/yarn/v6
Error: getCacheEntry failed: Cache service responded with 503

Npm caching is currently failing. See: bahmutov/npm-install#80

akindo · 2022-06-13T10:18:16Z

Updating to Checkout v. 3 didn't help. Didn't try updating setup-node to v. 3, but disabling npm cache did the trick.

dmarinere · 2022-06-13T10:19:13Z

Updating to Checkout v. 3 didn't help. Didn't try updating setup-node to v. 3, but disabling npm cache did the trick.

How do I disable cache

yras5869 · 2022-06-13T10:20:42Z

Disable the cache. It should work

afrokick · 2022-06-13T10:20:57Z

Updating to Checkout v. 3 didn't help. Didn't try updating setup-node to v. 3, but disabling npm cache did the trick.

How do I disable cache

Read above.

#80 (comment)

dmarinere · 2022-06-13T10:21:38Z

Updating to Checkout v. 3 didn't help. Didn't try updating setup-node to v. 3, but disabling npm cache did the trick.

How do I disable cache

Read above.

#80 (comment)

Thank you

sm1990 · 2022-06-13T11:09:52Z

I was also facing the same issue , I checked the github repo for the actions/setup-node and found out they have release a v3 upgrade . So i changed my code to use actions/setup-node@v3

and now its working 👍🏻 ..

May be you guys also try this method . And also its good practice to keep upgrading the version of the github action step

I have setup-node@v3 and still got the issue. Commenting cache:npm worked for me.

sdsa-cci · 2022-06-13T11:16:22Z

No need to upgrade anything. Just re-run you failed jobs. I tried this and worked for me. Seems like it was a service issues from Github's side.

bahmutov/npm-install#80 (comment)

topleft1562 · 2022-06-13T11:29:06Z

still failing for me.

kudaleganesh · 2022-06-13T11:30:16Z

Disabling the cache:npm works for me.

sirJiggles · 2022-06-13T11:31:39Z

are you all turning the cache on again and it works after? as I don't really want to just "turn off the cache" ideally 🙈

christos97 · 2022-06-13T11:33:27Z

Yes disabling (commenting out) the cache works.

It's not about the setup-* version.

Re-running failed jobs may work (tested) but it's not reliable.

If you HAVE to release today, just remove the cache but they will get it to work eventually I guess.

The thing here is, we need a way to disable cache without commiting t master branch imho
if the cache action is un-reliable.

Is this happening because of the underlying actions/cache action?

If so we need to know, we use actions/cache to cache angular build files too.

mateoqac · 2022-06-13T11:36:07Z

Ruby budnle-cache is failing too! :(

kudaleganesh · 2022-06-13T11:43:42Z

are you all turning the cache on again and it works after? as I don't really want to just "turn off the cache" ideally 🙈

After turning the cache on again, it failed. It is a temp solution.

kudaleganesh · 2022-06-13T11:49:59Z

It is a service issue.
https://www.githubstatus.com/

stdimitrovv · 2022-06-13T12:58:29Z

No production releases today, boys 😃

mwmw7 · 2022-06-13T13:03:18Z

Oh my god... We have to do hotfix...our team is still wating

Indronil · 2022-06-13T13:14:26Z

Hi,

I am having the same issue in my CI system just started occurring today for the first time. It was working fine without any issue until Friday.

Run actions/setup-node@v2
Found in cache @ /opt/hostedtoolcache/node/14.19.3/x64
/usr/local/bin/yarn --version
1.22.18
/usr/local/bin/yarn cache dir
/home/runner/.cache/yarn/v6
Error: getCacheEntry failed: Cache service responded with 503

Is it an issue from github side and will it be solved soon? We can live without cache until then if that is the case?

afrokick · 2022-06-13T13:33:06Z

Hi,

I am having the same issue in my CI system just started occurring today for the first time. It was working fine without any issue until Friday.

Run actions/setup-node@v2 Found in cache @ /opt/hostedtoolcache/node/14.19.3/x64 /usr/local/bin/yarn --version 1.22.18 /usr/local/bin/yarn cache dir /home/runner/.cache/yarn/v6 Error: getCacheEntry failed: Cache service responded with 503

Is it an issue from github side and will it be solved soon? We can live without cache until then if that is the case?

Yes, just disable cache for some time while Github fixing this issue

sherif-farid · 2022-06-13T13:42:02Z

updating from v2 to v3 solved my problem

steps:
      - uses: actions/checkout@v3
      - name: set up JDK 11
        uses: actions/setup-java@v3
        with:
          java-version: 11
          distribution: corretto

stdimitrovv · 2022-06-13T14:04:36Z

It's up again, boys, the dream is alive

sergiovanacloig · 2022-06-13T14:07:32Z

The issue should be solved, it seemed a problem in the github actions side. You can check here for the status: https://www.githubstatus.com/

christos97 · 2022-06-14T11:03:47Z

Can you please add the ability to disable the cache without commiting to master ?
Maybe directly from the actions tab if cache is mentioned in the yaml file?

gr2m mentioned this issue Jan 21, 2021

chore(deps): update dependency semantic-release to v17.3.6 semantic-release/npm#327

Merged

1 task

chenhunghan mentioned this issue Apr 9, 2021

Remove bahmutov/npm-install, use old school npm install lensapp/lens-platform-sdk#2

Merged

vinayakkulkarni mentioned this issue Jun 13, 2022

Error: getCacheEntry failed: Cache service responded with 503 actions/setup-node#516

Closed

5 tasks

Limraj mentioned this issue Jun 13, 2022

Fixed getCacheEntry failed: Cache service responded with 503 SCADA-LTS/Scada-LTS#2259

Closed

cedmax mentioned this issue Jun 13, 2022

Add _.isEmpty cedmax/youmightnotneed#189

Closed

mdubus mentioned this issue Jun 13, 2022

Use digit group formatting for the number of documents meilisearch/mini-dashboard#273

Merged

Noorts added a commit to onramper/widget that referenced this issue Jun 13, 2022

Temporarily disable workflow npm caching

056f648

Npm caching is currently failing. See: bahmutov/npm-install#80

akumar074 mentioned this issue Jun 13, 2022

KOGITO-7232: Push kogito-docs build to GH Pages apache/incubator-kie-kogito-docs#16

Merged

louislam mentioned this issue Jun 13, 2022

Remove template comment in SECURITY.md louislam/uptime-kuma#1754

Merged

Klaas-Ritense added a commit to Gemeente-DenHaag/nl-portal-libraries that referenced this issue Jun 13, 2022

Temporary disable cache

e5db560

bahmutov/npm-install#80 (comment)

allbecauseyoutoldmeso mentioned this issue Jun 13, 2022

Fix specs unboxed/bops#655

Merged

Error: getCacheEntry failed: Cache service responded with 503 #80

Error: getCacheEntry failed: Cache service responded with 503 #80

Comments

gr2m commented Jan 21, 2021

bitttttten commented Feb 8, 2021 • edited Loading

jgoux commented Mar 10, 2021

aryella-lacerda commented Apr 3, 2021

hhimanshu commented Apr 17, 2021

pjakubczyk commented Apr 21, 2021

anshulsahni commented Nov 17, 2021 • edited Loading

nickofthyme commented Jan 27, 2022

fransf-wtax commented Jun 13, 2022

nbonavia commented Jun 13, 2022

afrokick commented Jun 13, 2022 • edited Loading

perrin4869 commented Jun 13, 2022

dannyk03 commented Jun 13, 2022

Ginxo commented Jun 13, 2022

afrokick commented Jun 13, 2022 • edited Loading

Tonio-lavanda commented Jun 13, 2022

yatuvy commented Jun 13, 2022

mnicol93 commented Jun 13, 2022

IamViditAgarwal commented Jun 13, 2022

afrokick commented Jun 13, 2022

vinayakkulkarni commented Jun 13, 2022

TaenFN commented Jun 13, 2022

Ulset commented Jun 13, 2022

lossless1 commented Jun 13, 2022

riffraff commented Jun 13, 2022

ChristianBell1995 commented Jun 13, 2022

sdsa-cci commented Jun 13, 2022

kimjngyun commented Jun 13, 2022

akindo commented Jun 13, 2022

dmarinere commented Jun 13, 2022

yras5869 commented Jun 13, 2022

afrokick commented Jun 13, 2022

dmarinere commented Jun 13, 2022

sm1990 commented Jun 13, 2022

sdsa-cci commented Jun 13, 2022

topleft1562 commented Jun 13, 2022

kudaleganesh commented Jun 13, 2022

sirJiggles commented Jun 13, 2022

christos97 commented Jun 13, 2022 • edited Loading

mateoqac commented Jun 13, 2022

kudaleganesh commented Jun 13, 2022 • edited Loading

kudaleganesh commented Jun 13, 2022

stdimitrovv commented Jun 13, 2022

mwmw7 commented Jun 13, 2022

Indronil commented Jun 13, 2022

afrokick commented Jun 13, 2022

sherif-farid commented Jun 13, 2022 • edited Loading

stdimitrovv commented Jun 13, 2022

sergiovanacloig commented Jun 13, 2022 • edited Loading

christos97 commented Jun 14, 2022

bitttttten commented Feb 8, 2021 •

edited

Loading

anshulsahni commented Nov 17, 2021 •

edited

Loading

afrokick commented Jun 13, 2022 •

edited

Loading

afrokick commented Jun 13, 2022 •

edited

Loading

christos97 commented Jun 13, 2022 •

edited

Loading

kudaleganesh commented Jun 13, 2022 •

edited

Loading

sherif-farid commented Jun 13, 2022 •

edited

Loading

sergiovanacloig commented Jun 13, 2022 •

edited

Loading