Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
rabbitmq [2015/12/08 11:46] steve |
rabbitmq [2015/12/08 11:50] steve [Creating a Cluster] |
||
|---|---|---|---|
| Line 74: | Line 74: | ||
| One gotcha to be aware of is that the default cookie set will have no end-of-line for the string. Adding a new line will change the hash. In this case, it may be simpler to just create your own erlang cookie before starting the primary node. | One gotcha to be aware of is that the default cookie set will have no end-of-line for the string. Adding a new line will change the hash. In this case, it may be simpler to just create your own erlang cookie before starting the primary node. | ||
| + | |||
| + | The permissions are also set to read-only for the rabbitmq user. | ||
| + | |||
| + | In this example, I use pwgen to create a random password as well: | ||
| <code> | <code> | ||
| pwgen 8 1 | tee /var/lib/rabbitmq/.erlang.cookie | pwgen 8 1 | tee /var/lib/rabbitmq/.erlang.cookie | ||
| chmod 0600 /var/lib/rabbitmq/.erlang.cookie | chmod 0600 /var/lib/rabbitmq/.erlang.cookie | ||
| + | chown rabbitmq: /var/lib/rabbitmq/.erlang.cookie | ||
| + | </code> | ||
| + | |||
| + | At this point, the primary node is up and running, the cookie exists, and it is ready to have a second node joined to it to create a cluster. | ||
| + | |||
| + | On the second node, the RabbitMQ service is already running as normal, from when we started it earlier. Now, we need to tell rabbitmq to stop the application -- not the service -- so that we can join it to the primary node. | ||
| + | |||
| + | <code> | ||
| + | rabbitmqctl stop_app | ||
| </code> | </code> | ||
