Re: mesos/kafka issues (reviving old thread)

[Vinit Mahedia]

To close the loop on this one :

With Steve Niemitz's help, I resolved the issue, kafka-scheduler was going
to wrong master and the slave it was going to returned a
/master/status.json which did not have any information about the registered
slaves.

"slaves":[

   ],

What did I do?

   1. Restarted zookeeper - running the docket image on marathon.
   2. Edited kafka-mesos.properties with same content but changing seq.

It started working and I just tested it by producing one test message and
consuming it.

Thanks to all of you, who helped, for your time.

Vinit.


PS: for some reason, Steve was not CCed on one of the replies, so I worked
with him 1-1 below is the conversation thread, if anybody else runs into
the same problem.


On Mon, Jun 27, 2016 at 1:35 PM, Vinit Mahedia <vinitmahe...@gmail.com>
wrote:

> That exactly was the problem, it was going to the wrong master, I
> restarted zookeeper and edited the kafka-mesos.properies with the same
> content just changed the sequence of arguments, it discovered new master
> after this.
>
> Although I don't understand why it was discovering wrong master though on
> the start up, maybe stale state from ZK, but should not it get the correct
> master on startup?
>
> This is a huge help, truly appreciate.
>
>
>
> On Mon, Jun 27, 2016 at 12:44 PM, Steve Niemitz <sniem...@apache.org>
> wrote:
>
>> I think I know what your problem is, I've run into it before.  If you
>> don't have any slaves registered, mesos will just ignore any attempt to
>> register a framework.
>>
>> I looked at the results from /master/state.json in your packet capture
>> and you don't have any registered slaves.
>>
>> Try bringing up a slave and see if it works then.
>>
>> On Mon, Jun 27, 2016 at 3:25 PM, Vinit Mahedia <vinitmahe...@gmail.com>
>> wrote:
>>
>>> I replied to the thread and realized that for some reason, Joe Stein's
>>> reply did not have you the CC list, so forwarding you this.
>>>
>>>
>>> Hi Steve,
>>>
>>> Finally, I am getting the Jetty error for bad HTTP message - logs
>>> <https://gist.github.com/vmahedia/3a56e432d95c0b54912626293d449ec8>.
>>> Although I get this after a long time. Here is the packet capture.
>>>
>>> Kafka running on 10.10.17.41 and mesos-master is running on 10.10.17.68.
>>>
>>> Here is the screenshot, if you quickly want to look at the logs.
>>>
>>> Scheduler-logS
>>> ×
>>>
>>>
>>>
>>> Packet Capture with only POST showing
>>> Following the TCP stream of above capture.
>>>
>>>
>>>
>>>
>>> On Fri, Jun 24, 2016 at 6:21 AM, Joe Stein <joe.st...@stealth.ly> wrote:
>>>
>>>> +1 to setting --debug
>>>>
>>>> also make sure you set the --api via CLI or properties file correctly
>>>> suspectfully sounds like the issue that keeps going back and forth (or
>>>> since it isn't set right not going back and forth ... )  its also why
>>>> it works on master because your property file may have api as localhost  or
>>>> such...
>>>>
>>>> thinking out loud quick here but overall definitely a first thing to
>>>> check
>>>>
>>>> regards,
>>>>
>>>>
>>>> ~ Joe Stein
>>>>
>>>> On Fri, Jun 24, 2016 at 12:05 AM, Steve Niemitz <sniem...@apache.org>
>>>> wrote:
>>>>
>>>>> Have you tried running the Kafka scheduler in debug? (Pass --debug to
>>>>> iirc). That gives you a good amount of output in stdout/stderr.
>>>>>
>>>>> Also make sure your mesos lib that the scheduler is running matches
>>>>> your
>>>>> master version.
>>>>>
>>>>> Finally, make sure the master can communicate BACK to the scheduler on
>>>>> whatever port you set as the LIBPROCESS_PORT on the scheduler.
>>>>> (Firewall
>>>>> rules and such)
>>>>>
>>>>> If you want to post the stderr/stdout logs from the scheduler (with
>>>>> debug
>>>>> on) I can take a look.
>>>>> On Jun 23, 2016 4:41 PM, "Vinit Mahedia" <vinitmahe...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> > I am running into an issue where kafka framework can't register with
>>>>> > Mesos. In packet capture I see the POST request to subscribe on mesos
>>>>> > master box but mesos master does not res

Re: mesos/kafka issues (reviving old thread)

[Vinit Mahedia]

I am running into an issue where kafka framework can't register with Mesos.
In packet capture I see the POST request to subscribe on mesos master box
but mesos master does not respond, neither it logs that it received the
request which it usually does on any attempt by a framework.
Kafka-framework keeps re-sending the request and eventually gives up.

running locally, Mesos in VM1 and kafka-framework on VM2 works fine, also
some people here reported that putting kafka-framework on mesos master
works as well, but that is not actually working deployment.

I can provide more information. Thanks for offering help, I really
appreciate your time.

On Fri, Jun 17, 2016 at 1:36 PM, Steve Niemitz <sniem...@twitter.com> wrote:

> No issues here, we've been running two 8 broker clusters for ~a month
> without incident, and I plan on rolling it out to one of our larger (~40
> broker) clusters next week.
>
> My experience with it has been really positive so far, it just pretty much
> worked out of the box.   I'm curious what issues you ran into, happy to try
> to help if you want!
>
> On Fri, Jun 17, 2016 at 3:31 PM, Vinit Mahedia <vinitmahe...@gmail.com>
> wrote:
>
>> ​Hi Steve, ​
>>
>> How long has it been running without problems? I have read on mailing list
>> some people complaining that brokers sometimes disappear etc. Have you
>> come
>> across any such problems? Any other issues that you had to take care of?
>>
>> I tried to use the version you specified and also took the latest release
>> of kafka without luck although I am happy to have found someone for whom
>> it's working.
>>
>>
>> On Fri, Jun 10, 2016 at 3:57 PM, Steve Niemitz <sniem...@apache.org>
>> wrote:
>>
>> > Just to chime in, I've been running the 0.9.5.1 scheduler as a task on
>> > another slave without issues. (Aurora runs the kafka-mesos scheduler in
>> my
>> > case).
>> >
>> > On Thu, Jun 9, 2016 at 2:50 PM, Vinit Mahedia <vinitmahe...@gmail.com>
>> > wrote:
>> >
>> > > Justin,
>> > >
>> > > When you say "working" - does it mean kafka-scheduler still has to be
>> on
>> > > the same box as mesos-master? or you
>> > > have it working without that constraint?
>> > >
>> > > On Wed, Jun 8, 2016 at 6:07 PM, Justin Ryan <jur...@ziprealty.com>
>> > wrote:
>> > >
>> > > > inline
>> > > >
>> > > > On 6/8/16, 4:06 PM, "Justin Ryan" <jur...@ziprealty.com> wrote:
>> > > >
>> > > > >FYI, when I updated to the latest kafka-mesos (0.5.1.0) this
>> problem
>> > > went
>> > > > away.  FWIW, I’m actually using a branch which updates kafka to
>> > 0.10.0.0
>> > > as
>> > > > well:
>> > > > >
>> > > >
>> > > > Correction: 0.9.5.1 (current git master)
>> > > >
>> > > > > PR for kafka 0.10.0.0 (tests still fail, someone else did the
>> bulk of
>> > > > porting but didn’t PR it) : https://github.com/mesos/kafka/pull/220
>> > > > >   ( ./gradlew jar –x test gets a successful build )
>> > > > >
>> > > > > Issue for the problem discussed in this thread:
>> > > > https://github.com/mesos/kafka/issues/199
>> > > > >
>> > > > >Cheers!
>> > > > >
>> > > >
>> > > >
>> > > > 
>> > > >
>> > > > P Please consider the environment before printing this e-mail
>> > > >
>> > > > The information in this electronic mail message is the sender's
>> > > > confidential business and may be legally privileged. It is intended
>> > > solely
>> > > > for the addressee(s). Access to this internet electronic mail
>> message
>> > by
>> > > > anyone else is unauthorized. If you are not the intended recipient,
>> any
>> > > > disclosure, copying, distribution or any action taken or omitted to
>> be
>> > > > taken in reliance on it is prohibited and may be unlawful. The
>> sender
>> > > > believes that this E-mail and any attachments were free of any
>> virus,
>> > > worm,
>> > > > Trojan horse, and/or malicious code when sent. This message and its
>> > > > attachments could have been infected during transmission. By reading
>> > the
>> > > > message and opening any attachments, the recipient accepts full
>> > > > responsibility for taking protective and remedial action about
>> viruses
>> > > and
>> > > > other defects. The sender's employer is not liable for any loss or
>> > damage
>> > > > arising in any way.
>> > > >
>> > >
>> > >
>> > >
>> > > --
>> > > ~Vinit
>> > >
>> >
>>
>>
>>
>> --
>> ~Vinit
>>
>
>


-- 
~Vinit

Re: mesos/kafka issues (reviving old thread)

[Vinit Mahedia]

​Hi Steve, ​

How long has it been running without problems? I have read on mailing list
some people complaining that brokers sometimes disappear etc. Have you come
across any such problems? Any other issues that you had to take care of?

I tried to use the version you specified and also took the latest release
of kafka without luck although I am happy to have found someone for whom
it's working.


On Fri, Jun 10, 2016 at 3:57 PM, Steve Niemitz <sniem...@apache.org> wrote:

> Just to chime in, I've been running the 0.9.5.1 scheduler as a task on
> another slave without issues. (Aurora runs the kafka-mesos scheduler in my
> case).
>
> On Thu, Jun 9, 2016 at 2:50 PM, Vinit Mahedia <vinitmahe...@gmail.com>
> wrote:
>
> > Justin,
> >
> > When you say "working" - does it mean kafka-scheduler still has to be on
> > the same box as mesos-master? or you
> > have it working without that constraint?
> >
> > On Wed, Jun 8, 2016 at 6:07 PM, Justin Ryan <jur...@ziprealty.com>
> wrote:
> >
> > > inline
> > >
> > > On 6/8/16, 4:06 PM, "Justin Ryan" <jur...@ziprealty.com> wrote:
> > >
> > > >FYI, when I updated to the latest kafka-mesos (0.5.1.0) this problem
> > went
> > > away.  FWIW, I’m actually using a branch which updates kafka to
> 0.10.0.0
> > as
> > > well:
> > > >
> > >
> > > Correction: 0.9.5.1 (current git master)
> > >
> > > > PR for kafka 0.10.0.0 (tests still fail, someone else did the bulk of
> > > porting but didn’t PR it) : https://github.com/mesos/kafka/pull/220
> > > >   ( ./gradlew jar –x test gets a successful build )
> > > >
> > > > Issue for the problem discussed in this thread:
> > > https://github.com/mesos/kafka/issues/199
> > > >
> > > >Cheers!
> > > >
> > >
> > >
> > > 
> > >
> > > P Please consider the environment before printing this e-mail
> > >
> > > The information in this electronic mail message is the sender's
> > > confidential business and may be legally privileged. It is intended
> > solely
> > > for the addressee(s). Access to this internet electronic mail message
> by
> > > anyone else is unauthorized. If you are not the intended recipient, any
> > > disclosure, copying, distribution or any action taken or omitted to be
> > > taken in reliance on it is prohibited and may be unlawful. The sender
> > > believes that this E-mail and any attachments were free of any virus,
> > worm,
> > > Trojan horse, and/or malicious code when sent. This message and its
> > > attachments could have been infected during transmission. By reading
> the
> > > message and opening any attachments, the recipient accepts full
> > > responsibility for taking protective and remedial action about viruses
> > and
> > > other defects. The sender's employer is not liable for any loss or
> damage
> > > arising in any way.
> > >
> >
> >
> >
> > --
> > ~Vinit
> >
>



-- 
~Vinit

Re: Notification: Community Meeting @ Thu Jun 16, 2016 3pm - 4pm (Apache Mesos)

[Vinit Mahedia]

+1 Slack.

On Fri, Jun 17, 2016 at 12:59 AM, Jay JN Guo  wrote:

> +1 Slack!
>
> /J
>
> Vaibhav Khanduja  wrote on 06/16/2016 22:26:27:
>
> > From: Vaibhav Khanduja 
> > To: dev@mesos.apache.org
> > Date: 06/16/2016 22:26
> > Subject: Re: Notification: Community Meeting @ Thu Jun 16, 2016 3pm
> > - 4pm (Apache Mesos)
> >
> > + 1 slack
> >
> > Sent from my iPhone. Please excuse for typos and brevity of this message.
> >
> > > On Jun 16, 2016, at 6:46 PM, haosdent  wrote:
> > >
> > > +1 For Slack.
> > >
> > >> On Fri, Jun 17, 2016 at 7:33 AM, Greg Mann 
> wrote:
> > >>
> > >> Hello all,
> > >> Here are the notes from our community sync meeting this afternoon:
> > >>
> > >> Attendees:
> > >>
> > >> Mesosphere: Joris, Greg, Haris, Artem, Joseph, Kapil, Anand, Gilbert,
> > >> Harpreet, Kevin, Vinod, Jie, Joerg, MPark
> > >>
> > >> Uber: Zhitao Li
> > >>
> > >> Agenda/Note:
> > >>
> > >>   -
> > >>
> > >>   Reviewing the list of maintainers on
> > >>   http://mesos.apache.org/documentation/latest/committers/
> > >>   -
> > >>
> > >>  Add components for
> > >>  -
> > >>
> > >> Documentation (docs/*)
> > >> -
> > >>
> > >> Windows (*windows*)
> > >> -
> > >>
> > >> C++ standards (docs/c++-style-guide.md)
> > >> -
> > >>
> > >> HTTP API (http.*)
> > >> -
> > >>
> > >> Persistence
> > >> -
> > >>
> > >> Test infrastructure (src/tests/*)
> > >> -
> > >>
> > >> Build-related
> > >> -
> > >>
> > >>Autotools, CMake
> > >>-
> > >>
> > >> Subdivide Stout
> > >> -
> > >>
> > >> Subdivide Libprocess (3rdparty/libprocess/*)
> > >> -
> > >>
> > >> Subdivide Container-related things (src/slave/containerizer/*)
> > >> -
> > >>
> > >>Networking
> > >>-
> > >>
> > >>Storage
> > >>-
> > >>
> > >> Resource allocation/Scheduler
> > >> -
> > >>
> > >> Development tools
> > >> -
> > >>
> > >>  Think about some tooling to facilitate this
> > >>  -
> > >>
> > >> http://lxr.free-electrons.com/source/MAINTAINERS
> > >> -
> > >>
> > >>  AI: Ben Mahler will send out an email to the mailing list about
> > >>  maintainers
> > >>
> > >>
> > >>
> > >>   -
> > >>
> > >>   Reviewing and updating the roadmap.
> > >>
> > >> https://cwiki.apache.org/confluence/display/MESOS/Roadmap
> > >>
> > >> (NOTE: it’ll be moved to documentation roadmap.md)
> > >>
> > >>
> > >>   -
> > >>
> > >>   Review of working groups
> > >>
> > >> https://github.com/apache/mesos/blob/master/docs/working-groups.md
> > >>
> > >>
> > >>   -
> > >>
> > >>   AI [Jie]: Send emails to working group contacts (Simulation,
> Performance
> > >>   Isolation, Resource Allocation)
> > >>   -
> > >>
> > >>   AI [Jie] : Split Nested Container into Pods and Nested Containers
> > >>   -
> > >>
> > >>   AI [Jie] : Remove Strategy
> > >>   -
> > >>
> > >>   AI [Jie]: Send a proposal to dev@ regarding work groups
> > >>   -
> > >>
> > >>   AI [Kevin] : Add a WG for Community (reviews, maintainers, etc)
> > >>
> > >>
> > >>
> > >>   -
> > >>
> > >>   [Fan / Joris] Rack Awareness
> > >>   -
> > >>
> > >>  Need to find a shepherd!
> > >>  -
> > >>
> > >>  AI [Joris]: Ask on the dev@ list for the use case w.r.t
> frameworks
> > >>
> > >>
> > >>
> > >>   -
> > >>
> > >>   Closing stale reviews ( > 3 months)
> > >>   -
> > >>
> > >>  AI [Joris/Artem/Vinod/Joseph]: Policy for re-opening reviews
> > >>  -
> > >>
> > >>  AI [Joris/Artem] : Email dev@ as a heads up before closing the
> > >>  reviews (referencing above policy)
> > >>  -
> > >>
> > >>  AI [Artem] : Revive Community Kanban board to properly prioritize
> and
> > >>  track issues
> > >>
> > >>
> > >>
> > >>   -
> > >>
> > >>   Community metrics (e.g., affiliations)
> > >>   -
> > >>
> > >>  AI [Mpark] : Blog post around  Mesocon NA community talk
> > >>  -
> > >>
> > >>  AI [Artem] : Email dev@ and personally to solicit affiliations
> for
> > >>  contributor metrics
> > >>
> > >>
> > >>
> > >>   -
> > >>
> > >>   Communication Channel
> > >>   -
> > >>
> > >>  Slack, HipChat, IRC?
> > >>  -
> > >>
> > >>  AI [Vinod] : Email dev@ and user@ about using Slack as canonical
> > >>  communication channel
> > >>
> > >>
> > >>> On Wed, Jun 15, 2016 at 6:46 PM, Greg Mann 
> wrote:
> > >>>
> > >>> Also note: tomorrow's community sync will be hosted at Mesosphere HQ,
> 88
> > >>> Stevenson St., San Francisco, CA. Community members are welcome to
> attend
> > >>> in person!
> > >>>
> > >>> As usual, Google Hangout and Youtube links for the meeting will be
> posted
> > >>> in the Google doc just before the meeting begins.
> > >>>
> > >>> Cheers,
> > 

Re: Welcome Anand and Joseph as new committers!

[Vinit Mahedia]

Congratulations to both of you!

On Sat, Jun 11, 2016 at 4:36 AM, haosdent  wrote:

> Congratulations Anand and Joseph!
> I always learn a lot form Joseph's nice analyzations under Mesos flaky test
> tickets, thanks a lot!
>
> On Sat, Jun 11, 2016 at 8:15 AM, Brenden Matthews 
> wrote:
>
> > Welcome and congrats!
> >
> > On Fri, Jun 10, 2016 at 2:11 PM, Benjamin Mahler 
> > wrote:
> >
> >> Welcome Anand and Joseph, thanks for all of your contributions!
> >>
> >> Looking forward to seeing your ongoing positive influences on the
> >> community and the project, let's build great software!
> >>
> >> On Thu, Jun 9, 2016 at 2:00 PM, Vinod Kone 
> wrote:
> >>
> >>> Hi folks,
> >>>
> >>> I'm happy to announce that the PMC has voted in *Anand Mazumdar *and
> >>> *Joseph
> >>> Wu* as committers and members of PMC for the Apache Mesos project.
> >>>
> >>> A little about the new committers.
> >>>
> >>> Anand has been working on the Apache Mesos project for about an year
> now
> >>> and has shown incredible commitment to the project and the community.
> His
> >>> significant contributions include implementing scheduler HTTP API,
> >>> designing and implementing executor HTTP API and helping out with the
> >>> operator HTTP API. His formal committer checklist is here
> >>> <
> >>>
> https://docs.google.com/document/d/1DGRO-z-0JKS1dIxcrzXD8QznEv-auSqmIP3-aiwhtFI/edit?usp=sharing
> >>> >
> >>> .
> >>>
> >>> Joseph's passion and dedication to the community is phenomenal. His
> >>> significant contributions include Maintenance Primitives and Container
> >>> Logger Modules. He has also been a valuable contributor and reviewer to
> >>> our
> >>> testing infrastructure and the Windows work. His formal committer
> >>> checklist
> >>> is here
> >>> <
> >>>
> https://docs.google.com/document/d/1o7qLQJQ7TZCaf49gSNc6SSl29qAFagYH2STDfhHDDPw/edit?usp=sharing
> >>> >
> >>> .
> >>>
> >>> Please join me in congratulating them on their new roles and especially
> >>> responsibilities :)
> >>>
> >>> On behalf of the PMC,
> >>> Vinod
> >>>
> >>
> >>
> >
>
>
> --
> Best Regards,
> Haosdent Huang
>



-- 
~Vinit

Re: mesos/kafka issues (reviving old thread)

[Vinit Mahedia]

Justin,

When you say "working" - does it mean kafka-scheduler still has to be on
the same box as mesos-master? or you
have it working without that constraint?

On Wed, Jun 8, 2016 at 6:07 PM, Justin Ryan  wrote:

> inline
>
> On 6/8/16, 4:06 PM, "Justin Ryan"  wrote:
>
> >FYI, when I updated to the latest kafka-mesos (0.5.1.0) this problem went
> away.  FWIW, I’m actually using a branch which updates kafka to 0.10.0.0 as
> well:
> >
>
> Correction: 0.9.5.1 (current git master)
>
> > PR for kafka 0.10.0.0 (tests still fail, someone else did the bulk of
> porting but didn’t PR it) : https://github.com/mesos/kafka/pull/220
> >   ( ./gradlew jar –x test gets a successful build )
> >
> > Issue for the problem discussed in this thread:
> https://github.com/mesos/kafka/issues/199
> >
> >Cheers!
> >
>
>
> 
>
> P Please consider the environment before printing this e-mail
>
> The information in this electronic mail message is the sender's
> confidential business and may be legally privileged. It is intended solely
> for the addressee(s). Access to this internet electronic mail message by
> anyone else is unauthorized. If you are not the intended recipient, any
> disclosure, copying, distribution or any action taken or omitted to be
> taken in reliance on it is prohibited and may be unlawful. The sender
> believes that this E-mail and any attachments were free of any virus, worm,
> Trojan horse, and/or malicious code when sent. This message and its
> attachments could have been infected during transmission. By reading the
> message and opening any attachments, the recipient accepts full
> responsibility for taking protective and remedial action about viruses and
> other defects. The sender's employer is not liable for any loss or damage
> arising in any way.
>



-- 
~Vinit

Re: mesos/kafka issues (reviving old thread)

[Vinit Mahedia]

Vinod,

In my case, have two vagrant VMs, one where mesos-master runs and
frameworks on another.
This is my dev/debug setup where both marathon and kafka frameworks are
failing not just kafka.

But we do have a real (bare metal machines cluster) running marathon
successfully but kafka
framework fails there. I have tried both framework as a docker image and
running it directly on
machine.

I have the debugging environment setup, I see requests successfully
completed on master, it even
(thinks) it sends successfully, but framework never receives it. Nothing
can be seen on packet capture
as well which confuses me.


On Mon, Jun 6, 2016 at 2:23 PM, Vinod Kone  wrote:

> ZK communication is little different from framework communication. In the
> former case, the ZK client library inside master opens up a connection to
> the ZK server ensemble. In the latter case, the scheduler driver inside the
> framework scheduler opens up a connection to the mesos master. But it is
> strange that marathon from a different remote host works fine but
> kafka-mesos from a different remote host has issues.
>
> On Mon, Jun 6, 2016 at 3:12 PM, Justin Ryan  wrote:
>
> > inline
> >
> > On 6/6/16, 8:40 AM, "Vinod Kone"  wrote:
> >
> > >Have you tried running a different framework than the kafka one (maybe
> > marathon? or chronos?) to rule out framework related issues? I'm
> surprised
> > that it works when the scheduler and master are on the same host but not
> > when they are different.
> > > Looks like the request packets are getting dropped somewhere between
> the
> > master NIC and the application.
> > >
> >
> > Marathon is working just fine, I have flume running via Marathon and
> kafka
> > running via kafka-mesos.
> >
> > Yah, it does seem like the request packets are getting dropped, but that
> > makes no sense – how can the mesos-masters and zookeepers communicate
> with
> > each other, but an arbitrary other process can’t communicate with the
> > active mesos-master from another host which is a mesos-master? I’ve done
> a
> > lot of packet inspection and can do more, but overwhelmingly this seems
> to
> > anchor the notion that there is no firewall in play.
> >
> > 
> >
> > P Please consider the environment before printing this e-mail
> >
> > The information in this electronic mail message is the sender's
> > confidential business and may be legally privileged. It is intended
> solely
> > for the addressee(s). Access to this internet electronic mail message by
> > anyone else is unauthorized. If you are not the intended recipient, any
> > disclosure, copying, distribution or any action taken or omitted to be
> > taken in reliance on it is prohibited and may be unlawful. The sender
> > believes that this E-mail and any attachments were free of any virus,
> worm,
> > Trojan horse, and/or malicious code when sent. This message and its
> > attachments could have been infected during transmission. By reading the
> > message and opening any attachments, the recipient accepts full
> > responsibility for taking protective and remedial action about viruses
> and
> > other defects. The sender's employer is not liable for any loss or damage
> > arising in any way.
> >
>



-- 
~Vinit

Re: Documentation about debugging mesos-master : newbie

[Vinit Mahedia]

To close the loop on this - I got it working with a fresh vagrant vm.
Earlier
I was trying on a vm which I was using for other things.

Thank you *Gilbert* and others for your time and help :-)

Revived an old thread for kafka issue, refer to that if you are interested.

On Fri, Jun 3, 2016 at 2:21 PM, Vinit Mahedia <vinitmahe...@gmail.com>
wrote:

> Guangya -
>
> I just checked that. I am using v7.10 which has the fix for that issue. I
> also tried to
> build it on ubuntu(vagrant machine) 14.04, how Gilbert and others are
> doing it, but
> there I got this linking error so I think here I might have to work out
> some issues as
> there are already others who have it functioning unlike Mac OS:
>
>
> Error on ubuntu :"make"(during link phase)
>
> libtool: link: `slave/libmesos_no_3rdparty_la-validation.lo' is not a
> valid libtool object
>
>
> Brenno -
>
> That is the reason I tried to build the whole thing as static by passing
> --enable-static
> flag, altough that did not work either. With default setting, shared
> library, it gives that
> infamous error of "memory address not accessible". The only place where I
> could set
> break point was "main" which I believe was due to GTEST macro. Now, I am
> ditching the
> setup on mac os and trying to get it working on ubuntu like others here.
>
> About the issue I am facing with Kafka, I found this thread where someone
> else is running into
> same issue as me, registering the framework. So I will be replying to
> that.Here it is -
> mesos/kafka framework registration issue
> <https://mail-archives.apache.org/mod_mbox/mesos-user/201604.mbox/%3c89398c43-d45c-4653-8c0a-5ac987395...@ziprealty.com%3E>,
> for curious folks.
>
>
> Thank you for your time, guys.
>
>
>
>
>
>
>
>
> On Fri, Jun 3, 2016 at 6:45 AM, Shuai Lin <linshuai2...@gmail.com> wrote:
>
> +1 for setting CFLAGS and CXXFLAGS, I used to call configure like this:
>>
>> ```
>> CFLAGS=-ggdb3 CXXFLAGS=-ggdb3 ../configure ...
>> ```
>>
>> On Fri, Jun 3, 2016 at 6:13 PM, Evers Benno <ben...@yandex-team.ru>
>> wrote:
>>
>> > A random guess, but gdb tends to load shared libraries only after you do
>> > "run" for the first time, maybe that's what's missing?
>> >
>> > Apart from this, after installation mesos is just a normal c++ binary,
>> > so you could bypass libtool by installing in some custom prefix (not
>> > sure how to do this on mac) and then using gdb manually with `gdb --args
>> > /usr/local/bin/mesos-master --work_dir= ...`
>> >
>> > Also, I vaguely remember some build issues with flags not being passed
>> > correctly to all third-party dependencies, so you probably want
>> > "CFLAGS=-g3 CXXFLAGS=-g3" in your environment in addition to
>> > --enable-debug.
>> >
>> > Best regards,
>> > Benno
>> >
>> >
>> > On 03.06.2016 02:23, Guangya Liu wrote:
>> > > Hi Vinit,
>> > >
>> > > Please check if you are encountering this issue:
>> > > https://github.com/Homebrew/homebrew-dupes/issues/221
>> > >
>> > > Thanks,
>> > >
>> > > Guangya
>> > >
>> > > On Fri, Jun 3, 2016 at 2:24 AM, Vinit Mahedia <vinitmahe...@gmail.com
>> >
>> > > wrote:
>> > >
>> > >> Hi Gilbert,
>> > >>
>> > >> Thank you for replying.
>> > >>
>> > >> Yes, I did that.
>> > >>
>> > >>
>> > >>1.  ./configure --enable-debug --disable-java --disable-python
>> > >>2.  make
>> > >>3. ./bin/gdb-mesos-master.sh --ip=127.0.0.1 --work_dir=.
>> > >>
>> > >> Although even after setting source directory, I can not set
>> breakpoint I
>> > >> get warning like this
>> > >>
>> > >> (gdb) break master.cpp:2481
>> > >> Cannot access memory at address 0x714d40
>> > >>
>> > >>
>> > >> I also tried few things, passing "static" flag to libtool, passing
>> > >>  "--enable-static"
>> > >>
>> > >> Although I got linker error, where I saw libtool was not using
>> --static
>> > >> flag and I do
>> > >> not know if doing that will fix it. I forgot to mention that am
>> building
>> > >> this on Mac OS.
>> > >>
>> > >> Thank you.

Re: mesos/kafka issues (reviving old thread)

[Vinit Mahedia]

Justin,

There's certainly a bug somewhere, either in mesos kafka framework or mesos
itself. If I can get this
mesos master running under debugger, this would be over in maybe few hours
or few days.

Kafka is a stateful service so can't run on marathon directly, there has to
be some framework/wrapper
which manages brokers - Read here
<https://mesosphere.com/blog/2015/07/16/making-apache-kafka-elastic-with-apache-mesos/>
.

On Fri, Jun 3, 2016 at 4:36 PM, Justin Ryan <jur...@ziprealty.com> wrote:

> inline
>
> On 6/3/16, 2:19 PM, "Vinit Mahedia" <vinitmahe...@gmail.com> wrote:
>
> >Justin,
> >Yeah - as long as everything is on a single box (mesos-kafka scheduler,
> mesos-master, zk etc.)
> >things work just fine, which is what I meant by local setup.
> >
> >
> >I did a local cluster setup as well, 3 vagrant machines, where it does
> >not work. So it does not work at all
> >if you have multi node setup (vagrant machines or bare metal).
> >
>
> I do have two working clusters, but the mesos-kafka scheduler must run on
> the active mesos-master leader, which may also be an indication of another
> symptom that just *happens* to coincide with this.
>
> >
> >others,
> >
> >Is there any alternative for getting kafka up and running on mesos  other
> than this -
> >mesos/kafka <https://github.com/mesos/kafka> ?
> >
>
> I thought about this for a while, but digging into the code, this is just
> an extension of MesosFramework, which is core mesos functionality.
>
> We’re either missing something or have exposed a bug.
>
> Of course, a person could just run kafka brokers with marathon, but I
> think this is worth the trouble and is fundamentally how things should be
> done.
>
>
> 
>
> P Please consider the environment before printing this e-mail
>
> The information in this electronic mail message is the sender's
> confidential business and may be legally privileged. It is intended solely
> for the addressee(s). Access to this internet electronic mail message by
> anyone else is unauthorized. If you are not the intended recipient, any
> disclosure, copying, distribution or any action taken or omitted to be
> taken in reliance on it is prohibited and may be unlawful. The sender
> believes that this E-mail and any attachments were free of any virus, worm,
> Trojan horse, and/or malicious code when sent. This message and its
> attachments could have been infected during transmission. By reading the
> message and opening any attachments, the recipient accepts full
> responsibility for taking protective and remedial action about viruses and
> other defects. The sender's employer is not liable for any loss or damage
> arising in any way.
>



-- 
~Vinit

Re: mesos/kafka issues (reviving old thread)

[Vinit Mahedia]

Justin,
Yeah - as long as everything is on a single box (mesos-kafka scheduler,
mesos-master, zk etc.)
things work just fine, which is what I meant by local setup.

I did a local cluster setup as well, 3 vagrant machines, where it does *not*
work. So it does not work at all
if you have multi node setup (vagrant machines or bare metal).

others,

Is there any alternative for getting kafka up and running on mesos  other
than this - mesos/kafka <https://github.com/mesos/kafka> ?



On Fri, Jun 3, 2016 at 3:53 PM, Justin Ryan <jur...@ziprealty.com> wrote:

> Hiya Vinit,
>
> I’ve made some progress, I have a conditionally working setup, and another
> setup which was working now failing in new ways.
>
> It does sound like your captures are similar to mine, what I found is that
> if I run the scheduler on, say, zk01 (which is also a mesos-master), while
> it is the leader, things work fine.  If mesos-master fails over to zk02 or
> zk03, the scheduler running on zk01 stops working, though its’ config
> points at all three machines.  Obviously this makes it difficult to run the
> scheduler itself as a mesos task.
>
> Though I wish neither of us were having this problem, it’s good to not
> feel like I’m crazy, I kinda ran out of things to test until one day it
> occurred to me to check if it matters whether the scheduler runs on the
> active mesos-master.  I can think of a couple reasons this would be so, but
> haven’t had time to narrow it down.
>
> Cheers!
>
> Justin
>
> On 6/3/16, 12:52 PM, "Vinit Mahedia" <vinitmahe...@gmail.com> wrote:
>
> >
> >
> >​​Hey Justin,
> >
> >
> >I am running in the same issues as you mentioned in this old
> > thread <
> https://mail-archives.apache.org/mod_mbox/mesos-user/201604.mbox/%3c89398c43-d45c-4653-8c0a-5ac987395...@ziprealty.com%3E>,
> did you resolve it?
> >
> >
> >I see that kafka framework sends a POST request to register itself but
> mesos master logs does not even show that the request was received, packet
> capture does. My guess was that something is
> > wrong in HTTP request but doing this same thing on local setup works
> fine so that can't be the case. I can capture the requests on the master
> node so there's no network issues either, just like in your case. I also
> verified that two machines can communicate
> > on using netcat as well.
> >
> >
> >
> >Like you mentioned in your thread, once it registered with mesos but that
> was the only time that happened, the brokers did not start even then -
> "start" timed out.
> >
> >
> >^that behavior hints at possible bug in mesos, where it sits on this
> request for too long and some times under some conditions, it gets through,
> that's when it works.
> >
> >
> >PS I have network capture showing POST from framework to master, if
> anyone wants to take a look at it.
> >
> >
> >--
> >Vinit
> >
> >
>
> 
>
> P Please consider the environment before printing this e-mail
>
> The information in this electronic mail message is the sender's
> confidential business and may be legally privileged. It is intended solely
> for the addressee(s). Access to this internet electronic mail message by
> anyone else is unauthorized. If you are not the intended recipient, any
> disclosure, copying, distribution or any action taken or omitted to be
> taken in reliance on it is prohibited and may be unlawful. The sender
> believes that this E-mail and any attachments were free of any virus, worm,
> Trojan horse, and/or malicious code when sent. This message and its
> attachments could have been infected during transmission. By reading the
> message and opening any attachments, the recipient accepts full
> responsibility for taking protective and remedial action about viruses and
> other defects. The sender's employer is not liable for any loss or damage
> arising in any way.
>



-- 
~Vinit

mesos/kafka issues (reviving old thread)

[Vinit Mahedia]

​​Hey Justin,

I am running in the same issues as you mentioned in this old thread
,
did you resolve it?

I see that kafka framework sends a POST request to register itself but
mesos master logs does not even show that the request was received, packet
capture does. My guess was that something is wrong in HTTP request but
doing this same thing on local setup works fine so that can't be the case.
I can capture the requests on the master node so there's no network issues
either, just like in your case. I also verified that two machines can
communicate on using netcat as well.

Like you mentioned in your thread, once it registered with mesos but that
was the only time that happened, the brokers did not start even then -
"start" timed out.

^that behavior hints at possible bug in mesos, where it sits on this
request for too long and some times under some conditions, it gets through,
that's when it works.

PS I have network capture showing POST from framework to master, if anyone
wants to take a look at it.

-- 
Vinit

Re: Documentation about debugging mesos-master : newbie

[Vinit Mahedia]

Guangya -

I just checked that. I am using v7.10 which has the fix for that issue. I
also tried to
build it on ubuntu(vagrant machine) 14.04, how Gilbert and others are doing
it, but
there I got this linking error so I think here I might have to work out
some issues as
there are already others who have it functioning unlike Mac OS:


Error on ubuntu :"make"(during link phase)

libtool: link: `slave/libmesos_no_3rdparty_la-validation.lo' is not a valid
libtool object


Brenno -

That is the reason I tried to build the whole thing as static by passing
--enable-static
flag, altough that did not work either. With default setting, shared
library, it gives that
infamous error of "memory address not accessible". The only place where I
could set
break point was "main" which I believe was due to GTEST macro. Now, I am
ditching the
setup on mac os and trying to get it working on ubuntu like others here.

About the issue I am facing with Kafka, I found this thread where someone
else is running into
same issue as me, registering the framework. So I will be replying to
that.Here it is -
mesos/kafka framework registration issue
<https://mail-archives.apache.org/mod_mbox/mesos-user/201604.mbox/%3c89398c43-d45c-4653-8c0a-5ac987395...@ziprealty.com%3E>,
for curious folks.


Thank you for your time, guys.








On Fri, Jun 3, 2016 at 6:45 AM, Shuai Lin <linshuai2...@gmail.com> wrote:

+1 for setting CFLAGS and CXXFLAGS, I used to call configure like this:
>
> ```
> CFLAGS=-ggdb3 CXXFLAGS=-ggdb3 ../configure ...
> ```
>
> On Fri, Jun 3, 2016 at 6:13 PM, Evers Benno <ben...@yandex-team.ru> wrote:
>
> > A random guess, but gdb tends to load shared libraries only after you do
> > "run" for the first time, maybe that's what's missing?
> >
> > Apart from this, after installation mesos is just a normal c++ binary,
> > so you could bypass libtool by installing in some custom prefix (not
> > sure how to do this on mac) and then using gdb manually with `gdb --args
> > /usr/local/bin/mesos-master --work_dir= ...`
> >
> > Also, I vaguely remember some build issues with flags not being passed
> > correctly to all third-party dependencies, so you probably want
> > "CFLAGS=-g3 CXXFLAGS=-g3" in your environment in addition to
> > --enable-debug.
> >
> > Best regards,
> > Benno
> >
> >
> > On 03.06.2016 02:23, Guangya Liu wrote:
> > > Hi Vinit,
> > >
> > > Please check if you are encountering this issue:
> > > https://github.com/Homebrew/homebrew-dupes/issues/221
> > >
> > > Thanks,
> > >
> > > Guangya
> > >
> > > On Fri, Jun 3, 2016 at 2:24 AM, Vinit Mahedia <vinitmahe...@gmail.com>
> > > wrote:
> > >
> > >> Hi Gilbert,
> > >>
> > >> Thank you for replying.
> > >>
> > >> Yes, I did that.
> > >>
> > >>
> > >>1.  ./configure --enable-debug --disable-java --disable-python
> > >>2.  make
> > >>3. ./bin/gdb-mesos-master.sh --ip=127.0.0.1 --work_dir=.
> > >>
> > >> Although even after setting source directory, I can not set
> breakpoint I
> > >> get warning like this
> > >>
> > >> (gdb) break master.cpp:2481
> > >> Cannot access memory at address 0x714d40
> > >>
> > >>
> > >> I also tried few things, passing "static" flag to libtool, passing
> > >>  "--enable-static"
> > >>
> > >> Although I got linker error, where I saw libtool was not using
> --static
> > >> flag and I do
> > >> not know if doing that will fix it. I forgot to mention that am
> building
> > >> this on Mac OS.
> > >>
> > >> Thank you.
> > >>
> > >>
> > >>
> > >> On Thu, Jun 2, 2016 at 12:33 PM, Gilbert Song <gilb...@mesosphere.io>
> > >> wrote:
> > >>
> > >>> Hi Vinit,
> > >>>
> > >>> Did you configure with debug mode (e.g., ../confugure
> --enable-debug)?
> > >>>
> > >>> Assuming you have the gdb installed, you should be able to debug
> mesos
> > >>> master
> > >>> in gbd:
> > >>>
> > >>> ./bin/gdb-mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos
> > >>>
> > >>>
> > >>> Gilbert
> > >>>
> > >>> On Thu, Jun 2, 2016 at 9:30 AM, Vinit Mahedia <
> vinitmahe...@gmail.com>
> > >>> wrote:
> > >>>
> > >>>> I have been trying to debug mesos-master using gdb-mesos-master.sh
> > >>> although
> > >>>> it does not load symbols or sources. I tried to set those paths as
> > well
> > >>> but
> > >>>> since it thinks mesos-master, libtool script, is the main binary.
> > >>>>
> > >>>> I just want to set the dev environment and try to fix a very stupid
> > bug
> > >>> to
> > >>>> learn the work flow of test/debug/commit.
> > >>>>
> > >>>> If I can get it working, I can help to write if such documentation
> > does
> > >>> not
> > >>>> exist. I also tried to set it up on eclipse CDT but it can't handle
> > >>> libtool
> > >>>> scripts.
> > >>>>
> > >>>> Thank you.
> > >>>>
> > >>>
> > >>
> > >
> >
>

Re: Documentation about debugging mesos-master : newbie

[Vinit Mahedia]

I tried that I am getting a linking error; I guess it just does not like me
or it's not my day.
There's a psychic across the road, I think he may earn some money today.

libtool: link: `slave/libmesos_no_3rdparty_la-validation.lo' is not a valid
libtool object


Anyway, just to give you a bit more context. I was trying kafka framework
on mesos, which
was unable to register itself with mesos, so I tried tcpdump and saw the
request was getting to master
properly but master's log did not show "attempt" to register or anything. I
did try with curl HTTP API and that
works from command line but I think that API is different from what I see
in called by kafka framework.


POST /master/mesos.scheduler.Call HTTP/1.1\r\n
User-Agent: libprocess/
scheduler-8c5bd8cc-1d7b-4c2c-9de3-6daa8c173e9e@10.10.17.41:46484\r\n
Libprocess-From:
scheduler-8c5bd8cc-1d7b-4c2c-9de3-6daa8c173e9e@10.10.17.41:46484\r\n
Connection: Keep-Alive\r\nHost: \r\n
Transfer-Encoding: chunked\r\n
\r\n2d\r\n\20\1\32)\n'\n\4root\22\5kafka!\0\0\0\0\200\306CA(\0012\1*:\ndevmesos101\r\n0\r\n\r\n


I have been putting off setting up this environment to get involved in
mesos community, this issue
just gave me a little push that I needed. Anyway, don't worry if this kafka
related stuff does not make
much sense. Since I am already deep into the problem, I might have missed
all the details to provide
complete context.

On Thu, Jun 2, 2016 at 3:55 PM, Gilbert Song <gilb...@mesosphere.io> wrote:

> For dev, I would strongly recommend using linux os (e.g., ubuntu14.04,
> 15.10, centos7.1, etc.). Because features are very limited in os x, most
> of features like using containers, cgroup isolation etc. you will need a
> linux environment.
>
> PS: using a vagrant box may be convenient to setup env on your os x.
>
> Gilbert
>
> On Thu, Jun 2, 2016 at 12:24 PM, Vinit Mahedia <vinitmahe...@gmail.com>
> wrote:
>
> > I tried that, it did not help either, same error. What do you use for dev
> > OS, IDE etc.
> > Do you think switching on ubuntu should help? I will try that anyway. I
> am
> > out of
> > ideas at this point if switching OS does not work either.
> >
> > gdb) b master.cpp:2481
> > Cannot access memory at address 0x714d40
> >
> >
> > On Thu, Jun 2, 2016 at 1:56 PM, Gilbert Song <gilb...@mesosphere.io>
> > wrote:
> >
> > > Vinit,
> > >
> > > Seems like your question is similar to this one:
> > >
> > >
> >
> https://mail-archives.apache.org/mod_mbox/mesos-dev/201507.mbox/%3CCAOs_uxyyeJNF+CtceOd7zZabSMJTneC=yyqcpwbz-gjyesp...@mail.gmail.com%3E
> > >
> > > Could you verify if James' reply would help for your case?
> > >
> > >
> >
> https://mail-archives.apache.org/mod_mbox/mesos-dev/201507.mbox/%3c7155f7cf-db57-4202-bc97-62e6dcfe1...@gmail.com%3E
> > >
> > > Gilbert
> > >
> > > On Thu, Jun 2, 2016 at 11:24 AM, Vinit Mahedia <vinitmahe...@gmail.com
> >
> > > wrote:
> > >
> > > > Hi Gilbert,
> > > >
> > > > Thank you for replying.
> > > >
> > > > Yes, I did that.
> > > >
> > > >
> > > >1.  ./configure --enable-debug --disable-java --disable-python
> > > >2.  make
> > > >3. ./bin/gdb-mesos-master.sh --ip=127.0.0.1 --work_dir=.
> > > >
> > > > Although even after setting source directory, I can not set
> breakpoint
> > I
> > > > get warning like this
> > > >
> > > > (gdb) break master.cpp:2481
> > > > Cannot access memory at address 0x714d40
> > > >
> > > >
> > > > I also tried few things, passing "static" flag to libtool, passing
> > > >  "--enable-static"
> > > >
> > > > Although I got linker error, where I saw libtool was not using
> --static
> > > > flag and I do
> > > > not know if doing that will fix it. I forgot to mention that am
> > building
> > > > this on Mac OS.
> > > >
> > > > Thank you.
> > > >
> > > >
> > > >
> > > > On Thu, Jun 2, 2016 at 12:33 PM, Gilbert Song <gilb...@mesosphere.io
> >
> > > > wrote:
> > > >
> > > > > Hi Vinit,
> > > > >
> > > > > Did you configure with debug mode (e.g., ../confugure
> > --enable-debug)?
> > > > >
> > > > > Assuming you have the gdb installed, you should be able to debug
> > mesos
> > > > > master
> > > > > in gbd:
> > > > >
> > 

Re: Documentation about debugging mesos-master : newbie

[Vinit Mahedia]

I tried that, it did not help either, same error. What do you use for dev
OS, IDE etc.
Do you think switching on ubuntu should help? I will try that anyway. I am
out of
ideas at this point if switching OS does not work either.

gdb) b master.cpp:2481
Cannot access memory at address 0x714d40


On Thu, Jun 2, 2016 at 1:56 PM, Gilbert Song <gilb...@mesosphere.io> wrote:

> Vinit,
>
> Seems like your question is similar to this one:
>
> https://mail-archives.apache.org/mod_mbox/mesos-dev/201507.mbox/%3CCAOs_uxyyeJNF+CtceOd7zZabSMJTneC=yyqcpwbz-gjyesp...@mail.gmail.com%3E
>
> Could you verify if James' reply would help for your case?
>
> https://mail-archives.apache.org/mod_mbox/mesos-dev/201507.mbox/%3c7155f7cf-db57-4202-bc97-62e6dcfe1...@gmail.com%3E
>
> Gilbert
>
> On Thu, Jun 2, 2016 at 11:24 AM, Vinit Mahedia <vinitmahe...@gmail.com>
> wrote:
>
> > Hi Gilbert,
> >
> > Thank you for replying.
> >
> > Yes, I did that.
> >
> >
> >1.  ./configure --enable-debug --disable-java --disable-python
> >2.  make
> >3. ./bin/gdb-mesos-master.sh --ip=127.0.0.1 --work_dir=.
> >
> > Although even after setting source directory, I can not set breakpoint I
> > get warning like this
> >
> > (gdb) break master.cpp:2481
> > Cannot access memory at address 0x714d40
> >
> >
> > I also tried few things, passing "static" flag to libtool, passing
> >  "--enable-static"
> >
> > Although I got linker error, where I saw libtool was not using --static
> > flag and I do
> > not know if doing that will fix it. I forgot to mention that am building
> > this on Mac OS.
> >
> > Thank you.
> >
> >
> >
> > On Thu, Jun 2, 2016 at 12:33 PM, Gilbert Song <gilb...@mesosphere.io>
> > wrote:
> >
> > > Hi Vinit,
> > >
> > > Did you configure with debug mode (e.g., ../confugure --enable-debug)?
> > >
> > > Assuming you have the gdb installed, you should be able to debug mesos
> > > master
> > > in gbd:
> > >
> > > ./bin/gdb-mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos
> > >
> > >
> > > Gilbert
> > >
> > > On Thu, Jun 2, 2016 at 9:30 AM, Vinit Mahedia <vinitmahe...@gmail.com>
> > > wrote:
> > >
> > > > I have been trying to debug mesos-master using gdb-mesos-master.sh
> > > although
> > > > it does not load symbols or sources. I tried to set those paths as
> well
> > > but
> > > > since it thinks mesos-master, libtool script, is the main binary.
> > > >
> > > > I just want to set the dev environment and try to fix a very stupid
> bug
> > > to
> > > > learn the work flow of test/debug/commit.
> > > >
> > > > If I can get it working, I can help to write if such documentation
> does
> > > not
> > > > exist. I also tried to set it up on eclipse CDT but it can't handle
> > > libtool
> > > > scripts.
> > > >
> > > > Thank you.
> > > >
> > >
> >
>

Re: Documentation about debugging mesos-master : newbie

[Vinit Mahedia]

Hi Gilbert,

Thank you for replying.

Yes, I did that.


   1.  ./configure --enable-debug --disable-java --disable-python
   2.  make
   3. ./bin/gdb-mesos-master.sh --ip=127.0.0.1 --work_dir=.

Although even after setting source directory, I can not set breakpoint I
get warning like this

(gdb) break master.cpp:2481
Cannot access memory at address 0x714d40


I also tried few things, passing "static" flag to libtool, passing
 "--enable-static"

Although I got linker error, where I saw libtool was not using --static
flag and I do
not know if doing that will fix it. I forgot to mention that am building
this on Mac OS.

Thank you.



On Thu, Jun 2, 2016 at 12:33 PM, Gilbert Song <gilb...@mesosphere.io> wrote:

> Hi Vinit,
>
> Did you configure with debug mode (e.g., ../confugure --enable-debug)?
>
> Assuming you have the gdb installed, you should be able to debug mesos
> master
> in gbd:
>
> ./bin/gdb-mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos
>
>
> Gilbert
>
> On Thu, Jun 2, 2016 at 9:30 AM, Vinit Mahedia <vinitmahe...@gmail.com>
> wrote:
>
> > I have been trying to debug mesos-master using gdb-mesos-master.sh
> although
> > it does not load symbols or sources. I tried to set those paths as well
> but
> > since it thinks mesos-master, libtool script, is the main binary.
> >
> > I just want to set the dev environment and try to fix a very stupid bug
> to
> > learn the work flow of test/debug/commit.
> >
> > If I can get it working, I can help to write if such documentation does
> not
> > exist. I also tried to set it up on eclipse CDT but it can't handle
> libtool
> > scripts.
> >
> > Thank you.
> >
>

Documentation about debugging mesos-master : newbie

[Vinit Mahedia]

I have been trying to debug mesos-master using gdb-mesos-master.sh although
it does not load symbols or sources. I tried to set those paths as well but
since it thinks mesos-master, libtool script, is the main binary.

I just want to set the dev environment and try to fix a very stupid bug to
learn the work flow of test/debug/commit.

If I can get it working, I can help to write if such documentation does not
exist. I also tried to set it up on eclipse CDT but it can't handle libtool
scripts.

Thank you.