1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
|
.. _broker-rabbitmq:
================
Using RabbitMQ
================
.. contents::
:local:
Installation & Configuration
============================
RabbitMQ is the default broker so it doesn't require any additional
dependencies or initial configuration, other than the URL location of
the broker instance you want to use:
.. code-block:: python
broker_url = 'amqp://myuser:mypassword@localhost:5672/myvhost'
For a description of broker URLs and a full list of the
various broker configuration options available to Celery,
see :ref:`conf-broker-settings`, and see below for setting up the
username, password and vhost.
.. _installing-rabbitmq:
Installing the RabbitMQ Server
==============================
See `Installing RabbitMQ`_ over at RabbitMQ's website. For macOS
see `Installing RabbitMQ on macOS`_.
.. _`Installing RabbitMQ`: http://www.rabbitmq.com/install.html
.. note::
If you're getting `nodedown` errors after installing and using
:command:`rabbitmqctl` then this blog post can help you identify
the source of the problem:
http://www.somic.org/2009/02/19/on-rabbitmqctl-and-badrpcnodedown/
.. _rabbitmq-configuration:
Setting up RabbitMQ
-------------------
To use Celery we need to create a RabbitMQ user, a virtual host and
allow that user access to that virtual host:
.. code-block:: console
$ sudo rabbitmqctl add_user myuser mypassword
.. code-block:: console
$ sudo rabbitmqctl add_vhost myvhost
.. code-block:: console
$ sudo rabbitmqctl set_user_tags myuser mytag
.. code-block:: console
$ sudo rabbitmqctl set_permissions -p myvhost myuser ".*" ".*" ".*"
Substitute in appropriate values for ``myuser``, ``mypassword`` and ``myvhost`` above.
See the RabbitMQ `Admin Guide`_ for more information about `access control`_.
.. _`Admin Guide`: http://www.rabbitmq.com/admin-guide.html
.. _`access control`: http://www.rabbitmq.com/admin-guide.html#access-control
.. _rabbitmq-macOS-installation:
Installing RabbitMQ on macOS
----------------------------
The easiest way to install RabbitMQ on macOS is using `Homebrew`_ the new and
shiny package management system for macOS.
First, install Homebrew using the one-line command provided by the `Homebrew
documentation`_:
.. code-block:: console
ruby -e "$(curl -fsSL https://raw.github.com/Homebrew/homebrew/go/install)"
Finally, we can install RabbitMQ using :command:`brew`:
.. code-block:: console
$ brew install rabbitmq
.. _`Homebrew`: https://github.com/mxcl/homebrew/
.. _`Homebrew documentation`: https://github.com/Homebrew/homebrew/wiki/Installation
.. _rabbitmq-macOS-system-hostname:
After you've installed RabbitMQ with :command:`brew` you need to add the following to
your path to be able to start and stop the broker: add it to the start-up file for your
shell (e.g., :file:`.bash_profile` or :file:`.profile`).
.. code-block:: bash
PATH=$PATH:/usr/local/sbin
Configuring the system host name
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you're using a DHCP server that's giving you a random host name, you need
to permanently configure the host name. This is because RabbitMQ uses the host name
to communicate with nodes.
Use the :command:`scutil` command to permanently set your host name:
.. code-block:: console
$ sudo scutil --set HostName myhost.local
Then add that host name to :file:`/etc/hosts` so it's possible to resolve it
back into an IP address::
127.0.0.1 localhost myhost myhost.local
If you start the :command:`rabbitmq-server`, your rabbit node should now
be `rabbit@myhost`, as verified by :command:`rabbitmqctl`:
.. code-block:: console
$ sudo rabbitmqctl status
Status of node rabbit@myhost ...
[{running_applications,[{rabbit,"RabbitMQ","1.7.1"},
{mnesia,"MNESIA CXC 138 12","4.4.12"},
{os_mon,"CPO CXC 138 46","2.2.4"},
{sasl,"SASL CXC 138 11","2.1.8"},
{stdlib,"ERTS CXC 138 10","1.16.4"},
{kernel,"ERTS CXC 138 10","2.13.4"}]},
{nodes,[rabbit@myhost]},
{running_nodes,[rabbit@myhost]}]
...done.
This is especially important if your DHCP server gives you a host name
starting with an IP address, (e.g., `23.10.112.31.comcast.net`). In this
case RabbitMQ will try to use `rabbit@23`: an illegal host name.
.. _rabbitmq-macOS-start-stop:
Starting/Stopping the RabbitMQ server
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To start the server:
.. code-block:: console
$ sudo rabbitmq-server
you can also run it in the background by adding the ``-detached`` option
(note: only one dash):
.. code-block:: console
$ sudo rabbitmq-server -detached
Never use :command:`kill` (:manpage:`kill(1)`) to stop the RabbitMQ server,
but rather use the :command:`rabbitmqctl` command:
.. code-block:: console
$ sudo rabbitmqctl stop
When the server is running, you can continue reading `Setting up RabbitMQ`_.
|
