The Tanzu RabbitMQ OVA troubleshooting information includes solutions (or workarounds) to potential problems that you might encounter when deploying, configuring, and using the Tanzu RabbitMQ OVA (virtual machine).

Networking Information populated in the Configuration Wizard while Importing the OVA does not work on the Virtual Machine

Problem

Networking information for the Tanzu RabbitMQ virtual machine (network IP address: address, default gateway: gateway, and domain name server: DNS) which is populated in the configuration wizard when the OVA is imported does not work after the virtual machine is started and initialization is complete. The network IP address, default gateway, and domain name server are set to invalid. This issue is happening on VMware’s vSphere and VMware’s Workstation virtual machine environments.

Solution

The network card configuration file must be updated manually after the Tanzu RabbitMQ virtual machine starts. After startup, log into the virtual machine and manually modify the virtual machine’s network configuration information to meet the specific requirements of the network environment.

1. Log into the virtual machine using the terminal tool and modify the 99-dhcp-en.network configuration file. If you cannot find the 99-dhcp-en.network file, run the sudo ls /etc/systemd/network/ command to find the correct network configuration file name.

   sudo vim /etc/systemd/network/99-dhcp-en.network
   

2. Modify the hostname (server name):

   sudo vim /etc/hostname
   

3. Modify the hosts file:

   sudo vim /etc/hosts
   

Delete or comment out 127.0.0.1 photon and add the actual IP address and hostname to the hosts file.

Know how to View RabbitMQ Logs

Problem

Know how to view the logs when the Tanzu RabbitMQ service is not running properly or when it fails.

Solution

The Tanzu RabbitMQ OVA does not write error logs to a dedicated RabbitMQ log file by default so to check why the Tanzu RabbitMQ Service (bitnami.vmware-tanzu-rabbitmq) is not running, run this command:

sudo journalctl -u bitnami.vmware-tanzu-rabbitmq

RabbitMQ Service is Started but some Ports cannot be Accessed

Problem

The RabbitMQ Service (bitnami.vmware-tanzu-rabbitmq) is started but the client cannot access some ports (usually non-default ports). This issue can occur when non-default ports are used or you are modifying a default port.

Solution

First check that the Rabbit service on the port is started by running the following command. If you cannot find the lsof command, you can install it using sudo yum install lsof -y.

sudo lsof -i:5672

If the RabbitMQ service is started but you changed the default port number, to use port 5671, for example, or you enabled Stream queuing (using port 5552), then you must either open the new port number in the firewall or turn off the firewall. To turn off the firewall, run:

sudo systemctl disable iptables.service

Note, by default, the firewall in the Tanzu RabbitMQ OVA virtual machine is automatically turned on and these ports: 22/4369/5672/25672/15672 are open and available to use.