# Error code 137 - cache error

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Ferror-code-137-cache-error%2F152177%3E%5C
**Category:** Beginners\
**Created:** [April 24, 2025, 4:41pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Ferror-code-137-cache-error%2F152177 "2025-04-24T16:41:28Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [April 25, 2025, 7:18am UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Ferror-code-137-cache-error%2F152177%2F4 "2025-04-25T07:18:53Z")

</div>

> [@My Space suddenly went offline. The CPU cannot restart](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fmy-space-suddenly-went-offline-the-cpu-cannot-restart%2F151121)%3A
>
> It was running normally before, then suddenly disappeared, showing the Huggingface icon and a message saying “Building Space.” I checked the backend logs, and before the logs stopped, there were several instances of “reloading database.” I tried restarting the Space, but it didn’t work. I tried rebuilding the Space, but it also didn’t work. Then I noticed my CPU is stuck in a spinning state. What should I do now?

I wonder if the effects of this server error are still ongoing…

If I knew which space it was, I could give you more details. The original copy is fine…

---

_[View the full topic](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Ferror-code-137-cache-error%2F152177)._
