Withdraw of the 6.9.2 Release
Unfortunately, due to critical issues identified with version 6.9.2, we have decided to remove it and ensure it's no longer available for download. These issues impacted the ability to install or upgrade but none were security-related. We are diligently working to resolve these issues and are planning to release an updated version 6.9.3 in early May.
What if you've already upgraded?For customers who have already upgraded to 6.9.2, no immediate action is required, as none of these issues are security-related. Once it's available, you will still be able to upgrade to 6.9.3 as normal. We appreciate your patience and trust as we continue to enhance our software to better serve you. Thank you for your understanding.
Message Queue
Opsview uses messages for all communication between all micro-services, this is based on RabbitMQ. The component is installed into /opt/opsview/messagequeue
.
You can see what queues are set up and in use on the current server by using the following command (each Opsview Monitor server has its own message queue).
sudo -iu opsview /opt/opsview/messagequeue/sbin/rabbitmqctl list_queues
Commonly a collector is clustered with other collectors (always in an odd number, as per rabbitmqs recommendation). To view this information you may run the below.
sudo -iu opsview /opt/opsview/messagequeue/sbin/rabbitmqctl cluster_status
There is also a UI available for RabbitMQ, but you need to use an SSH tunnel to access it
ssh -L 15672:localhost:15672 orchestrator.mydomain.com
You can then use http://localhost:15672
to access the UI and log in using the opsview user credentials stored within the deploy configuration on the Orchestrator.