1. You could run it as a daemon, what you're doing with nohup is fine as well.
2. The webui shows various resource statistics: [image: Inline image 2] *Total memory* indicates the total amount of memory available on all the slaves. Total Memory should equal Used + Idle + Offered * * *Used:* Memory used by the frameworks. *Offered:* This memory has been offered but the framework hasn't responded yet. *Idle:* Any remaining memory in the system. 3. Are you running off trunk or a release? What is the command line you're running to start the master? Can you provide the master's log output? On Tue, Sep 18, 2012 at 11:57 PM, praveenesh kumar <[email protected]>wrote: > Hi all, > > I have been able to successfully build and install mesos on my physical > nodes. I can see the mesos web-url with list of mesos slaves. However I am > finding few difficulties w.r.t to following things: > > *1. How to start mesos-master.sh and mesos-slave.sh as a background process > ? * > I am seeing all my output on the console. Since I want to remotely start > the service on the cluster, I tried using nohup. Its working for now, but > is it the right way? I am hoping there should be better way to do that. > > *2.* *Whatever memory I am seeing on the mesos-web url, is it the total > memory or the free memory available on my system ?* > I am seeing very low memory (0.001 GB) -- Does it indicate the current > available memory ? > > 3. I have enable the "log_dir" directory, while starting the mesos-master > and slaves. I can see the logs for my slave machines from mesos web url, > but not able to see logs for my master. Its saying *"Failed to Initialize > .... Retrying"*. I can see work directory is there as well as the logs are > also there. Set the permission to 777 also. Still no success. > > > Any help on the above to understand mesos, would be very helpful. > > Regards, > Praveenesh >
