Hi,

Yes, I have tried on both environments (one CentOS 7 and one Ubuntu) and
they behave the exact same way. I probably should clarify though that after
a restart the agent fails to start on the slave, which is why it never
reaches the master.

I can however run a smoke test and get it to connect from a slave to the
master by passing a job, but the slave agent won't start. The guide I
followed is at:
http://open.mesosphere.com/getting-started/datacenter/install/

The environment is by no means live, I can share details with you if you
can help me to that degree.

On Thu, Aug 6, 2015 at 2:23 PM, haosdent <[email protected]> wrote:

> Hi, @Stephen From your slave log, could not see the restart log about
> slave. Are you sure you restart slave after reboot?
>
> On Thu, Aug 6, 2015 at 5:54 PM, Stephen Knight <[email protected]> wrote:
>
>> Hi Klaus, I have attached all from a master and a slave.
>>
>> I've replicated the problem over and over again, not sure what to make of
>> it. First registration is fine but then if I reboot the service for
>> mesos-slave (process restart of full server restart) it never connects
>> again.
>>
>> The VM's are in the same VPC on AWS with an open security group between
>> them.
>>
>> On Thu, Aug 6, 2015 at 12:41 PM, Klaus Ma <[email protected]> wrote:
>>
>>> Hi Stephen,
>>>
>>> Would you share the log of master & slave?
>>>
>>> Thanks
>>> Klaus
>>>
>>>
>>> On 2015年08月06日 16:07, Stephen Knight wrote:
>>>
>>> Hi,
>>>
>>> I was wondering if anyone can help me. I have a test setup, 1
>>> master/zookeeper and 2 slaves on Ubuntu 14.04.
>>>
>>> When I initialize the slaves the first time it all works and they
>>> register with the master (I can see it on x.x.x.x:5050) but when I reboot
>>> those slaves for any reason, they never re-register. Am I missing something?
>>>
>>> Thx
>>>
>>>
>>> --
>>> ---
>>> Stephen Knight
>>> Infrastructure Consultant
>>>
>>> Pivotal Services @ EMC
>>> +971 (0)56 538 2071
>>>
>>> [email protected]
>>> [email protected]
>>>
>>> Pivotal.io
>>>
>>> Notice of Confidentiality - This email message is for the sole use of
>>> the intended recipient and may contain confidential and privileged
>>> information. Any unauthorized review, use, disclosure or distribution is
>>> prohibited. If you are not the intended recipient, please contact the
>>> sender by reply email and destroy all copies of the original message.
>>>
>>>
>>>
>>
>
>
> --
> Best Regards,
> Haosdent Huang
>

Reply via email to