VMware PACKAGE MANAGER 1.1 Bedienungsanleitung PDF herunterladen (Seite 84)

Upgrading RabbitMQ Server

exit

3. Log in to each hub host, and stop Resource Manager daemons.

ssh root@remote-hub-host

service zenoss stop

exit

4. Log in to the Resource Manager master host as user zenoss, and stop all daemons.

zenoss stop

Occasionally, the stop command does not terminate all of the Resource Manager daemons. To check, enter the

following command:

pgrep -fl ${ZENHOME}

If the pgrep command returns a result, kill the processes.

pkill -f ${ZENHOME}

A.3. Stop RabbitMQ Server

1. Check 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 erases 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 use RabbitMQ and are not Zenoss-supported, ensure that all

of the messages in the relevant queues are consumed before continuing this upgrade. Consult the provider

of the customizations for help regarding the sensitivity of lost messages.

2. Stop RabbitMQ.

service rabbitmq-server stop

3. Verify that RabbitMQ is stopped.

service rabbitmq-server status

You should see output similar to:

Status of all running nodes...

Error: no_nodes_running

1 2 ... 79 80 81 82 83 84 85 86 87 88 89 ... 94 95

Keine Kommentare

VMware PACKAGE MANAGER 1.1 Bedienungsanleitung Seite 84