-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
24.9 Sentry cron container error #3442
Labels
Comments
Routing to @getsentry/product-owners-crons for triage ⏲️ |
Assigning to @getsentry/support for routing ⏲️ |
getsantry
bot
moved this from Waiting for: Support
to Waiting for: Product Owner
in GitHub Issues with 👀 3
Nov 25, 2024
This can be fixed by removing the celerybeat state file |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: