wiki:sentry_troubleshooting
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| wiki:sentry_troubleshooting [2024/09/25 13:25] – add Kafka info antisa | wiki:sentry_troubleshooting [2026/05/27 08:16] (current) – [Postgres DB getting too big] antisa | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ====== Sentry troubleshooting ====== | ====== Sentry troubleshooting ====== | ||
| ===== Postgres DB getting too big ===== | ===== Postgres DB getting too big ===== | ||
| - | One option is to truncate the nodestore_node table. Enter the DB: | + | One option is to truncate the nodestore_node table. |
| + | |||
| + | Enter the DB: | ||
| psql -U postgres | psql -U postgres | ||
| Line 64: | Line 66: | ||
| ... | ... | ||
| </ | </ | ||
| - | ====== Tested on ====== | + | ==== Tested on ===== |
| * sentry_version: | * sentry_version: | ||
| * PostgreSQL 14.5 | * PostgreSQL 14.5 | ||
| + | ===== Can't start some containers ===== | ||
| + | |||
| + | <code | > | ||
| + | |||
| + | ERROR: for memcached | ||
| + | |||
| + | ERROR: for symbolicator-cleanup | ||
| + | |||
| + | ERROR: for smtp UnixHTTPConnectionPool(host=' | ||
| + | |||
| + | ERROR: for clickhouse | ||
| + | |||
| + | ERROR: for zookeeper | ||
| + | |||
| + | ERROR: for postgres | ||
| + | ERROR: An HTTP request took too long to complete. Retry with --verbose to obtain debug information. | ||
| + | If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60). | ||
| + | </ | ||
| + | |||
| + | Just run it with higher timeout value: | ||
| + | |||
| + | COMPOSE_HTTP_TIMEOUT=120 docker-compose ps | ||
| + | |||
| + | ==== Tested on ===== | ||
| + | * Sentry 20.6.037a7530 (docker) | ||
| ====== See also ====== | ====== See also ====== | ||
wiki/sentry_troubleshooting.1727270731.txt.gz · Last modified: by antisa
