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
MISCONF Redis #11614
Comments
Did you check the Redis logs as the error suggests? Maybe the disk is full? |
This issue has been marked as a question by a Weblate team member. Why? Because it belongs more to the professional Weblate Care or community Discussions than here. We strive to answer these reasonably fast here, too, but purchasing the support subscription is more responsible and faster for your business. And it makes Weblate stronger as well. Thanks! In case your question is already answered, making a donation is the right way to say thank you! |
Where can I find the redis logs in Docker? I have about 5 GB of free space. |
|
I will check this log if the problem reoccurs. Currently, I only have logs available after restarting the container. Edit: |
Redis does dump it's content regularly and in that time it needs double disk space, check content of its volume to see how much it uses. |
There was no mistake after the seat was cleared tonight. I think that was a real problem. |
The issue you have reported is now resolved. If you don’t feel it’s right, please follow its labels to get a clue for further steps.
|
Describe the issue
After this error, celery stops processing jobs. Maybe there is more useful information in sentry.
I already tried
Steps to reproduce the behavior
Expected behavior
No response
Screenshots
No response
Exception traceback
No response
How do you run Weblate?
weblate.org service
Weblate versions
5.5.4-dev — 5067ae4cb050c601f6fb2fa396e19832931efd5e -- 5.5.4-dev — [5067ae4](https://github.com/WeblateOrg/weblate/commits/5067ae4cb050c601f6fb2fa396e19832931efd5e)Weblate deploy checks
No response
Additional context
docker compose stop and docker compose up temporarily solve the problem
The text was updated successfully, but these errors were encountered: