Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doesn't works with mesos 0.24 #11

Open
altvnk opened this issue Oct 4, 2015 · 7 comments
Open

Doesn't works with mesos 0.24 #11

altvnk opened this issue Oct 4, 2015 · 7 comments

Comments

@altvnk
Copy link

altvnk commented Oct 4, 2015

Mesos 0.24 was released recently. Was not able to make it work with updated version. Marathon-consul don't have any information in log, even in debug mode, so i don't have any diagnostic information. After downgrading mesos it works as usual.
Btw, marathon 0.11 was also released, so it would be reasonable to check compatibility too.

@altvnk
Copy link
Author

altvnk commented Oct 4, 2015

UPDATE: marathon 0.11 seems working fine, tested just now

@Mongey
Copy link

Mongey commented Oct 9, 2015

👍 marathon-consul doesn't seem to work using marathon 0.11 and 0.24.1

@abhishekamralkar
Copy link

do we have any deadline for this , we recently migrated to DCOS 1.3 and it uses Mesos 0.24.1 ,but marathon-consul not working with it. DO we have ay work around for it?

@BrianHicks
Copy link
Contributor

@altvnk what version are you using? (0.1 and 0.2 are both released on the Docker index.) Can you make sure you're using the right debug flag? For 0.2 it should be --log-level=debug. Do you see any information about not being able to send events in the Marathon log?

@davidsayers
Copy link

I am encountering this issue with Marathon 0.13.0 and Mesos 0.25.0.

It looks like Consul DNS is returning the wrong IP:

# host marathon-consul.service.consul
marathon-consul.service.consul has address 172.17.0.1

After a redeploy of marathon-consul the information in the Consul KV is correctly updated. The wrong IP is causing problems when update events are sent to "http://marathon-consul.service.consul:31901/events"

I see that mesos-consul has a flag to set IP lookup order. I have tried various combinations of "--mesos-ip-order=host,mesos,netinfo,docker" but the issue is still present.

@ChrisAubuchon
Copy link
Contributor

mesos-consul doesn't change the service if it already exists in Consul. The service will need to be deregistered and mesos-consul run with host first in the --mesos-ip-order list.

@davidsayers
Copy link

Its looking much healthier now. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants