mesos-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinod Kone <>
Subject Re: Mesos / Libprocess ENETUNREACH
Date Wed, 21 May 2014 17:40:28 GMT
-mesos-user@incubator (this mailing list is deprecated)


Both the framework (and slaves) and master need to be able to talk to each
other. IOW, if one of the end points uses a private IP (presumably thats
the case with framework behind a VPN) then it wouldn't work. If you want
the master/slave to use a public ip you can use --ip flag. For the
framework, you can set LIBPROCESS_IP in the environment.


On Wed, May 21, 2014 at 3:12 AM, Tom Arnfeld <> wrote:

> Hey,
> I’ve been testing out mesos for production recently and i’m having trouble
> registering frameworks over our VPN connection. I expect it’s a firewall
> issue, but i’m unsure as to what connectivity mesos requires for its
> frameworks.
> When running the test java framework from one of the slaves everything
> runs fine, however from my local machine across our VPN it just continues
> to re-register. With a little more debugging (GLOG_v=2) I narrowed it down
> to a specific socket error 101 - ENETUNREACH. That’s an error being thrown
> on *3rdparty/libprocess/src/process.cpp *line *1208*.
> Would anyone be able to describe the required connectivity between the
> mesos master(s) and the frameworks themselves? I’m a not very familiar with
> libprocess.
> Thanks!
> Tom.

View raw message