[Question] - The issue of starting Celery in Django.Suspected to be related to LOGGING

[AhaozZ]

I tried using celery in django according to the tutorial, but I couldn't start it properly and got celery@xxx ready. The program will stop at mingle: all alone.

Settings:

Python: 3.10.12
Django: 4.2.3
Celery version: 5.3.6

I used default django settings.py and add LOGGING into settings.py:

from pathlib import Path

BASE_DIR = Path(__file__).resolve().parent.parent


SECRET_KEY = 'django-insecure-f_m-bx_@&oj7=*cyir$j(j%v$)a3zp@y5$4k@+*-j_ie_bcfmt'

DEBUG = True

ALLOWED_HOSTS = ["*"]


INSTALLED_APPS = [
    'django.contrib.admin',
    'django.contrib.auth',
    'django.contrib.contenttypes',
    'django.contrib.sessions',
    'django.contrib.messages',
    'django.contrib.staticfiles',
]

MIDDLEWARE = [
    'django.middleware.security.SecurityMiddleware',
    'django.contrib.sessions.middleware.SessionMiddleware',
    'django.middleware.common.CommonMiddleware',
    'django.middleware.csrf.CsrfViewMiddleware',
    'django.contrib.auth.middleware.AuthenticationMiddleware',
    'django.contrib.messages.middleware.MessageMiddleware',
    'django.middleware.clickjacking.XFrameOptionsMiddleware',
]

ROOT_URLCONF = 'celery_demo.urls'

TEMPLATES = [
    {
        'BACKEND': 'django.template.backends.django.DjangoTemplates',
        'DIRS': [],
        'APP_DIRS': True,
        'OPTIONS': {
            'context_processors': [
                'django.template.context_processors.debug',
                'django.template.context_processors.request',
                'django.contrib.auth.context_processors.auth',
                'django.contrib.messages.context_processors.messages',
            ],
        },
    },
]

WSGI_APPLICATION = 'celery_demo.wsgi.application'


# Database
# https://docs.djangoproject.com/en/4.2/ref/settings/#databases

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.sqlite3',
        'NAME': BASE_DIR / 'db.sqlite3',
    }
}


# Password validation
# https://docs.djangoproject.com/en/4.2/ref/settings/#auth-password-validators

AUTH_PASSWORD_VALIDATORS = [
    {
        'NAME': 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator',
    },
    {
        'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator',
    },
    {
        'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator',
    },
    {
        'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator',
    },
]


# Internationalization
# https://docs.djangoproject.com/en/4.2/topics/i18n/

LANGUAGE_CODE = 'en-us'

TIME_ZONE = 'UTC'

USE_I18N = True

USE_TZ = True


# Static files (CSS, JavaScript, Images)
# https://docs.djangoproject.com/en/4.2/howto/static-files/

STATIC_URL = 'static/'

# Default primary key field type
# https://docs.djangoproject.com/en/4.2/ref/settings/#default-auto-field

DEFAULT_AUTO_FIELD = 'django.db.models.BigAutoField'

CELERY_BROKER_URL = "redis://127.0.0.1:6379/1"
CELERY_RESULT_BACKEND = "redis://127.0.0.1:6379/2"
CELERY_BROKER_CONNECTION_RETRY_ON_STARTUP = True

LOGGING = {
    "version": 1
}

I am running the worker with the following options:
celery -A celery_demo worker -l INFO

Celery report

 -------------- celery@DESKTOP-G14ISDA v5.3.6 (emerald-rush)
--- ***** -----
-- ******* ---- Linux-5.15.133.1-microsoft-standard-WSL2-x86_64-with-glibc2.35 2024-01-31 15:53:28
- *** --- * ---
- ** ---------- [config]
- ** ---------- .> app:         celery_demo:0x7fca231d6ec0
- ** ---------- .> transport:   redis://127.0.0.1:6379/1
- ** ---------- .> results:     redis://127.0.0.1:6379/2
- *** --- * --- .> concurrency: 16 (prefork)
-- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
--- ***** -----
 -------------- [queues]
                .> celery           exchange=celery(direct) key=celery


[tasks]
  . celery_demo.celery.debug_task

[2024-01-31 15:53:29,169: INFO/MainProcess] Connected to redis://127.0.0.1:6379/1
[2024-01-31 15:53:29,172: INFO/MainProcess] mingle: searching for neighbors
[2024-01-31 15:53:30,181: WARNING/MainProcess] /home/zenu/celery_demo/venv/lib/python3.10/site-packages/celery/app/control.py:56: DuplicateNodenameWarning: Received multiple replies from node name: celery@DESKTOP-G14ISDA.
Please make sure you give each node a unique nodename using
the celery worker `-n` option.
  warnings.warn(DuplicateNodenameWarning(

[2024-01-31 15:53:30,181: INFO/MainProcess] mingle: all alone

When I comment LOGGING, it seems that Celery started normally:

 -------------- celery@DESKTOP-G14ISDA v5.3.6 (emerald-rush)
--- ***** -----
-- ******* ---- Linux-5.15.133.1-microsoft-standard-WSL2-x86_64-with-glibc2.35 2024-01-31 16:15:26
- *** --- * ---
- ** ---------- [config]
- ** ---------- .> app:         celery_demo:0x7fe8302ceec0
- ** ---------- .> transport:   redis://127.0.0.1:6379/1
- ** ---------- .> results:     redis://127.0.0.1:6379/2
- *** --- * --- .> concurrency: 16 (prefork)
-- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
--- ***** -----
 -------------- [queues]
                .> celery           exchange=celery(direct) key=celery


[tasks]
  . celery_demo.celery.debug_task

[2024-01-31 16:15:27,472: INFO/MainProcess] Connected to redis://127.0.0.1:6379/1
[2024-01-31 16:15:27,475: INFO/MainProcess] mingle: searching for neighbors
[2024-01-31 16:15:28,484: WARNING/MainProcess] /home/zenu/celery_demo/venv/lib/python3.10/site-packages/celery/app/control.py:56: DuplicateNodenameWarning: Received multiple replies from node name: celery@DESKTOP-G14ISDA.
Please make sure you give each node a unique nodename using
the celery worker `-n` option.
  warnings.warn(DuplicateNodenameWarning(

[2024-01-31 16:15:28,484: INFO/MainProcess] mingle: all alone
[2024-01-31 16:15:28,490: INFO/MainProcess] celery@DESKTOP-G14ISDA ready.