Skip to content
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

Celery queue celery looks like always stop work after few days... #4214

Closed
zslucky opened this issue Jul 24, 2020 · 4 comments
Closed

Celery queue celery looks like always stop work after few days... #4214

zslucky opened this issue Jul 24, 2020 · 4 comments
Labels
question This is more a question for the support than an issue. wontfix Nobody will work on this.

Comments

@zslucky
Copy link

zslucky commented Jul 24, 2020

Describe the bug

Celery queue celery looks like always stop working after few days... every time I restart the service, it can run for some days.

weblate will show alert, Celery looks like too slow, after celery collect many tasks, it also alert me Celery looks like stop work

To Reproduce

Hard to describe the reproduce steps, just I have some projects and many components.

Expected behavior

Celery should work correctly.

Server configuration and status

  • Weblate: 4.2-dev
  • Django: 3.0.8
  • siphashc: 1.3
  • Whoosh: 2.7.4
  • translate-toolkit: 3.0.0
  • lxml: 4.5.2
  • Pillow: 7.2.0
  • bleach: 3.1.5
  • python-dateutil: 2.8.1
  • social-auth-core: 3.3.3
  • social-auth-app-django: 4.0.0
  • django-crispy-forms: 1.9.2
  • oauthlib: 3.1.0
  • django-compressor: 2.4
  • djangorestframework: 3.11.0
  • django-filter: 2.3.0
  • django-appconf: 1.0.4
  • user-agents: 2.1
  • filelock: 3.0.12
  • setuptools: 40.8.0
  • jellyfish: 0.8.2
  • openpyxl: 3.0.1
  • celery: 4.4.6
  • kombu: 4.6.11
  • translation-finder: 2.1
  • html2text: 2020.1.16
  • pycairo: 1.16.2
  • pygobject: 3.30.4
  • diff-match-patch: 20181111
  • requests: 2.24.0
  • django-redis: 4.12.1
  • hiredis: 1.0.1
  • sentry_sdk: 0.16.1
  • Cython: 0.29.21
  • misaka: 2.1.1
  • GitPython: 3.1.3
  • borgbackup: 1.1.13
  • pyparsing: 2.4.7
  • Python: 3.7.3
  • Git: 2.20.1
  • psycopg2: 2.8.5
  • psycopg2-binary: 2.8.5
  • phply: 1.2.5
  • chardet: 3.0.4
  • ruamel.yaml: 0.16.10
  • tesserocr: 2.5.1
  • akismet: 1.1
  • boto3: 1.14.20
  • zeep: 3.4.0
  • aeidon: 1.7.0
  • iniparse: 0.5
  • mysqlclient: 2.0.1
  • Mercurial: 5.4.2
  • git-svn: 2.20.1
  • git-review: 1.28.0
  • hub: 2.13.0
  • lab: 0.16
  • Redis server: 4.0.14
  • PostgreSQL server: 11.8
  • Database backends: django.db.backends.postgresql
  • Cache backends: default:RedisCache, avatar:FileBasedCache
  • Email setup: django.core.mail.backends.smtp.EmailBackend: smtp.gmail.com
  • OS encoding: filesystem=utf-8, default=utf-8
  • Celery: redis://cache:6379/1, redis://cache:6379/1, regular
  • Platform: Linux 4.14.143-118.123.amzn2.x86_64 (x86_64)

Weblate deploy checks

Only a piece of backup configuration info.

Additional context

I'm using docker-compose, I'm not sure is it related to celery configuration, I want to increase celery concurrency number, but looks like no documents let to configure celery in docker-compose file?


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@nijel
Copy link
Member

nijel commented Jul 24, 2020

Do you get any errors in the logs? Is it still receiving tasks?

I want to increase celery concurrency number, but looks like no documents let to configure celery in docker-compose file?

Recently, a pull request implementing this has been merged, see WeblateOrg/docker#745

@nijel nijel added the question This is more a question for the support than an issue. label Jul 24, 2020
@github-actions
Copy link

This issue looks like a support question. We try to answer these reasonably fast, but in case you are looking for faster resolution, please consider purchasing support subscription and make Weblate stronger.

@zslucky
Copy link
Author

zslucky commented Jul 25, 2020

I will provide all the relation logs later

@stale
Copy link

stale bot commented Aug 8, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix Nobody will work on this. label Aug 8, 2020
@stale stale bot closed this as completed Aug 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question This is more a question for the support than an issue. wontfix Nobody will work on this.
Projects
None yet
Development

No branches or pull requests

2 participants