search

getsentry / self-hosted

Sentry, feature-complete and packaged up for low-volume deployments and proofs-of-concept
https://develop.sentry.dev/self-hosted/
Other
7.97k stars 1.78k forks source link

24.9 Sentry cron container error #3442

Open OldBucFan opened 1 week ago

OldBucFan commented 1 week ago

Self-Hosted Version

24.9.0

CPU Architecture

x86_64

Docker Version

26.1.1

Docker Compose Version

NA

Steps to Reproduce

When starting the cron container it continually errors ,same output trying to start the container manually.

Expected Result

Sentry-cron container rune without issue

Actual Result

output:

sentry/requirements.txt is deprecated, use sentry/enhance-image.sh - see https://github.com/getsentry/self-hosted#enhance-sentry-image celery beat v5.3.5 (emerald-rush) is starting. - ... - _ LocalTime -> 2024-11-21 15:35:26 Configuration -> . broker -> redis://:**@127.0.0.1:6379/0 . loader -> celery.loaders.app.AppLoader . scheduler -> celery.beat.PersistentScheduler . db -> /tmp/sentry-celerybeat . logfile -> [stderr]@%WARNING . maxinterval -> 5.00 minutes (300s) Traceback (most recent call last): File "/usr/local/lib/python3.12/shelve.py", line 111, in getitem value = self.cache[key]


KeyError: 'entries'

During handling of the above exception, another exception occurred:
...
ModuleNotFoundError: No module named 'pytz'

Previous version 23.11.0 didn't have any issues and none of the other containers have an issue.  

### Event ID

_No response_
getsantry[bot] commented 1 week ago

Routing to @getsentry/product-owners-crons for triage ⏲️

getsantry[bot] commented 1 week ago

Assigning to @getsentry/support for routing ⏲️

bc-sentry commented 1 week ago

This can be fixed by removing the celerybeat state file