
Updating RabbitMQ Serv-
er for Resource Manager 4.2.2
61
On each remote hub
ssh zenoss@remote-hub
zenoss stop
On the Resource Manager master
ssh root@master
service zenoss stop
4. Examine the RabbitMQ queues:
rabbitmqctl list_queues -p /zenoss
Your output should be similar to:
Listing queues ...
zenoss.queues.modelrequests.vmware 0
zenoss.queues.zep.migrated.summary 0
zenoss.queues.hub.invalidations.localhost:8789 0
zenoss.queues.zep.migrated.archive 0
zenoss.queues.hub.collectorcalls.localhost:8789 0
zenoss.queues.zep.rawevents 0
zenoss.queues.zep.heartbeats 0
zenoss.queues.zep.zenevents 0
zenoss.queues.zep.signal 0
zenoss.queues.zep.modelchange 0
...done.
Warning
Upgrading RabbitMQ will erase all exchanges and queries. All messages that have not been consumed
will be lost. If you notice any non-zero queues, then contact Zenoss Support before continuing.
If you have customizations or ZenPacks that are not Zenoss-supported and use RabbitMQ, ensure that
all of the messages in the relevant queues are consumed before continuing upgrade. Consult the provider
of the customizations for help regarding the sensitivity of lost messages.
5. Enter the following commands to quiesce RabbitMQ:
service rabbitmq-server stop
service rabbitmq-server status
You should see output similar to:
Status of all running nodes...
Error: no_nodes_running
6. Perform the RabbitMQ upgrade on the Resource Manager master:
yum localupdate rabbitmq-server-2.8.6-1.noarch.rpm
7. Start the RabbitMQ server:
service rabbitmq-server start
8. Create a script to restore the RabbitMQ configuration for use with Resource Manager:
a. Create a file named configure_amqp.sh.
b. Add the following content to the file:
#!/bin/sh
RABBITMQ_USER=zenoss
RABBITMQ_PASS=zenoss
RABBITMQ_VHOST=/zenoss
configure_amqp() {
RABBITMQCTL="`which rabbitmqctl`"
if [ ! -z "$RABBITMQCTL" ]; then
Kommentare zu diesen Handbüchern