Stephen: Klaus is correct, you are starting the Master in "standalone" mode, not with zookeeper support: it needs adding the --zk=zk://10.xx.xx.124:2181/mesos --quorum=1 options (at the very least).
As you correctly noted, the contents of the /mesos znode is empty and thus the agent nodes cannot find elected Master leader (also, if you are running more than one Master, they won't 'know' about each other and won't be able to elect a leader). To check that your settings work, you can (a) look in Master logs (it will log a lot of info when connecting to ZK) and (b) see that under /mesos a number of json.info_0000nn nodes will appear (whose contents are JSON so you can double check that the contents make sense). You can find more info here[0]. [0] http://codetrips.com/2015/08/16/apache-mesos-leader-master-discovery-using-zookeeper-part-2/ *Marco Massenzio* *Distributed Systems Engineerhttp://codetrips.com <http://codetrips.com>* On Fri, Sep 4, 2015 at 5:33 PM, Stephen Boesch <java...@gmail.com> wrote: > > I installed using yum -y install mesos. That did work. > > Now the master and slaves do not see each other. > > > Here is the master: > $ ps -ef | grep mesos | grep -v grep > stack 30236 17902 0 00:09 pts/4 00:00:04 > /mnt/mesos/build/src/.libs/lt-mesos-master --work_dir=/tmp/mesos > --ip=10.xx.xx.124 > > > Here is one of the 20 slaves: > > ps -ef | grep mesos | grep -v grep > root 26086 1 0 00:10 ? 00:00:00 /usr/sbin/mesos-slave > --master=zk://10.xx.xx.124:2181/mesos --log_dir=/var/log/mesos > root 26092 26086 0 00:10 ? 00:00:00 logger -p user.info -t > mesos-slave[26086] > root 26093 26086 0 00:10 ? 00:00:00 logger -p user.err -t > mesos-slave[26086] > > > Note the slave and master are on correct same ip address > > The /etc/mesos/zk seems to be set properly : and I do see the /mesos node > in zookeeper is updated after restarting the master > > However the zookeeper node is empty: > > [zk: localhost:2181(CONNECTED) 10] ls /mesos > [] > > The node is world accessible so no permission issue: > > [zk: localhost:2181(CONNECTED) 12] getAcl /mesos > 'world,'anyone > : cdrwa > > Why is the zookeeper node empty? Is this the reason the master and > slaves are not connecting? > > 2015-09-04 14:56 GMT-07:00 craig w <codecr...@gmail.com>: > >> No problem, they have a "downloads" link inn their menu: >> https://mesosphere.com/downloads/ >> On Sep 4, 2015 5:43 PM, "Stephen Boesch" <java...@gmail.com> wrote: >> >>> @Craig . That is an incomplete answer - given that such links are not >>> presented in an obvious manner . Maybe you managed to find a link on >>> their site that provides prebuilt for Centos7: if so then please share it. >>> >>> >>> I had previously found a link on their site for prebuilt binaries but is >>> based on using CDH4 (which is not possible for my company). It is also old. >>> >>> https://docs.mesosphere.com/tutorials/install_centos_rhel/ >>> >>> >>> 2015-09-04 14:27 GMT-07:00 craig w <codecr...@gmail.com>: >>> >>>> Mesosphere has packages prebuilt, go to their site to find how to >>>> install >>>> On Sep 4, 2015 5:11 PM, "Stephen Boesch" <java...@gmail.com> wrote: >>>> >>>>> >>>>> After following the directions here: >>>>> http://mesos.apache.org/gettingstarted/ >>>>> >>>>> Which for centos7 includes the following: >>>>> >>>>> >>>>> >>>>> >>>>> # Change working directory. >>>>> $ cd mesos >>>>> >>>>> # Bootstrap (Only required if building from git repository). >>>>> $ ./bootstrap >>>>> >>>>> # Configure and build. >>>>> $ mkdir build >>>>> $ cd build >>>>> $ ../configure >>>>> $ make >>>>> >>>>> In order to speed up the build and reduce verbosity of the logs, you >>>>> can append-j <number of cores> V=0 to make. >>>>> >>>>> # Run test suite. >>>>> $ make check >>>>> >>>>> # Install (Optional). >>>>> $ make install >>>>> >>>>> >>>>> >>>>> But the installation is not correct afterwards: here is the bin >>>>> directory: >>>>> >>>>> $ ll bin >>>>> total 92 >>>>> -rw-r--r--. 1 stack stack 1769 Jul 17 23:14 >>>>> valgrind-mesos-tests.sh.in >>>>> -rw-r--r--. 1 stack stack 1769 Jul 17 23:14 >>>>> valgrind-mesos-slave.sh.in >>>>> -rw-r--r--. 1 stack stack 1772 Jul 17 23:14 >>>>> valgrind-mesos-master.sh.in >>>>> -rw-r--r--. 1 stack stack 1769 Jul 17 23:14 >>>>> valgrind-mesos-local.sh.in >>>>> -rw-r--r--. 1 stack stack 1026 Jul 17 23:14 mesos-tests.sh.in >>>>> -rw-r--r--. 1 stack stack 901 Jul 17 23:14 mesos-tests-flags.sh.in >>>>> -rw-r--r--. 1 stack stack 1019 Jul 17 23:14 mesos-slave.sh.in >>>>> -rw-r--r--. 1 stack stack 1721 Jul 17 23:14 mesos-slave-flags.sh.in >>>>> -rw-r--r--. 1 stack stack 1366 Jul 17 23:14 mesos.sh.in >>>>> -rw-r--r--. 1 stack stack 1026 Jul 17 23:14 mesos-master.sh.in >>>>> -rw-r--r--. 1 stack stack 858 Jul 17 23:14 mesos-master-flags.sh.in >>>>> -rw-r--r--. 1 stack stack 1023 Jul 17 23:14 mesos-local.sh.in >>>>> -rw-r--r--. 1 stack stack 935 Jul 17 23:14 mesos-local-flags.sh.in >>>>> -rw-r--r--. 1 stack stack 1466 Jul 17 23:14 lldb-mesos-tests.sh.in >>>>> -rw-r--r--. 1 stack stack 1489 Jul 17 23:14 lldb-mesos-slave.sh.in >>>>> -rw-r--r--. 1 stack stack 1492 Jul 17 23:14 lldb-mesos-master.sh.in >>>>> -rw-r--r--. 1 stack stack 1489 Jul 17 23:14 lldb-mesos-local.sh.in >>>>> -rw-r--r--. 1 stack stack 1498 Jul 17 23:14 gdb-mesos-tests.sh.in >>>>> -rw-r--r--. 1 stack stack 1527 Jul 17 23:14 gdb-mesos-slave.sh.in >>>>> -rw-r--r--. 1 stack stack 1530 Jul 17 23:14 gdb-mesos-master.sh.in >>>>> -rw-r--r--. 1 stack stack 1521 Jul 17 23:14 gdb-mesos-local.sh.in >>>>> drwxr-xr-x. 2 stack stack 4096 Jul 17 23:21 . >>>>> drwxr-xr-x. 11 stack stack 4096 Sep 4 20:08 .. >>>>> >>>>> So .. two things: >>>>> >>>>> (a) what is missing from the installation instructions? >>>>> >>>>> (b) Is there an *up to date *rpm/yum installation for centos7? >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>> >
