Troubleshooting RabbitMQ Server

This section helps you troubleshoot the common problems that you might encounter when using certificate server functionalities. Effective troubleshooting documents depend on the availability of useful, detailed information. This guide will give more troubleshooting processes on server addition, deletion, import, export, push, bind, rollback, and other actions associated with RabbitMQ server.

Issues in RabbitMQ Server Addition using AppViewX UI


Error Message	Possible Cause	Possible Solution
Device Name already exists.	A device with the same name already exists in inventory.	Check the Device name, it should be unique.
Details incorrect	Some of the mandatory fields might be missing or might be invalid.	Add all the valid information in the mandatory section.

Issues in Communicating to RabbitMQ Server


Error Message	Possible Cause	Possible Solution
Device name cannot be null or empty.	Device name is empty.	Provide device name as it is a mandatory field.
Invalid device name.	Device Name is not valid.	The Device name can only contain alphanumeric characters, '-' , '_' , '.' , '*' , '\|' , '!' and spaces.
Device IP/FQDN cannot be null or empty.	Device IP/FQDN is empty.	Provide device IP/FQDN as it is a mandatory field.
Invalid device IP/FQDN address.	IP/FQDN address is not valid.	Provide valid IP/FQDN address.
Communication to <ip/fqdn> has failed. Caused by: java.io.IOException: Unable to authenticate with password, keyboard-interactive and publickey methods Possible Remediations: 1. Kindly check the credentials provided.	Password of the device added might be wrong.	Click on the device name on the Inventory Page. Update the correct password and click Save.
Communication to <ip/fqdn> has failed. Caused by: java.net.SocketException: Network is unreachable (connect failed)	IP/FQDN provided is not reachable	Check manually by establishing an SSH session to the target device with the provided IP/FQDN.
Communication to <IP/FQDN> has failed. Caused by: java.net.ConnectException: Connection refused (Connection refused) Possible Remediations: 1. Kindly check the SSH Port configurations. 2. Kindly check the firewall settings	Problem with port configuration	Check if the configured port in the device addition page is correct.
Communication to <IP/FQDN> has failed. Caused by: java.io.IOException: Key exchange was not finished, connection is closed.	Problem with SSH key handshake	Request to check the ciphers, key and HMacs configured in the target device and ensure AppViewX SSH-plugin supports the same
Device version fetch has failed.	Config path is incorrect / No RabbitMQ instances running in the target device	Check manually by establishing an SSH session to the target device and check RabbitMQ installations and find a valid configuration path and update the same in the device addition page.

Issues in Accessing Server

Access Issues might be reproduced when communicating with servers while discovering or fetching configuration files (/etc/rabbitmq/rabbitmq.config). These errors can be collected either from logs, API responses, or in the status field for the particular server.


Error Message	Possible Cause	Possible Solution
Custom Config Location	For default installation, The config location path is /etc/rabbitmq/rabbitmq. config, if any custom location is provided check the valid rabbitmq config file exists in that location	Login via SSH to the target device and check the “rabbitmq” installations and valid configuration file location path
Permission denied for file/location.	1. File might not be present in the avx environment. 2. user might not have permission to read in the given source location 3.Device communication might not be established when service has started.	1.Check whether someone deleted the file from AppViewX environment. 2. Verify if read permission is given for the location. 3.Verify the device connection and restart the service.

Issues in Config Fetch


Error Message	Possible Cause	Possible Solution
Communication to <IP/FQDN> has failed.	Device communication has failed due to invalid credentials / SSH Port	Verify the input details and check for device status error messages in the Issues in Communicating to RabbitMQ Server section.

Issues in Certificate Discovery


Error Message	Possible Cause	Possible Solution
Please provide information as required	Discovery name is not given or the length is less than 2 characters. Interval between batches info. is missing when execution type is sequential.	Enter a valid name with a minimum of 2 characters. Provide a time interval between batches in minutes.
Please select a device	No device is selected in the “Discover By” section.	Select at least one device to discover certificates from.

Issues in CSR generation


Error Message	Possible Cause	Possible Solution
Problem while generating csr on target server	General Failure - SSH/SFTP communication failure	Provide correct credentials and make sure device communication is successful.
Invalid key type specified in the request	Given key type might not be supported by open SSL in the target machine.	Provide valid key type.
Problem while generating csr on the target server.	Location might not have permission.	Check the permission and provide it.
CSR and Private key has been failed	Open SSL configuration might be wrong in the target machine.	Check and correct open SSL configuration in the device.
CSR generation got failed	User has restricted access to the path configured for the “CSR FileName” and “Key File name”	Kindly ensure the user configured for device addition has read/write access to the path configured.

Issues in Push and Rollback


Error Message	Possible Cause	Possible Solution
Unable to initiate request.	Pushing to device when certificate is unavailable, i.e, in a new state. Previous work order is in progress and not completed. AppConnector might not be in sync.	Push to device after certificate has been retrieved from CA. Initiate push after previous work order is finished. Synchronize the AppConnector and retry.
Unable to initiate request, template is in disabled state	Given workflow is not in enabled state	Enable the push/rollback workflow from the Workflow section.
User is not authorized	User does not have required permissions to push to the device.	Retry after getting the access for required action.
Private key content is unavailable.	Private key content is not available for the certificate.	Private key is mandatory for the certificate to be pushed.
Application connector(s) not found	Application connector info was not found.	Provide the correct connectorId if not pushing using AppViewX UI.
Request associated with the application connector is in progress	Previous work order is in progress and not completed.	Initiate this request after the previous work order is finished.
Push not triggered or succeeded or No existing data available for backup process.	Rollback couldn’t proceed because push was not successful.	Only successfully pushed certificates can be rolled back.
Certificate not found.	Pushing to device when certificate is unavailable, i.e, in a new state.	Push to device after certificate has been retrieved from CA.
Certificate Push failed	User has restricted access to the path configured to push the certificate in the application connector	Kindly ensure the user is configured while device addition has the read/write access to the path configured in application connector to certificate push.
PrivateKey in device push invalid	“Private key in Device” is enabled in application connector, but key is not available on device.	Ensure to enable “Private key in Device” attribute in application connector, if the certificate does not have the key and the certificate is generated using CSR gen option from Device.