Geek Answers Handbook

Celery stuck in the mix: finding neighbors, not getting ready

I used celery for my project using 10 threads. It worked great. Now when I use the command:

celery -A tasks worker --loglevel=info --concurrency 10

celery stuck in:

 [2014-08-07 12:55:21,013: INFO/MainProcess] Connected to amqp://guest:**@127.0.0.1:5672// [2014-08-07 12:55:21,025: INFO/MainProcess] mingle: searching for neighbors

he previously showed the state is ready after that.

and when I try to finish this with ctrl + c , it does not shut down.

 [2014-08-07 12:55:21,013: INFO/MainProcess] Connected to amqp://guest:**@127.0.0.1:5672// [2014-08-07 12:55:21,025: INFO/MainProcess] mingle: searching for neighbors ^C worker: Hitting Ctrl+C again will terminate all running tasks! worker: Warm shutdown (MainProcess) ^C worker: Cold shutdown (MainProcess) ^C worker: Cold shutdown (MainProcess) ^C worker: Cold shutdown (MainProcess) ^C worker: Cold shutdown (MainProcess) ^C worker: Cold shutdown (MainProcess) ^C worker: Cold shutdown (MainProcess)

I even tried to assign the task to workers, but it does not work.

I want celery to be ready? can anyone help?

I also need the right way to finish the celery process, including tasks, annd worker queues. thanks.

+7
python celery
source share
4 answers

Check free disk space. By default, RabbitMQ requires 1 GB of free space.

+4
source share

For more information, RabbitMQ requires 1Gb if offline. If you are using a RabbitMQ all cluster, the cluster must have 1 GB of free space.

+1
source share

If you use a database backend, adding the following parameters to celery should solve the problem: --without-gossip --without-mingle .

See the related issue on github.

0
source share

This problem occurred due to a failure of the RabbitMQ message broker, the restart of which worked.

0
source share

More articles:


All Articles