Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Access Rights Manager (ARM) formerly 8MAN > ARM - Knowledgebase Articles > Alarm configuration error in server health check

Alarm configuration error in server health check

Updated November 19, 2018

Overview

This article details an issue in which there is an error message in the server health check alarm configuration.

Environment

  • Access Rights Manager

Cause

The RabbitMQ service is either not installed or not running properly.

Resolution

Verifiy installation of RabbitMQ service.

  • RabbitMQ service is not installed
    ARM must be completely uninstalled and reinstalled. You will keep your ARM configuration because it is stored in the database.
    Simply repairing the installation file does not successfully resolve this issue. The program must be fully uninstalled to fix the error.
     
  • If RabbitMQ service is installed but continues to stop after repeated manual restarts
    You may receive an error message: RabbitMQ; Erlang machines stopped instantly (distribution name conflict?). The service is not restarted as OnFail is set to ignore.
    The ARM Log file contains the following: RabbitMQ.Client.Exceptions.BrokerUnreachableException: None of the specified endpoints were reachable.
  1. Rename the recovery.dets file located under the path C:\ProgramData\rabbitmq\db\rabbit@YOURSERVER-mnesia\ for example to recovery.dets.bak. 
  2. Restart ARM and RabbitMQ service. Restarting creates a new recovery.dets file, which stabilizes your RabbitMQ service. 
  3. Delete the renamed file.

 

 
Last modified

Tags

Classifications

Public