the worker by executing our program with the worker argument: $ celery -A tasks worker --loglevel=info Note See the Troubleshooting section if the worker doesn’t start. In production you’ll want to start the worker (you need to run the worker in the directory above proj): $ celery -A proj worker -l info When the worker starts you should see a banner and some messages: -------------- celery@halcyon multi start w1 -A proj -l info celery multi v4.0.0 (latentcall) > Starting nodes... > w1.halcyon.local: OK You can restart it too: $ celery multi restart w1 -A proj -l info celery multi v4.0.0 (latentcall)

the worker by executing our program with the worker argument: $ celery -A tasks worker --loglevel=info Note See the Troubleshooting section if the worker doesn’t start. In production you’ll want to start the worker (you need to run the worker in the directory above proj): $ celery -A proj worker -l info When the worker starts you should see a banner and some messages: -------------- celery@halcyon multi start w1 -A proj -l info celery multi v4.0.0 (latentcall) > Starting nodes... > w1.halcyon.local: OK You can restart it too: $ celery multi restart w1 -A proj -l info celery multi v4.0.0 (latentcall)

the worker by executing our program with the worker argument: $ celery -A tasks worker --loglevel=info Note See the Troubleshooting section if the worker doesn’t start. In production you’ll want to start the worker (you need to run the worker in the directory above proj): $ celery -A proj worker -l info When the worker starts you should see a banner and some messages: -------------- celery@halcyon multi start w1 -A proj -l info celery multi v4.0.0 (latentcall) > Starting nodes... > w1.halcyon.local: OK You can restart it too: $ celery multi restart w1 -A proj -l info celery multi v4.0.0 (latentcall)

the worker by executing our program with the worker argument: $ celery -A tasks worker --loglevel=info Note See the Troubleshooting section if the worker doesn’t start. In production you’ll want to start the worker (you need to run the worker in the directory above proj): $ celery -A proj worker -l info When the worker starts you should see a banner and some messages: --------------- celery@halcyon multi start w1 -A proj -l info celery multi v4.0.0 (latentcall) > Starting nodes... > w1.halcyon.local: OK You can restart it too: $ celery multi restart w1 -A proj -l info celery multi v4.0.0 (latentcall)

the worker by executing our program with the worker argument: $ celery -A tasks worker --loglevel=info Note See the Troubleshooting section if the worker doesn’t start. In production you’ll want to start the worker (you need to run the worker in the directory above proj): $ celery -A proj worker -l info When the worker starts you should see a banner and some messages: --------------- celery@halcyon multi start w1 -A proj -l info celery multi v4.0.0 (latentcall) > Starting nodes... > w1.halcyon.local: OK You can restart it too: $ celery multi restart w1 -A proj -l info celery multi v4.0.0 (latentcall)

the worker by executing our program with the worker argument: $ celery -A tasks worker --loglevel=info Note See the Troubleshooting section if the worker doesn’t start. In production you’ll want to start the worker (you need to run the worker in the directory above proj): $ celery -A proj worker -l info When the worker starts you should see a banner and some messages: -------------- celery@halcyon multi start w1 -A proj -l info celery multi v4.0.0 (latentcall) > Starting nodes... > w1.halcyon.local: OK You can restart it too: $ celery multi restart w1 -A proj -l info celery multi v4.0.0 (latentcall)

the worker by executing our program with the worker argument: $ celery -A tasks worker --loglevel=info Note See the Troubleshooting section if the worker doesn’t start. In production you’ll want to start the worker (you need to run the worker in the directory above proj): $ celery -A proj worker -l info When the worker starts you should see a banner and some messages: --------------- celery@halcyon multi start w1 -A proj -l info celery multi v4.0.0 (latentcall) > Starting nodes... > w1.halcyon.local: OK You can restart it too: $ celery multi restart w1 -A proj -l info celery multi v4.0.0 (latentcall)

the worker by executing our program with the worker argument: $ celery -A tasks worker --loglevel=info Note See the Troubleshooting section if the worker doesn’t start. In production you’ll want to start the worker (you need to run the worker in the directory above proj): $ celery -A proj worker -l info When the worker starts you should see a banner and some messages: --------------- celery@halcyon multi start w1 -A proj -l info celery multi v4.0.0 (latentcall) > Starting nodes... > w1.halcyon.local: OK You can restart it too: $ celery multi restart w1 -A proj -l info celery multi v4.0.0 (latentcall)

the worker by executing our program with the worker argument: $ celery -A tasks worker --loglevel=info Note See the Troubleshooting section if the worker doesn’t start. In production you’ll want to start the worker (you need to run the worker in the directory above proj): $ celery -A proj worker -l info When the worker starts you should see a banner and some messages: --------------- celery@halcyon multi start w1 -A proj -l info celery multi v4.0.0 (latentcall) > Starting nodes... > w1.halcyon.local: OK You can restart it too: $ celery multi restart w1 -A proj -l info celery multi v4.0.0 (latentcall)

the worker by executing our program with the worker argument: $ celery -A tasks worker --loglevel=info Note See the Troubleshooting section if the worker doesn’t start. In production you’ll want to start the worker (you need to run the worker in the directory above proj): $ celery -A proj worker -l info When the worker starts you should see a banner and some messages: --------------- celery@halcyon multi start w1 -A proj -l info celery multi v4.0.0 (latentcall) > Starting nodes... > w1.halcyon.local: OK You can restart it too: $ celery multi restart w1 -A proj -l info celery multi v4.0.0 (latentcall)