(weblate.E034) The Celery process is outdated or misconfigured. Following items differ: vcs

[erictapen]

Describe the issue

I'm currently packaging Weblate for NixOS. When running weblate check --deploy on my deployment, I get the error

?: (weblate.E034) The Celery process is outdated or misconfigured. Following items differ: vcs
        HINT: https://docs.weblate.org/en/weblate-4.8.1/admin/install.html#celery

I already tried

This error is persistent across reboots and service restarts.

I looked inte Weblate and Celery sources. The check happens in weblate/utils/checks.py check_celery(). Iirc the check compares a pong received by Celery with a predefined pong defined in weblate/utils/tasks.py.

By patching the check to give more verbose output I figured, that current["vcs"]) (the predefined list) is ['gerrit', 'git', 'git-force-push', 'local', 'mercurial', 'subversion'], while pong["vcs"] (which is the answer received by celery) is [].

Unfortunately I have no clue how this difference happens. Also neither in the documentation or in the sources I found any clue on how to manipulate the value of VCS_REGISTRY from config.

• I've read and searched the docs and did not find the answer there.
  If you didn’t try already, try to search there what you wrote above.

To Reproduce the issue

Steps to reproduce the behavior:

weblate check --deploy

See system information below.

Expected behavior

Screenshots

Exception traceback

Server configuration and status

Weblate installation: other, I wrote a NixOS module for deploying Weblate

$ weblate-env weblate list_versions
 * Weblate: 4.8.1
 * Django: 3.2.8
 * siphashc: 2.1
 * translate-toolkit: 3.4.1
 * lxml: 4.6.3
 * Pillow: 8.3.2
 * bleach: 4.1.0
 * python-dateutil: 2.8.2
 * social-auth-core: 4.1.0
 * social-auth-app-django: 5.0.0
 * django-crispy-forms: 1.12.0
 * oauthlib: 3.1.1
 * django-compressor: 2.4.1
 * djangorestframework: 3.12.4
 * django-filter: 2.4.0
 * django-appconf: 1.0.5
 * user-agents: 2.2.0
 * filelock: 3.0.12
 * setuptools: 54.2.0.post0
 * jellyfish: 0.8.2
 * openpyxl: 3.0.9
 * celery: 5.1.2
 * kombu: 5.1.0
 * translation-finder: 2.10
 * weblate-language-data: 2021.5
 * html2text: 2020.1.16
 * pycairo: 1.20.1
 * pygobject: 3.42.0
 * diff-match-patch: 20200713
 * requests: 2.26.0
 * django-redis: 5.0.0
 * hiredis: 2.0.0
 * sentry_sdk: 1.3.1
 * Cython: 0.29.24
 * misaka: 2.1.1
 * GitPython: 3.1.18
 * borgbackup: 1.1.17
 * pyparsing: 2.4.7
 * pyahocorasick: 1.4.2
 * python-redis-lock: 3.7.0
 * Python: 3.8.11
 * Git: 2.31.1
 * psycopg2: 2.9.1
 * phply: 1.2.5
 * chardet: 4.0.0
 * ruamel.yaml: 0.17.16
 * aeidon: 1.9
 * iniparse: 0.5
 * Mercurial: 5.8
 * git-svn: 2.31.1
 * git-review: 2.1.0
 * Redis server: 6.2.6
 * PostgreSQL server: 9.6.23
 * Database backends: django.db.backends.postgresql
 * Cache backends: default:RedisCache, avatar:FileBasedCache
 * Email setup: django.core.mail.backends.smtp.EmailBackend: 127.0.0.1
 * OS encoding: filesystem=utf-8, default=utf-8
 * Celery: redis+socket::///run/redis/redis.sock, redis+socket::///run/redis/redis.sock, regular
 * Platform: Linux 5.10.71 (x86_64)

Weblate deploy checks

Additional context

[github-actions]

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger.

In case your question is already answered, making a donation is the right way to say thank you!

[nijel]

Maybe the Celery process has different PATH? It could not find the VCS binaries then...

[erictapen]

Ok that was an easy one. Simply oversaw that the celery unit indeed had a different path as all the other units. Thanks @nijel!

[github-actions]

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.

• In case you see a similar problem, please open a separate issue.
• If you are happy with the outcome, don’t hesitate to support Weblate by making a donation.

[nijel]

I've added logging of the system checks in Celery when running in debug mode. This should help in finding such configuration issues, see 3b9a5b0.