[Django] #34509: Celery task throwing error

4 views
Skip to first unread message

Django

unread,
Apr 22, 2023, 5:48:41 AM4/22/23
to django-...@googlegroups.com
#34509: Celery task throwing error
-------------------------------------------+------------------------
Reporter: rakshithxaloori | Owner: nobody
Type: Bug | Status: new
Component: Utilities | Version: 4.2
Severity: Normal | Keywords: celery
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------------+------------------------
A celery task is throwing the below error with Django 4.2 but downgrading
to Django 4.1 fixes the issue.
------------
[2023-04-22 09:38:48,978: ERROR/MainProcess] Process 'ForkPoolWorker-8'
pid:9717 exited with 'signal 11 (SIGSEGV)'
[2023-04-22 09:38:48,994: ERROR/MainProcess] Task handler raised error:
WorkerLostError('Worker exited prematurely: signal 11 (SIGSEGV) Job: 0.')
Traceback (most recent call last):
File "/Users/rick/django/venv/lib/python3.9/site-
packages/billiard/pool.py", line 1265, in mark_as_worker_lost
raise WorkerLostError(
billiard.exceptions.WorkerLostError: Worker exited prematurely: signal 11
(SIGSEGV) Job: 0.

--
Ticket URL: <https://code.djangoproject.com/ticket/34509>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Apr 22, 2023, 6:07:43 AM4/22/23
to django-...@googlegroups.com
#34509: Celery task throwing error
---------------------------------+--------------------------------------
Reporter: Rakshith Aloori | Owner: nobody
Type: Bug | Status: closed
Component: Utilities | Version: 4.2
Severity: Normal | Resolution: invalid

Keywords: celery | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):

* status: new => closed
* resolution: => invalid


Comment:

Thanks for the ticket, however it's not an issue tracker for Celery.

--
Ticket URL: <https://code.djangoproject.com/ticket/34509#comment:1>

Reply all
Reply to author
Forward
0 new messages