This is the error message after grabbing standard error:
/usr/local/sbin/mesos-master: error while loading shared libraries: libmesos-0.12.0.so: cannot open shared object file: No such file or directory What's weird is that the lib is in /usr/local/lib: bin etc games include java jdk1.7.0_21 lib lib64 libexec sbin share src var [root@mesos-test-01 local]# ls -la lib total 85164 drwxr-xr-x. 2 root root 4096 Jul 8 16:49 . drwxr-xr-x. 14 root root 4096 Jul 8 16:49 .. -rwxr-xr-x 1 root root 87194758 Jul 8 16:49 libmesos-0.12.0.so -rwxr-xr-x 1 root root 1014 Jul 8 16:49 libmesos.la lrwxrwxrwx 1 root root 18 Jul 8 16:49 libmesos.so -> libmesos-0.12.0.so On Mon, Jul 8, 2013 at 7:35 PM, Gary Malouf <[email protected]> wrote: > > 1. How are you installing mesos? > > > - I am using > > http://www.globalish.com/am/incubator/mesos/mesos-0.12.0-incubating/mesos-0.12.0-incubating.tar.gzrelease > on CentOS-6.3 > - This gets unpacked into a mesos-0.12.0 directory and the I run: > ./configure --disable-perftools && make && make install > - I then create /var/log/mesos for output logs > - /usr/local/var/mesos/conf/mesos.conf is created which specifies the > zk addresses of the masters and the log directory > - /usr/local/var/mesos/deploy/masters and > /usr/local/var/mesos/deploy/slaves are created for deploy scripts to know > where to start instances > > > > 2. How are you starting the master / slave? > > I usually use the mesos-start-cluster.sh script to start the cluster in > staging - I've tried this and others in my new prod environment to no avail. > > 3. Can you provide the slave logs? > > There are no logs being generated from what I can see - they are only > generated when I run from the build location with local scripts as opposed > to the install one. > > Hope this helps, > > Gary > > > On Mon, Jul 8, 2013 at 6:41 PM, Gary Malouf <[email protected]> wrote: > >> I've run been running a mesos cluster for about a month in our staging >> environment without issue. Today, I tried to compile and install a cluster >> in production using the same build process we did for staging but have run >> into issues getting it to run from the install location. We have the >> log_dir parameter set to /var/log/mesos but no data is showing up in there >> or in /tmp when I run the sbin/start-mesos-cluster.sh scripts. >> >> To be clear, I am able to run masters and slaves from the directory I >> built the code in but the install location seems to have issues. >> >> Two questions: >> >> 1) What are the recommended strategies for debugging an install? >> >> 2) Any other places where the logs could be showing up? >> >> >> Thanks for the help. >> >> Gary >> > >
