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 <[email protected]> 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ğ <[email protected]> > 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 | [email protected] | http://www.cguru.net > -- Brandon
