mesos-slave service does not work

[Ahmet Emre Aladağ <em...@fikrimuhal.com>]

Hi,

I performed the mesosphere 0.25 installation with 3 nodes
(master/zookeeper/slaves).

"sudo start mesos-master" works but when I type: "sudo start mesos-slave",

"/usr/bin/mesos-init-wrapper slave" is called but it does not spawn a slave
process. It just finishes. I had to change the /etc/init/mesos-slave.conf to

exec mesos-slave --containerizers=docker,mesos --master="zk://.../mesos"
 --hostname="...." --ip="...." --log_dir="/var/log/mesos"

to make it work. This way it works but it can't read the conf files under
/etc/mesos-slave. I think the wrapper's main function is to read those
confs.

What could be the reason for this? How can I debug it? Bash code seems
complicated.

Re: mesos-slave service does not work

[Brandon Gulla <gu...@gmail.com>]

if that doesn't seem to work, an old favorite of mine is:

start mesos-slave && ps -ef | grep mesos-slave

assuming the ps can fire off before the mesos-slave exits, everyone loves a
good race condition.



On Thu, Oct 22, 2015 at 9:44 PM, Klaus Ma <kl...@gmail.com> wrote:

> For the bash, I think you can use "bash -x" to see what command are
> executing, and check the environment variables of the shell.
>
> On Thu, Oct 22, 2015 at 12:07 PM, Ahmet Emre Aladağ <em...@fikrimuhal.com>
> wrote:
>
>> Hi,
>>
>> I performed the mesosphere 0.25 installation with 3 nodes
>> (master/zookeeper/slaves).
>>
>> "sudo start mesos-master" works but when I type: "sudo start mesos-slave",
>>
>> "/usr/bin/mesos-init-wrapper slave" is called but it does not spawn a
>> slave process. It just finishes. I had to change the
>> /etc/init/mesos-slave.conf to
>>
>> exec mesos-slave --containerizers=docker,mesos --master="zk://.../mesos"
>>  --hostname="...." --ip="...." --log_dir="/var/log/mesos"
>>
>> to make it work. This way it works but it can't read the conf files under
>> /etc/mesos-slave. I think the wrapper's main function is to read those
>> confs.
>>
>> What could be the reason for this? How can I debug it? Bash code seems
>> complicated.
>>
>>
>>
>
>
> --
> Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer
> Platform Symphony/DCOS Development & Support, STG, IBM GCG
> +86-10-8245 4084 | madaxa@cn.ibm.com | http://www.cguru.net
>



-- 
Brandon

Re: mesos-slave service does not work

[Klaus Ma <kl...@gmail.com>]

For the bash, I think you can use "bash -x" to see what command are
executing, and check the environment variables of the shell.

On Thu, Oct 22, 2015 at 12:07 PM, Ahmet Emre Aladağ <em...@fikrimuhal.com>
wrote:

> Hi,
>
> I performed the mesosphere 0.25 installation with 3 nodes
> (master/zookeeper/slaves).
>
> "sudo start mesos-master" works but when I type: "sudo start mesos-slave",
>
> "/usr/bin/mesos-init-wrapper slave" is called but it does not spawn a
> slave process. It just finishes. I had to change the
> /etc/init/mesos-slave.conf to
>
> exec mesos-slave --containerizers=docker,mesos --master="zk://.../mesos"
>  --hostname="...." --ip="...." --log_dir="/var/log/mesos"
>
> to make it work. This way it works but it can't read the conf files under
> /etc/mesos-slave. I think the wrapper's main function is to read those
> confs.
>
> What could be the reason for this? How can I debug it? Bash code seems
> complicated.
>
>
>


-- 
Da (Klaus), Ma (马达) | PMP® | Advisory Software Engineer
Platform Symphony/DCOS Development & Support, STG, IBM GCG
+86-10-8245 4084 | madaxa@cn.ibm.com | http://www.cguru.net

Re: mesos-slave service does not work

[Artem Harutyunyan <ar...@mesosphere.io>]

Hi,

What's the content of your /etc/mesos-slave directory? What are the
values in files that you have there? Also, even if the agent doesn't
start it should produce some logs, did you take a look at those?

Artem.

On Thu, Oct 22, 2015 at 9:07 AM, Ahmet Emre Aladağ <em...@fikrimuhal.com> wrote:
> Hi,
>
> I performed the mesosphere 0.25 installation with 3 nodes
> (master/zookeeper/slaves).
>
> "sudo start mesos-master" works but when I type: "sudo start mesos-slave",
>
> "/usr/bin/mesos-init-wrapper slave" is called but it does not spawn a slave
> process. It just finishes. I had to change the /etc/init/mesos-slave.conf to
>
> exec mesos-slave --containerizers=docker,mesos --master="zk://.../mesos"
> --hostname="...." --ip="...." --log_dir="/var/log/mesos"
>
> to make it work. This way it works but it can't read the conf files under
> /etc/mesos-slave. I think the wrapper's main function is to read those
> confs.
>
> What could be the reason for this? How can I debug it? Bash code seems
> complicated.
>
>