Caching not working

[vladimir-h4h]

Select Topic Area

Bug

Body

Our workflows are all failing because the caching is not working.

Warning: The runner was not able to contact the cache service. Caching will be skipped
Run actions/cache@v4
Warning: An internal error has occurred in cache backend. Please check https://www.githubstatus.com/ for any ongoing issue in actions.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[kirilshivachev]

Getting the same error.

[tapsouza]

I'm having the same problem!

[tjsousa]

We're also affected. why no mention in the status page?

[prati08]

We're also affected. why no mention in the status page?

[prati08]

when it is expected to get fix?

[aquarhead]

This seems to have started around 10:30 AM GMT - we had one build successfully done at 10:01.

For us this primarily affects aquasecurity/trivy-action@master while e.g. astral-sh/setup-uv@v6 and docker/build-push-action@v6 seems to still work fine. Maybe that helps to pinpoint where the issue might be?

[aquarhead]

This also affects SonarSource/sonarqube-scan-action@v5

though it doesn't rely entirely on the cache so can still finish.

For trivy though, we use a cronjob to cache trivy db which is totally broken now https://github.com/aquasecurity/trivy-action?tab=readme-ov-file#updating-caches-in-the-default-branch

[hugos99]

Also affected on my side

[arxanter]

We are also affected.

[VladKhachikyan]

We're also affected.

[jannikrichter]

Alse affected here

[gurugray]

our builds are also affected

[damian-pilarczyk]

not working for us as well

[yuvalek]

We're also affected. why no mention in the status page?

[codeasone]

This is affecting our team too:

Warning: An internal error has occurred in cache backend. Please check https://www.githubstatus.com/ for any ongoing issue in actions.

But the status page is reporting "All Systems Operational" 🤕

[arxanter]

I think the problem relates to the backend service of this action. Maybe it's not a part of Github infrastructure.

[vladimir-h4h]

Maybe it is related to this:
actions/toolkit#1890

[arxanter]

I don't think so. This announcement was about legacy version(v1 and v2). As I know this issue happens at v3 and v4 versions

[arxanter]

GH have updated the status, and created an incident - https://www.githubstatus.com/incidents/2fk03fzv6zk0

Cross fingers for quick fix

[rumaniel]

https://www.githubstatus.com/incidents/9hzy25gws8vh
new issue mentions that there is an problem with Actions cache service.
We are experiencing degradation with the GitHub Actions cache service and are working on applying the appropriate mitigations.

[samus-aran]

Hi everyone!

We appreciate you reaching out to report this issue! 

We have provided details about the incident in this discussion. Please subscribe to that post to receive real-time updates and a notification when the incident is resolved. 

If you have further questions or additional details about your experience, please comment directly on the discussion linked above.

We appreciate your patience as we work toward a solution. Thank you for your contribution to making GitHub even better!

[samus-aran]

Hi Everyone! The Incident status has been updated to Resolved. If you are still experiencing issues please continue to raise them here or in the Incident discussion 👍 Thank you all for your patience. ⭐

[Leksat]

It looks like there are still some leftovers from the incident: https://github.com/orgs/community/discussions/160793

[rjtferreira]

we're also seeing what appears to be some leftovers of this.

Warning: Failed to save: reserveCache failed: connect ETIMEDOUT 52.152.245.137:443

It appears to be something wrong on this IP

Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
tcp        0      1 172.19.66.136:40734     52.152.245.137:443      SYN_SENT    -                   
tcp6       0      0 172.19.66.136:33740     140.82.112.22:443       ESTABLISHED -                   
tcp6       0      0 172.19.66.136:37356     20.96.133.71:443        ESTABLISHED -                   
tcp6       0      0 172.19.66.136:37368     20.96.133.71:443        ESTABLISHED -                   
tcp6       0      0 172.19.66.136:52124     20.85.130.105:443       ESTABLISHED -                   
root@actions-runner-no-cache-m6qrz-0:~# telnet 52.152.245.137 443
Trying 52.152.245.137...

[Leksat]

@samus-aran Many people confirm the issue: https://github.com/orgs/community/discussions/160793

[matan-legit]

there are issues again