Skip to content
DataMiner DoJo

More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
Search in posts
Search in pages
Log in
Menu
  • Updates & Insights
  • Questions
  • Learning
    • E-learning Courses
    • Empower Replay: Limited Edition
    • Tutorials
    • Open Classroom Training
    • Certification
      • DataMiner Fundamentals
      • DataMiner Configurator
      • DataMiner Automation
      • Scripts & Connectors Developer: HTTP Basics
      • Scripts & Connectors Developer: SNMP Basics
      • Visual Overview – Level 1
      • Verify a certificate
    • YouTube Videos
    • Solutions & Use Cases
      • Solutions
      • Use Case Library
    • Agility
      • Book your Agile Fundamentals training
      • Book you Kanban workshop
      • Learn more about Agile
        • Agile Webspace
        • Everything Agile
          • The Agile Manifesto
          • Best Practices
          • Retro Recipes
        • Methodologies
          • The Scrum Framework
          • Kanban
          • Extreme Programming
        • Roles
          • The Product Owner
          • The Agile Coach
          • The Quality & UX Coach (QX)
    • >> Go to DataMiner Docs
  • DevOps
    • About the DevOps Program
    • Sign up for the DevOps Pogram
    • DataMiner DevOps Support
    • Feature Suggestions
  • Swag Shop
  • Downloads
  • PARTNERS
    • All Partners
    • Technology Partners
    • Strategic Partner Program
    • Solutions
    • Deal Registration
  • Contact
    • Sales, Training & Certification
    • DataMiner Support
    • Global Feedback Survey
  • >> Go to dataminer.services

Unable to connect to Elasticsearch

Solved1.93K views21st September 2023Elasticsearch
1
Edib Šupić [SLC] [DevOps Catalyst]2.15K 21st September 2023 2 Comments

Hello,

I'm having issues with local DMA where I get error "Retrieving the service definitions failed." upon opening the Cube. I have Elasticsearch installed locally and everything worked fine until I installed Hyper-V and virtual adapters with it. I tried reinstalling the Elasticsearch and the issue was fixed but only until the first restart of the system. I have checked other similar questions, but none of them seem to work in my case.

This is the error I get in SLErrors:

This is the error I used to get before I deleted these interfaces from regedit(they were empty, and there were multiple interfaces this is just one of them):

SLASPConnection.txt|SLASPConnection.exe 10.3.2243.15574|9652|30792|CServiceModule::LoadIPAddresses|ERR|-1|Error 2 while fetching IP adapter info for SYSTEM\\CurrentControlSet\\Services\\Tcpip\\Parameters\\Interfaces\\{065D3EB3-4F67-46C1-9415-DE43DAD5EC42} (DHCP=1)

These are alarms I get in the Cube:

Edib Šupić [SLC] [DevOps Catalyst] Selected answer as best 21st September 2023
Miguel Obregon [SLC] [DevOps Catalyst] commented 21st September 2023

Hi Edib,
Small question, checking quickly the error from SLErrors I see the following address: 172.27.240:9200. Since you are running an Elasticsearch node locally, is it not an option to use localhost (127.0.0.1) in DB.xml?

Edib Šupić [SLC] [DevOps Catalyst] commented 21st September 2023

I am using localhost in DB.xml, I am wondering where this IP is coming from too. I feel like important part is that everything was working fine before I installed Hyper-V, so I’m guessing the issue has to do something with that, but I’ve been known to be wrong in the past.
Elastic was installed as standalone and not through DataMiner Cube, because Cube doesn’t allow Cassandra and Elastic to be on the same drive.

2 Answers

  • Active
  • Voted
  • Newest
  • Oldest
2
Robbe De Ghein [SLC] [DevOps Advocate]850 Posted 21st September 2023 1 Comment

Hi Edib,

I believe this IP is coming from inter node communication.
The node is trying to sniff the cluster configuration.

The virtual adapters are messing with Elastic's IP.

I have the same problem when running elasticsearch inside docker containers.

I solved it by filling in the following settings:
network.publish_host=<the ip from the right adapter>
http.publish_port=9200

Edib Šupić [SLC] [DevOps Catalyst] Selected answer as best 21st September 2023
Edib Šupić [SLC] [DevOps Catalyst] commented 21st September 2023

This is the solution. I didn’t want to hard code the IP address so I used _local_ instead and it seems to be working. I say seems to because after I changed the IP from 0.0.0.0 to IP of the adapter it worked, but then when I changed it back to 0.0.0.0 it still worked, I guess some caching is happening. Also I didn’t have to configure publish_port but I will experiment more with it later, for now this is fine. Thank you.

You are viewing 1 out of 2 answers, click here to view all answers.
Please login to be able to comment or post an answer.

My DevOps rank

DevOps Members get more insights on their profile page.

My user earnings

0 Dojo credits

Spend your credits in our swag shop.

0 Reputation points

Boost your reputation, climb the leaderboard.

Promo banner DataMiner DevOps Professiona Program
DataMiner Integration Studio (DIS)
Empower Katas
Privacy Policy • Terms & Conditions • Contact

© 2025 Skyline Communications. All rights reserved.

DOJO Q&A widget

Can't find what you need?

? Explore the Q&A DataMiner Docs

[ Placeholder content for popup link ] WordPress Download Manager - Best Download Management Plugin