Alex Zaslavsky
Alex Zaslavsky
It's quite difficult to debug this remotely - Sentry knows that some errors didn't make it all the way through the pipeline, but that's really all it knows, otherwise they...
Yep, there is a backup/restore tool for exactly this use case: https://develop.sentry.dev/self-hosted/backup/#partial-json-backup
@csvan Have you updated your install recently?
My first guess here would be a memory issue. Can you check the memory usage on this container, and the system asa whole, relative to how much you have available?
I don't doubt that your setup is sufficient, but if the issue is related to memory consumption on our end due to something we snuck into the 24.4.0 release, it...
Can you try the advice posted [here](https://github.com/getsentry/self-hosted/issues/2931#issuecomment-2040854990)?
cc @volokluev. We'll keep it open for now.
This script was basically nonfunctional on old versions, prior to 23.11.1. I'd recommend using the approach specified [here](https://develop.sentry.dev/self-hosted/backup/#full-backup) for your version instead. Conversely, you can upgrade to >=23.11.1 (don't forget...
It's very hard to say. The reason this operation was so buggy was because it just exported/imported raw tables. But a new instance has entries of its own - these...
It seems like the SSL certificates on the machine you are running self-hosted on may be out of date? Have you tried updating those?