by adding the -detached option (note: only one dash): $ sudo rabbitmq-server -detached Never use kill to stop the RabbitMQ server, but rather use the rabbitmqctl command: $ sudo rabbitmqctl stop When anything drastic (like sending the KILL signal). If the worker won’t shutdown after considerate time, for example because of tasks stuck in an infinite-loop, you can use the KILL signal to force terminate the currently executing tasks will be lost (unless the tasks have the acks_late option set). Also, since the KILL signal can’t be catched by processes the worker will not be able to reap its children so make sure

by adding the -detached option (note: only one dash): $ sudo rabbitmq-server -detached Never use kill to stop the RabbitMQ server, but rather use the rabbitmqctl command: $ sudo rabbitmqctl stop When tasks are important you should wait for it to finish before doing anything drastic (like sending the KILL signal). 36 Chapter 2. User Guide Celery Documentation, Release 2.3.5 If the worker won’t shutdown the KILL signal to force terminate the worker, but be aware that currently executing tasks will be lost (unless the tasks have the acks_late option set). Also as processes can’t override the KILL signal

by adding the -detached option (note: only one dash): $ sudo rabbitmq-server -detached Never use kill to stop the RabbitMQ server, but rather use the rabbitmqctl command: $ sudo rabbitmqctl stop When anything drastic (like sending the KILL signal). If the worker won’t shutdown after considerate time, for example because of tasks stuck in an infinite-loop, you can use the KILL signal to force terminate the currently executing tasks will be lost (unless the tasks have the acks_late option set). Also, since the KILL signal can’t be catched by processes the worker will not be able to reap its children so make sure

by adding the -detached option (note: only one dash): $ sudo rabbitmq-server -detached Never use kill to stop the RabbitMQ server, but rather use the rabbitmqctl command: $ sudo rabbitmqctl stop When anything drastic (like sending the KILL signal). If the worker won’t shutdown after considerate time, for example because of tasks stuck in an infinite-loop, you can use the KILL signal to force terminate the override the KILL signal, the worker will not be able to reap its children, so make sure to do so manually. This command usually does the trick: $ ps auxww | grep celeryd | awk ’{print $2}’ | xargs kill -9 2

by adding the -detached option (note: only one dash): $ sudo rabbitmq-server -detached Never use kill to stop the RabbitMQ server, but rather use the rabbitmqctl command: $ sudo rabbitmqctl stop When anything drastic (like sending the KILL signal). If the worker won’t shutdown after considerate time, for example because of tasks stuck in an infinite-loop, you can use the KILL signal to force terminate the the KILL signal, the worker will not be able to reap its children, so make sure to do so manually. This command usually does the trick: $ ps auxww | grep celeryd | awk '{print $2}' | xargs kill -9 Restarting

by adding the -detached option (note: only one dash): $ sudo rabbitmq-server -detached Never use kill to stop the RabbitMQ server, but rather use the rabbitmqctl command: $ sudo rabbitmqctl stop When anything drastic (like sending the KILL signal). If the worker won’t shutdown after considerate time, for example because of tasks stuck in an infinite-loop, you can use the KILL signal to force terminate the the KILL signal, the worker will not be able to reap its children, so make sure to do so manually. This command usually does the trick: $ ps auxww | grep celeryd | awk '{print $2}' | xargs kill -9 Restarting

by adding the -detached option (note: only one dash): $ sudo rabbitmq-server -detached Never use kill to stop the RabbitMQ server, but rather use the rabbitmqctl command: $ sudo rabbitmqctl stop When tasks are important you should wait for it to finish before doing anything drastic (like sending the KILL signal). 42 Chapter 2. User Guide Celery Documentation, Release 2.5.5 If the worker won’t shutdown the KILL signal to force terminate the worker, but be aware that currently executing tasks will be lost (unless the tasks have the acks_late option set). Also as processes can’t override the KILL signal

by adding the -detached option (note: only one dash): $ sudo rabbitmq-server -detached Never use kill to stop the RabbitMQ server, but rather use the rabbitmqctl command: $ sudo rabbitmqctl stop When tasks are important you should wait for it to finish before doing anything drastic (like sending the KILL signal). 44 Chapter 2. User Guide Celery Documentation, Release 2.4.7 If the worker won’t shutdown the KILL signal to force terminate the worker, but be aware that currently executing tasks will be lost (unless the tasks have the acks_late option set). Also as processes can’t override the KILL signal

by adding the -detached option (note: only one dash): $ sudo rabbitmq-server -detached Never use kill to stop the RabbitMQ server, but rather use the rabbitmqctl command: $ sudo rabbitmqctl stop When anything drastic (like sending the KILL signal). If the worker won’t shutdown after considerate time, for example because of tasks stuck in an infinite-loop, you can use the KILL signal to force terminate the override the KILL signal, the worker will not be able to reap its children, so make sure to do so manually. This command usually does the trick: $ ps auxww | grep celeryd | awk '{print $2}' | xargs kill -9 Restarting

adding the -detached option (note: only one dash): $ sudo rabbitmq-server -detached Never use kill (kill(1)) to stop the RabbitMQ server, but rather use the rabbitmqctl command: $ sudo rabbitmqctl stop convenient for making sure all tasks return in a timely manner, but a time limit event will actually kill the process by force so only use them to detect cases where you haven’t used manual timeouts yet. anything drastic, like sending the KILL signal. If the worker won’t shutdown after considerate time, for being stuck in an infinite-loop or similar, you can use the KILL signal to force terminate the worker: