My sprite has been unreachable for the past ~24 hours

Questions / Help
1

Hi folks, I have a sprite that has become unreachable for about 24 hours. It’s not a production workload or anything, it was running claude, its not the end of the world if we cant get it back but it would be nice to even just log in & get my claude context + pull some markdown files from it.

```
luke@telamon:~/workbench/sprites$ sprite console -s armstrong-bot
Error: failed to start sprite command: failed to connect: read tcp [2605:a601:a0c9:f200:5758:ca81:be85:f6c2]:46734->[2a09:8280:1::99:d7b3:0]:443: i/o timeout
```

Hopefully you can tell my other details from my account?

There is a chance it’s run out of disk space, I did this one before on another sprite where my app was flooding the machine with log files, I thought I had fixed it but now here we are, so heads up maybe its out of disk - maybe we can provision it bigger temporarily, log in & clean out the logs? Or maybe thats not the problem at all, thats just my guess. And I will fix the bug properly after this I promise :stuck_out_tongue:

Thanks

4

Note sure if you fixed it or it fixed itself, but I can access this sprite now. Thanks!

5

From what I could see, it seems like there was a process(es) eating up the CPU and memory. I was able to restart the sprite. It should be accessible now but something you had running got very resource-greedy.

EDIT: Cool, you’re back in!

6

yeah my b :stuck_out_tongue:

you guys probably know a lot more about this than I do but maybe sprites need a certain % of resources so CPU thrashing or whatever doesnt lock people out - thanks for fixing this though, I am going to move my work (which isnt suited to sprites that well I think cause of issues like whats causing this to happen) to a fly IO container