expand_abbreviations.delay(article.pk) Note Django 1.6 (and later) now enables autocommit mode by default, and commit_on_success/commit_manually are deprecated. This means each SQL query is wrapped Troubleshooting If you can’t get the init-scripts to work, you should try running them in verbose mode: # sh -x /etc/init.d/celeryd start This can reveal hints as to why the service won’t start. If commands directly in the arguments to celery amqp, or just start with no arguments to start it in shell-mode: $ celery -A proj amqp -> connecting to amqp://guest@localhost:5672/. -> connected. 1> Here 1> is

expand_abbreviations.delay(article.pk) Note Django 1.6 (and later) now enables autocommit mode by default, and commit_on_success/commit_manually are deprecated. This means each SQL query is wrapped Troubleshooting If you can’t get the init-scripts to work, you should try running them in verbose mode: # sh -x /etc/init.d/celeryd start This can reveal hints as to why the service won’t start. If commands directly in the arguments to celery amqp, or just start with no arguments to start it in shell-mode: $ celery -A proj amqp -> connecting to amqp://guest@localhost:5672/. -> connected. 1> Here 1> is

commit() expand_abbreviations.delay(article.pk) Note: Django 1.6 (and later) now enables autocommit mode by default, and commit_on_success/commit_manually are deprecated. This means each SQL query is wrapped Troubleshooting If you can’t get the init-scripts to work, you should try running them in verbose mode: # sh -x /etc/init.d/celeryd start This can reveal hints as to why the service won’t start. If commands directly in the arguments to celery amqp, or just start with no arguments to start it in shell-mode: $ celery -A proj amqp -> connecting to amqp://guest@localhost:5672/. -> connected. 1> Here 1> is

Troubleshooting If you can’t get the init-scripts to work, you should try running them in verbose mode: # sh -x /etc/init.d/celeryd start This can reveal hints as to why the service won’t start. If commands directly in the arguments to celery amqp, or just start with no arguments to start it in shell-mode: $ celery -A proj amqp -> connecting to amqp://guest@localhost:5672/. -> connected. 1> Here 1> is delivery_mode=1), routing_key='transient', durable=False), ) or by using task_routes: task_routes = { 'proj.tasks.add': {'queue': 'celery', 'delivery_mode': 'transient'} } The delivery_mode changes

commit() expand_abbreviations.delay(article.pk) Note: Django 1.6 (and later) now enables autocommit mode by default, and commit_on_success/commit_manually are deprecated. This means each SQL query is wrapped Troubleshooting If you can’t get the init-scripts to work, you should try running them in verbose mode: # sh -x /etc/init.d/celeryd start This can reveal hints as to why the service won’t start. If commands directly in the arguments to celery amqp, or just start with no arguments to start it in shell-mode: $ celery -A proj amqp -> connecting to amqp://guest@localhost:5672/. -> connected. 1> Here 1> is

commit() expand_abbreviations.delay(article.pk) Note: Django 1.6 (and later) now enables autocommit mode by default, and commit_on_success/commit_manually are deprecated. This means each SQL query is wrapped Troubleshooting If you can’t get the init-scripts to work, you should try running them in verbose mode: # sh -x /etc/init.d/celeryd start This can reveal hints as to why the service won’t start. If commands directly in the arguments to celery amqp, or just start with no arguments to start it in shell-mode: $ celery -A proj amqp -> connecting to amqp://guest@localhost:5672/. -> connected. 1> Here 1> is

commit() expand_abbreviations.delay(article.pk) Note: Django 1.6 (and later) now enables autocommit mode by default, and commit_on_success/commit_manually are deprecated. This means each SQL query is wrapped Troubleshooting If you can’t get the init-scripts to work, you should try running them in verbose mode: # sh -x /etc/init.d/celeryd start This can reveal hints as to why the service won’t start. If commands directly in the arguments to celery amqp, or just start with no arguments to start it in shell-mode: $ celery -A proj amqp -> connecting to amqp://guest@localhost:5672/. -> connected. 1> Here 1> is

commit() expand_abbreviations.delay(article.pk) Note: Django 1.6 (and later) now enables autocommit mode by default, and commit_on_success/commit_manually are deprecated. This means each SQL query is wrapped Troubleshooting If you can’t get the init-scripts to work, you should try running them in verbose mode: # sh -x /etc/init.d/celeryd start This can reveal hints as to why the service won’t start. If commands directly in the arguments to celery amqp, or just start with no arguments to start it in shell-mode: $ celery -A proj amqp -> connecting to amqp://guest@localhost:5672/. -> connected. 1> Here 1> is

expand_abbreviations.delay(article.pk) Note Django 1.6 (and later) now enables autocommit mode by default, and commit_on_success/commit_manually are deprecated. This means each SQL query is wrapped Troubleshooting If you can’t get the init-scripts to work, you should try running them in verbose mode: # sh -x /etc/init.d/celeryd start This can reveal hints as to why the service won’t start. If commands directly in the arguments to celery amqp, or just start with no arguments to start it in shell-mode: $ celery -A proj amqp -> connecting to amqp://guest@localhost:5672/. -> connected. 1> Here 1> is

expand_abbreviations.delay(article.pk) Note Django 1.6 (and later) now enables autocommit mode by default, and commit_on_success/commit_manually are deprecated. This means each SQL query is wrapped Troubleshooting If you can’t get the init-scripts to work, you should try running them in verbose mode: # sh -x /etc/init.d/celeryd start This can reveal hints as to why the service won’t start. If commands directly in the arguments to celery amqp, or just start with no arguments to start it in shell-mode: $ celery -A proj amqp -> connecting to amqp://guest@localhost:5672/. -> connected. 1> Here 1> is