You don't have to build it on every machine. Just install checkinstall tool, build it on one machine and create package. When building, after make command don't run make install, instead run:
checkinstall --install=no --pkgname=mesos --pkgversion=0.28.2 -y I am using Ubuntu, so in my case it will create deb package. Just copy it over to every node and do: dpkg -i <package_name> With this approach, it is very easy to update mesos to the most recent version. 2016-07-08 1:56 GMT+02:00 Douglas Nelson <itsbeh...@gmail.com>: > Inlining the environment variable fixed it! I had to use sudo to run > mesos, so I either needed to inline it or use -E. *Facepalm* > > On the note of building mesos, is there any chance in the future that > mesosphere would create a prebuilt mesos package with ssl included? It > would be nice to avoid building on each machine I want to run mesos on. > Also, it would be great to have the convenience of using config files, > having automatic startup, etc with a simple apt-get install mesos-ssl. Is > that something that's been considered? > > Thanks! > > On Thu, Jul 7, 2016 at 1:14 PM, Joseph Wu <jos...@mesosphere.io> wrote: > >> Can you double-check if your master is linking to openssl? >> >> From your build folder, you should get something like: >> ldd src/.libs/mesos-master | grep ssl >> libevent_openssl-2.0.so.5 => /lib64/libevent_openssl-2.0.so.5 >> libssl.so.10 => /lib64/libssl.so.10 >> libssl3.so => /lib64/libssl3.so >> >> There doesn't seem to be anything wrong with your configure/build steps. >> And your environment variables setup should work on any sane Unix shell. >> (Perhaps inline the environment variable? SSL_ENABLED=true >> ./mesos-master.sh ...) >> >> On Thu, Jul 7, 2016 at 11:53 AM, Douglas Nelson <itsbeh...@gmail.com> >> wrote: >> >>> I rebuilt from scratch with SSL support and got no errors. I only set >>> *export >>> SSL_ENABLED=true* and then I ran the mesos-master. >>> >>> No errors were thrown and I can see the web UI via HTTP. I double >>> checked that I was running the .sh from the build folder I created. Is >>> mesos not connecting with the environment variable I set for some reason? >>> >>> >>> >>> On Wed, Jul 6, 2016 at 2:20 PM, Joseph Wu <jos...@mesosphere.io> wrote: >>> >>>> If you can see the WebUI via HTTP, without downgrade support, you might >>>> be inadvertently running a different version of Mesos than the one you >>>> built. >>>> >>>> You can quickly sanity check this by removing either SSL_KEY_FILE or >>>> SSL_CERT_FILE and starting your master. If your build has SSL support, it >>>> should immediately exit with an error message. >>>> >>>> >>>> On Wed, Jul 6, 2016 at 12:33 PM, Douglas Nelson <itsbeh...@gmail.com> >>>> wrote: >>>> > >>>> > I attempted to set up SSL following this guide: >>>> http://mesos.apache.org/documentation/latest/ssl/ >>>> > >>>> > I'm able to hit the WebUI with http but using https gives me nothing. >>>> I must be missing something. Here are the steps I'm taking: >>>> > >>>> > I downloaded 0.28.2 from here: >>>> https://github.com/apache/mesos/releases >>>> > I ran ./configure --enable-libevent --enable-ssl >>>> > Then I ran make and make install >>>> > I set the following environment variables: >>>> > >>>> > export SSL_ENABLED=1 >>>> > export SSL_SUPPORT_DOWNGRADE=0 >>>> > export SSL_KEY_FILE=<path> >>>> > export SSL_CERT_FILE=<path> >>>> > >>>> > Finally, I ran ./bin/mesos-master.sh --ip=127.0.0.1 >>>> --work_dir=/var/lib/mesos >>>> > >>>> > I can provide any additional information if needed. Thanks! >>>> > >>>> > Also, I read that SSL would be included in mesosphere's nightly >>>> builds: https://open.mesosphere.com/downloads/mesos-nightly/ >>>> > >>>> > How stable are those builds and has SSL already been included? >>>> > >>>> > -Doug Nelson >>>> >>>> >>> >> >
