Sentry Self-Hosted Upgrade Failed
Quick answer
Failed self-hosted upgrades often leave Kafka, Snuba or ClickHouse half migrated, often after running out of disk. Free disk, re-run install.sh from a required stop version, and never prune volumes without a backup.
Most likely fix: Free resources first
How to fix it
Try these in order — the most common fix is first.
1. Free resources first
- Meet the 4 CPU, 16 GB RAM and 20+ GB free disk baseline
- Back up before deleting anything; docker system prune --volumes can delete data
Did this fix it?2. Re-run the upgrade
- Check the self-hosted releases for required stops
- Run ./install.sh again and read which component fails first
- Then docker compose up --wait
Did this fix it?
Symptoms
install.sh errors out on Kafka topics, Snuba or ClickHouse during upgrade.
Why it happens
- Not enough disk (Kafka fills it)
- Skipped a required upgrade stop
- Partial migration from an earlier failed run
This guide also covers
- sentry self hosted upgrade failed
- sentry install.sh error
- sentry kafka clickhouse error
Still not working?
If Sentry keeps failing, you're not alone. See every Sentry problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usOther Sentry errors
- Sentry Source Maps Not Working
- Sentry Events Not Showing Up
- Sentry Blocked by Ad Blockers (Tunnel Fix)
- Sentry Quota Exceeded: What Happens and How to Fix It
- Sentry Too Many Alerts and Noisy Errors
- Sentry Alert Emails Not Received
- Sentry Next.js Not Sending Events
- Sentry Spans and Performance Quota Running Out