Description
Self-Hosted Version
22.9.0 (on Ubuntu 22.04)
CPU Architecture
x86_64
Docker Version
20.10.18, build b40c2f6
Docker Compose Version
2.10.2
Steps to Reproduce
Install Sentry-self hosted, leave it running for a while.
Expected Result
Normal CPU and RAM consumption.
Actual Result
When I first installed Sentry self-hosted, and started sending it data, all was going well. The self-hosted dashboard was reporting performance and error data as expected, and RAM/CPU usage was completely under control.
But then overnight the CPU and RAM usage on the server went crazy, with CPU maxing out, high RAM and swap usage. This appeared to be down to sentry, because running docker compose down
restored things back to normal (except that sentry was no longer running).
This seems very similar to this issue from @umgbhalla but there wasn't any apparent resolution there, except maybe to re-install sentry from fresh. I also have 32 GB RAM and 8 cores. It's also similar to this issue from @wodCZ, but I'm not seeing the little CPU spikes.
I tried installing sentry from fresh, but CPU was still maxing out after:
The short period maxing out at 100% was when I set it running again, followed soon after by shutting it down again.
However, I don't think that it was a completely fresh install, because despite removing the self-hosted
folder completely and re-installing, when running docker compose run --rm web createuser
after installing to add a user (I install with ./install.sh --skip-user-creation
to avoid any prompts during installation), it said User: me@mydomain.com exists, use --force-update to force
... so it still had some retained state from before?
In any case, it shouldn't really be necessary to re-install in order to get CPU/RAM back under control. Any ideas?
(And an aside... is it possible to script the docker compose run --rm web createuser
step, i.e. with no user prompts and instead pass the info by args or env vars?)
Metadata
Metadata
Assignees
Type
Projects
Status
Status
Status