It looks like you mistyped GLOG_V, it should be GLOG_v.
Can you re-run them with GLOG_v=2 and send the verbose logs? I couldn't
tell form those logs what the issue was.
I'm also wondering why your slaves were built on Oct 21st and your master
was built on Dec 31st. What version are you running?
Hi,
Please find the attached folders of mesos slave and mesos master logs.
I used the following commands to start the master and slave respectively
MESOS_VERBOSE=1 GLOG_V=2 ./bin/mesos-master.sh
--log_dir=/home/test/mesos_logs
MESOS_VERBOSE=1 GLOG_V=2 ./bin/mesos-slave.sh
--master=192.168.145.18
Running the master / slave with GLOG_v=2 in your environment may prove more
insightful.
Can you provide the full textual version of the logs instead of screenshots
please? :)
On Mon, Jan 13, 2014 at 8:36 PM, Sai Sagar wrote:
> Hi,
>
> Please find the attached images of master log and slave log
Hi,
Thanks for the quick reply.
My framework just registers. It does not reregister. I do not have access
to system right now. But I remember that hierarchial-allocator registered
the framework and added to the scheduler(1). *But master.cpp is not sending
offers to my framework.* I will mail deta
Does your framework constantly reregister? If so, it is likely a firewall /
ports issue between framework and master.
On Mon, Jan 13, 2014 at 9:07 PM, Sai Sagar wrote:
> Hi all,
>
> I am implementing a framework on the top of mesos. The framework is
> registered successfully but the master is n
Can you provide the commands you're using to run the master and slaves?
Can you provide the master and slave logs?
On Mon, Jan 13, 2014 at 6:07 PM, Sai Sagar wrote:
> Hi all,
>
> I am implementing a framework on the top of mesos. The framework is
> registered successfully but the master is not
Hi all,
I am implementing a framework on the top of mesos. The framework is
registered successfully but the master is not sending any offers to the
framework. Can any suggest me what might the issue here?
Thanks and Regards,
Sai Sagar.J
7 matches
Mail list logo
