Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document how to troubleshoot queue problems #788

Closed
chadwhitacre opened this issue Jan 4, 2021 · 3 comments · Fixed by getsentry/develop#271
Closed

Document how to troubleshoot queue problems #788

chadwhitacre opened this issue Jan 4, 2021 · 3 comments · Fixed by getsentry/develop#271
Assignees

Comments

@chadwhitacre
Copy link
Member

chadwhitacre commented Jan 4, 2021

We have some basic troubleshooting docs. Let's expand them to talk about sentry queues.

@kanadaj:

basic troubleshooting (to find which worker is actually broken, we have like 7 different consumers/replacers/workers)

@lucas-zimerman:

ah yeah, when sentry breaks nobody knows how to fix it xD
I think our biggest issue is the workers that often times die
and they won't come back

@lucas-zimerman
Copy link

This might be too complex but it would be nice if there was troubleshooting about migrating Sentry from one computer/server to another.

@kanadaj
Copy link

kanadaj commented Jan 4, 2021

This might be too complex but it would be nice if there was troubleshooting about migrating Sentry from one computer/server to another.

I think you just need to SQL dump CH and postgres, then restore on the new server. You can also just shut down the containers and copy the mounted data folders as they are, that should work as well.

@lucas-zimerman
Copy link

one thing to point out for troubleshooting is to check the number of active connections:
image
I just noticed from redis container that the maximum number of connections is not allowing the internal services to communicate.

@BYK BYK self-assigned this Jan 6, 2021
BYK added a commit to getsentry/develop that referenced this issue Feb 12, 2021
This section now covers the most commin questions/issues we get regarding self-hosted. It also addresses https://app.asana.com/0/1169344595888357/1188448821391289 meaning it fixes getsentry/self-hosted#478, and fixes getsentry/self-hosted#788.
BYK added a commit to getsentry/develop that referenced this issue Feb 15, 2021
This section now covers the most commin questions/issues we get regarding self-hosted. It also addresses https://app.asana.com/0/1169344595888357/1188448821391289 meaning it fixes getsentry/self-hosted#478, and fixes getsentry/self-hosted#788.
@github-actions github-actions bot locked and limited conversation to collaborators Mar 3, 2021
a-hariti pushed a commit to getsentry/sentry-docs that referenced this issue Jun 8, 2024
This section now covers the most commin questions/issues we get regarding self-hosted. It also addresses https://app.asana.com/0/1169344595888357/1188448821391289 meaning it fixes getsentry/self-hosted#478, and fixes getsentry/self-hosted#788.
stephanie-anderson pushed a commit to getsentry/sentry-docs that referenced this issue Jun 10, 2024
This section now covers the most commin questions/issues we get regarding self-hosted. It also addresses https://app.asana.com/0/1169344595888357/1188448821391289 meaning it fixes getsentry/self-hosted#478, and fixes getsentry/self-hosted#788.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants