- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Elasticsearch error
Hi,
In a 3 node vIDM 2.8.1 cluster I get the following error on the dashboard:
Following the steps on the documentation didn´t solve the issue
The status is green, but still the error on the dashboard.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Have the same problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same issue for us after upgrade to 2.8.1.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The messaging connection test is related to the RabbitMQ service not Elastic Search. I'm still trying to find an answer as to why that test is failing in our 3-node cluster. No functionality seems to be lost but error message is concerning.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Have you tried KB articles 2146170 and 2146545 for the Rabitmq Cluster issue.
Please let me know If the solution from above KB articles helped to fix the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am having the same issue and have not been able to solve it. I tried the rabbitmq troubleshooting steps but no luck.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Has anyone come up with a good solution for this? The KB articles referenced did not help. It seems like a complete waste of time to have to restart servers until you get them up in the correct order. There has to be something that can be scripted differently.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We got rid of our mutti-node vIDM deployment all together. Way too many issues like this were occurring. The problems didn't outweigh the HA and Load Balancing that the multi-node deployment offered. Will revisit once they improve this part of the product.