Schnittchen

Go away stale bot.

This issue is very likely not solved, and a stale bot won't change that. I won't expend any more energy here fighting a stupid bot. Have a good day.

> -> Hatch -> Recovery and Repair -> Recreate missing chunks for all files This gave me a screenful of "This document could not be saved" errors

I think a new option is more clear. And I think for 99.999% of all use cases, the option makes sense to be true, so that should be the default.

I added the LOG_LEVEL and I'm currently investigating. The second time now I've seen this: ``` Nov 19 09:19:13 sonnenschein-gh-runner docker[320972]: [2024-11-19 09:19:13 +00:00 DEBUG] Going back to sleep… Nov...

If it was a Signal, I think systemd would show that in the logs? It's definitely not memory pressure.

That would be quite some effort, since I'm running it on a server and I'd need to set up all the tooling... Maybe it's possible to wrap docuum with a...

As I mentioned, besides docuum I have a service running which periodically tries to get rid of old container, volumes and networks. I disabled it(*) so it does not interfere...

For the record, this is what I'm doing right now regarding other resources, from a minutely scheduled script: ``` # Clear docker build cache when free disk space is running...

Here's logs from the last time docuum terminated: ``` Nov 29 10:19:42 sonnenschein-gh-runner docker[2402942]: [2024-11-29 10:19:42 +00:00 DEBUG] Docker images are using `9.68 GB`, which is within the limit of...