As long as they are on different ports it should be fine. Use "--port" to
specify the slave port. You should also give each slave its own work
directory ("--work_dir") so that they don't trample on each other.On Mon, Jun 9, 2014 at 2:36 PM, Prakhar Panwaria < [email protected]> wrote: > Hi Vinod, > > Thanks for your reply. Yes, specifying the ip for the slave fixes that > error. And, the slave is also showing up in the Mesos GUI now. > > Also, is there a way I could set up multiple slaves on a single machine > for a particular Mesos master. Looks like IP address is being used as an > identifier for the slave. > > Thanks! > prakhar > > > On Mon, Jun 9, 2014 at 1:56 PM, Vinod Kone <[email protected]> wrote: > >> Looks like "gethostbyname2" call is returning an error. I've seen this >> before on my mac when i have vpn software running (or incorrectly stopped). >> im surprised though that master on the same box is fine but only slave has >> this issue? what happens if you specify --ip on the slave too? >> >> >> On Mon, Jun 9, 2014 at 10:38 AM, Prakhar Panwaria < >> [email protected]> wrote: >> >>> Hi Vinod, Benjamin, and other mates, >>> >>> I recently started playing around with Mesos. I think I installed it >>> successfully (make install went fine), but when I'm starting a Mesos slave >>> (and even during 'make check'), I'm facing the following warning and error: >>> >>> >>> >>> *WARNING: Logging before InitGoogleLogging() is written to STDERR* >>> *F0609 10:27:18.194910 1953354512 process.cpp:1488] Failed to >>> initialize, gethostbyname2: Unknown host* >>> **** Check failure stack trace: **** >>> *Abort trap: 6* >>> <<< >>> >>> I'm starting Mesos master using following cmd: >>> *mesos-master --ip=127.0.0.1 --zk=zk://localhost:2181/mesos >>> --work_dir=/Users/prakhar/mesos/data --log_dir=/Users/prakhar/mesos/logs* >>> >>> and, setting up a slave using the following cmd: >>> *mesos-slave --master=zk://localhost:2181/mesos >>> --log_dir=/Users/prakhar/mesos/logs/* >>> >>> My build environment is *Mac OSX 10.9.3*. I've zookeeper installed and >>> zookeeper server running in the background. >>> >>> Do you have any clue what could have caused this error or what I could >>> be doing wrong? >>> >>> Thanks, >>> prakhar >>> >> >> >
