Discussion:
[celery-users] Celery Worker silently exits (exit code 0)
Micah Hausler
10 years ago
Permalink
Hi all,

I'm using Celery with Django for background tasks, and I have in the lats
few weeks had multiple workers just exit (with code 0) without any output.
I'm pretty lost as to where to start debugging, so I'd really appreciate
any help on figuring out how this is happening. I've not changed the
version of celery, django, OS, Redis, or python in months, so I'm very
confused why this is happening.


*Versions*
Ubuntu 12.04

Linux 3.2.0-69-virtual (AWS)



celery==3.1.17

django-celery==3.1.16

Django==1.7.7

redis==2.10.3



Redis 2.8.6

Python 2.7.3

supervisord 3.1.3



*Supervisor Main Log *

2015-07-06 08:49:31,179 INFO exited: ambition_worker_aaaaabbbbb (exit
status 0; expected)


*Supervisor Worker Log*

[2015-07-06 08:49:25,262: INFO/MainProcess] Received task:
xxxx_yyyy.tasks.ConvertEventsToEmails[6219057c-41e4-45c9-bed0-eeabc6699ca9]

[2015-07-06 08:49:25,263: INFO/MainProcess] Ambition Autoscaler:
{'max_prefetch': 4, 'reserved_requests': 1, 'num_processes': 1,
'active_requests': 0}

[2015-07-06 08:49:25,398: INFO/MainProcess] Task xxxx_yyyy.tasks.ConvertEventsToEmails[6219057c-41e4-45c9-bed0-eeabc6699ca9]
succeeded in 0.132920803968s: None



-------------- ***@aaaaabbbbb v3.1.17 (Cipater)

---- **** -----

--- * *** * -- Linux-3.2.0-69-virtual-x86_64-with-Ubuntu-12.04-precise

-- * - **** ---

- ** ---------- [config]

- ** ---------- .> app: production:0x1f22b90

- ** ---------- .> transport:
redis://yyyy.zzzz.0001.use1.cache.amazonaws.com:6379/0

- ** ---------- .> results: redis://yyyy.zzzz
.0001.use1.cache.amazonaws.com:6379/0

- *** --- * --- .> concurrency: {min=1, max=5} (prefork)

-- ******* ----

--- ***** ----- [queues]

-------------- .> ambition-aaaaabbbbb-async exchange=ambition-aaaaabbbbb-async(direct)
key=ambition-aaaaabbbbb-async




[tasks]

. a.x.a.tasks.XxYyZzTask

. a.x.b.tasks.XxYyZzTask

. a.x.c.tasks.XxYyZzTask

. a.x.d.tasks.XxYyZzTask

. a.x.e.tasks.XxYyZzTask

. a.y.f.tasks.XxYyZzTask

. a.y.g.tasks.XxYyZzTask

. a.y.g.tasks.XxYyPhoto

. a.y.h.tasks.XxYyZzTask

. a.y.h.tasks.XxYyTask

. a.z.tasks.XxYyZzTask

. a.a.tasks.XxYyZzTask

. a.a.tasks.XxYyTask

. b.b.XxYyZzTask

. b.b.XxYyZzTask

. c.c.XxYyTask

. c.c.XxTask

. c.c.ZzTask

. d.tasks.XxYyZzTask

. e.tasks.XxYyZzTask

. xxxx_yyyy.tasks.ConvertEventsToEmails

. xxxx_yyyy.tasks.XxYyZzTask

. f.tasks.XxYyZzTask

. g.tasks.XxYyZzTask

. h.x.a._generate_file


[2015-07-06 13:10:30,964: INFO/MainProcess] Connected to redis://yyyy.zzzz
.0001.use1.cache.amazonaws.com:6379/0

[2015-07-06 13:10:30,991: INFO/MainProcess] celery@ aaaaabbbbb ready.



*Command*

command=/var/app/env/bin/newrelic-admin run-python /var/app/manage.py
celery worker \

--hostname=aaaaabbbbb \

--no-execv \

--pool=prefork \

--autoscale=5,1 \

--without-gossip \

--without-mingle \

--maxtasksperchild=100 \

--loglevel=INFO \

--pidfile=/opt/sockets/ambition_worker_aaaaabbbbb.pid \

-Ofair
--
You received this message because you are subscribed to the Google Groups "celery-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to celery-users+***@googlegroups.com.
To post to this group, send email to celery-***@googlegroups.com.
Visit this group at http://groups.google.com/group/celery-users.
For more options, visit https://groups.google.com/d/optout.
Micah Hausler
10 years ago
Permalink
So I figured out that it was the oom-killer, but that is really confusing
why celery exited with code 0!
...
--
You received this message because you are subscribed to the Google Groups "celery-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to celery-users+***@googlegroups.com.
To post to this group, send email to celery-***@googlegroups.com.
Visit this group at http://groups.google.com/group/celery-users.
For more options, visit https://groups.google.com/d/optout.
Loading...