ERROR EndpointCoordinator.Communication.RabbitMQ.CommunicationManager - Failed to get connection to localhost
Originally Published: 2016-03-24
Article Number
Applies To
RSA Product/Service Type: Enterprise Manager
RSA Version/Condition: 9.6 SP2P04
Platform: Windows server 2008R2
Issue
2- RSA DLP Message Broker service persistently fail to get started.
3- All Endpoint coordinators appears offline on EM GUI.
Cause
Install_dir\EndpointCoordinator\RabbitMQ\AppData\rabbitmq.conf
- Error captured related to the problem are as follows:
Apache logs: [Thu Mar 24 11:55:52 2016] [warn] RSA server certificate CommonName (CN) `27df9999-dc36-4e5d-ac70-3312d3d51612' does NOT match server name!? [Thu Mar 24 11:56:06 2016] [error] [client 10.167.8.39] ERROR: Failed to establish connection to message broker [Thu Mar 24 11:56:06 2016] [error] [client 10.167.8.39] ERROR: Failed to send agent heartbeat EPCservice logs: 2016-03-24 11:55:53,349 [ServiceMonitor-9] ERROR EndpointCoordinator.Tasks.MonitorService.RabbitMonitorTask - RabbitMQ is down... polling the server until it starts back up. 2016-03-24 11:55:47,233 [17] ERROR EndpointCoordinator.Tasks.MonitorService.EventBroadcastTask - Exception thrown during processing of notifications. System.Threading.ThreadAbortException: Thread was being aborted. RabbitMQ logs: Line 561824: SSL: hello: ssl_handshake.erl:156:Fatal error: insufficient security
Resolution
Install_dir\EndpointCoordinator\RabbitMQ\AppData\rabbitmq.conf
2 - Make sure that there are no corruption in the file by validating it's values to the below parameters:
[
{rabbitmq_stomp, [{tcp_listeners, [{"127.0.0.1", 61613}]},
{default_user, [{login, "gtkzierl2rkxyfdofxypgw"},
{passcode, "xujklnfrwrzo5tcvrllakg"}]},
{implicit_connect, true}]},
{rabbit, [ {tcp_listeners, []},
{ssl_listeners, [5671]},
{ssl_options, [{certfile,"C:\\PROGRA~2\\RSA\\ENDPOI~1\\Certificates\\ServerCert.crt"},
{keyfile,"C:\\PROGRA~2\\RSA\\ENDPOI~1\\Certificates\\ServerKey.key"},
{cacertfile,"C:\\PROGRA~2\\RSA\\ENDPOI~1\\Certificates\\ServerChain.pem"},
{ciphers,[ {rsa,rc4_128,sha},{rsa,rc4_128,md5} ]}
]}
]}
].
3- Restart RSA DLP endpoint coordinator service.
4- Restart RSA DLP file server service.
5- Start RSA DLP Message Broker service.
Related Articles
Troubleshooting Linux/Agent Communication Issues 30Number of Views RSA Authentication Manager Bulk Administration Is Reporting A Communication Error 47Number of Views Database fails to start with ORA-03113: end-of-file on communication channel error in RSA Identity Governance & Lifecycle 88Number of Views PAM agent fails on acetest with error 'Cannot Do AceInitialize for communication with ACE/Server' | RSA Authentication Man… 133Number of Views Customizing Secure Communication 19Number of Views
Don't see what you're looking for?