Eureka client registers with wrong IP address

[Gaël Marziou]

Hi all,

On my Linux machine where Docker is installed, I found that the gateway registers using docker0 IP address (172.x.x.x), as a result when I go in the registry dashboard and I click on the gateway link it does not work.
More important, the Eureka server cannot check that the client is up and this is probably why I get this warning:

EMERGENCY! EUREKA MAY BE INCORRECTLY CLAIMING INSTANCES ARE UP WHEN THEY'RE NOT. RENEWALS ARE LESSER THAN THRESHOLD AND HENCE THE INSTANCES ARE NOT BEING EXPIRED JUST TO BE SAFE.

This is caused by the Eureka client which does not respect server.address property and uses default detection in org.springframework.cloud.util.InetUtils#getFirstNonLoopbackAddress which finds docker0 address.

I commented on 2 related issues:

https://github.com/spring-cloud/spring-cloud-netflix/issues/815

https://github.com/spring-cloud/spring-cloud-commons/issues/88

Hopefully spring-cloud will fix it as this could be a blocking problem.

--
Gael

[Julien Dubois]

Or maybe we could patch this in our code ?
This is a great bug, it shows we go further than many people with Eureka.

--
You received this message because you are subscribed to the Google Groups "JHipster dev team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jhipster-dev...@googlegroups.com.
To post to this group, send email to jhipst...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jhipster-dev/bbc0d4bb-0313-48af-aa52-5b1ab78e46af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Gaël Marziou]

I tried what Dave Syer suggested

eureka:
    instance:
        prefer-ip-address: false
        hostname: 220.2.3.2

It works but only if prefer-ip-address is false and I don't really understand what it implies.

Also, I have some similar concern about the port, I'd like to be able to use server.port=0 to get random port.
I think that random ports and discovery at registration could be useful


[Julien Dubois]

Oh, I put prefer-ip to true as this causing issues with VirtualBox: all the "devbox" have the same name, so you need to use the IP (this is in bridge mode, with a new MAC address per box)

--

You received this message because you are subscribed to the Google Groups "JHipster dev team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jhipster-dev...@googlegroups.com.
To post to this group, send email to jhipst...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jhipster-dev/34be81a1-5692-4901-8e68-65831c42a1ee%40googlegroups.com.

[Gaël Marziou]

I knew it did not seem right.
Most of the issues here seems to be related to VMs or Docker networking.

I wonder whether the client's IP address could be determined by server from the origin of the connection at registration time.

[Deepu K Sasidharan]

I saw a linux bug somewhere few days back which was talking about kernel giving wrong ip to vm and docker, could it be related. I couldn't find that source since i saw it on twitter

--
You received this message because you are subscribed to the Google Groups "JHipster dev team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jhipster-dev...@googlegroups.com.
To post to this group, send email to jhipst...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jhipster-dev/1e2bb455-5856-4ee8-ba3a-d351bdce43d1%40googlegroups.com.

[Gaël Marziou]

I got it working by setting eureka.instance.ip-address while using prefer-ip-address to true in application.yml.

eureka:
    instance:
        prefer-ip-address: true
        ip-address: ${server.address}

So maybe, this should be our default setup.

[Gaël Marziou]

I found in the doc that some named network interfaces could be ignored

http://projects.spring.io/spring-cloud/spring-cloud.html#ignore-network-interfaces

Maybe we could provide a default list to prevent our users to fall into this common trap, always excluding docker0

spring:
  cloud:
    inetutils:
      ignoredInterfaces:
        - docker0
        - veth.*

[Julien Dubois]

Very interesting.

This is going to be complex to test, but this is where we add a lot of value, compared to what Spring Cloud provides by default.

--
You received this message because you are subscribed to the Google Groups "JHipster dev team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jhipster-dev...@googlegroups.com.
To post to this group, send email to jhipst...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jhipster-dev/a1611e96-ad83-49bd-94ee-f288016db01d%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Julien Dubois

Twitter: @juliendubois
Phone: +33 (0)6 25 02 34 18

[Gaël Marziou]

It seems something changed in registry or maybe on my machine, anyway I had to configure eureka client this way putting both hostname and ip-address:

eureka:
    instance:
        prefer-ip-address: true
        hostname: ${server.address}
        ip-address: ${server.address}

[Julien Dubois]

Thanks Gaël, I will definitely have to do more test with this. My current goal is to be able to have the Registry in a Docker container, so it's easier to deploy & test, as long as we don't have too many networking issues!

--
You received this message because you are subscribed to the Google Groups "JHipster dev team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jhipster-dev...@googlegroups.com.
To post to this group, send email to jhipst...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jhipster-dev/cd950dcd-2e58-4865-9786-a85354e33ed5%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.