Skip to content

Commit 2c084e1

Browse files
committed
docs(self-hosted): Troubleshooting guide to invalidate projectconfigs
Closes getsentry/self-hosted#3977
1 parent ffca9d0 commit 2c084e1

File tree

1 file changed

+15
-0
lines changed
  • develop-docs/self-hosted/troubleshooting

1 file changed

+15
-0
lines changed

develop-docs/self-hosted/troubleshooting/sentry.mdx

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -69,3 +69,18 @@ Some known paths where you may see this error:
6969
* _static/dist/sentry/entrypoints/app.js
7070

7171
To fix this, you can disable the auto optimization performed by your CDN.
72+
73+
## Relay rejects envelope events
74+
75+
If you're seeing the following error in your Relay logs:
76+
```
77+
ERROR relay_server::services::projects::cache::service: failed to fetch project from source: Fetch { project_key: ProjectKey("00000000000000000000000000000000"), previous_fetch: None, initiated: Instant { tv_sec: 16838910, tv_nsec: 923025932 }, when: Some(Instant { tv_sec: 16839069, tv_nsec: 382950946 }), revision: Revision(None) } tags.project_key="00000000000000000000000000000000" tags.has_revision=false error=upstream error failed to send message to service error.sources=[failed to send message to service]
78+
```
79+
80+
This means Relay is unable to fetch the project configuration from Redis. This can happen if the worker (in the `taskworker` container) is lagging behind, making it unable to write new project configurations to Redis, which Relay then cannot fetch.
81+
82+
To fix this, you can trigger a manual project configuration invalidation by running the following command. Warning: This will temporarily halt event ingestion until the project configurations are written to Redis again.
83+
84+
```bash
85+
docker compose exec web ./bin/invalidate-project-configs
86+
```

0 commit comments

Comments
 (0)