Do you compile mesos with ssl support? The default compile don't contains ssl. And does docker container have stdour and stderr?
On Thu, Oct 29, 2015 at 11:41 AM, Xiaodong Zhang <xdzh...@alauda.io> wrote: > My scenarios is like previous email says, masters and slaves are in > different IaaS. Now the slaves can register to the masters with SSL_ENABLED > is on . > > But I meet another problem. Slaves can’t run container(the odd thing is > they can pull image successfully,just can not run container, `docker ps –a > ` list nothing) > > The logs like this: > > I1029 03:29:45.967741 9288 docker.cpp:758] Starting container > 'd4f4e236-0d0a-492c-86df-eef48a414e23' for task > '279bcb34-f705-4857-96ad-d96843b848fb.4b3abdcd-7ded-11e5-a82d-0240afabf713' > (and executor > '279bcb34-f705-4857-96ad-d96843b848fb.4b3abdcd-7ded-11e5-a82d-0240afabf713') > of framework '20151029-031549-1294671788-5050-4937-0000' > I1029 03:29:48.044148 9292 docker.cpp:382] Checkpointing pid 12062 to > '/tmp/mesos/meta/slaves/20151029-031549-1294671788-5050-4937-S0/frameworks/20151029-031549-1294671788-5050-4937-0000/executors/279bcb34-f705-4857-96ad-d96843b848fb.4b3abdcd-7ded-11e5-a82d-0240afabf713/runs/d4f4e236-0d0a-492c-86df-eef48a414e23/pids/forked.pid' > I1029 03:29:53.159361 9292 docker.cpp:1576] Executor for container > 'd4f4e236-0d0a-492c-86df-eef48a414e23' has exited > I1029 03:29:53.159572 9292 docker.cpp:1374] Destroying container > 'd4f4e236-0d0a-492c-86df-eef48a414e23' > I1029 03:29:53.159822 9292 docker.cpp:1478] Running docker stop on > container 'd4f4e236-0d0a-492c-86df-eef48a414e23' > I1029 03:29:53.160143 9292 slave.cpp:3399] Executor > '279bcb34-f705-4857-96ad-d96843b848fb.4b3abdcd-7ded-11e5-a82d-0240afabf713' > of framework 20151029-031549-1294671788-5050-4937-0000 terminated with > signal Killed > I1029 03:29:53.160884 9292 slave.cpp:2696] Handling status update > TASK_FAILED (UUID: 27a2080a-8807-449e-9077-837ec45b4c51) for task > 279bcb34-f705-4857-96ad-d96843b848fb.4b3abdcd-7ded-11e5-a82d-0240afabf713 > of framework 20151029-031549-1294671788-5050-4937-0000 from @0.0.0.0:0 > W1029 03:29:53.161247 9288 docker.cpp:986] Ignoring updating unknown > container: d4f4e236-0d0a-492c-86df-eef48a414e23 > I1029 03:29:53.161548 9293 status_update_manager.cpp:322] Received status > update TASK_FAILED (UUID: 27a2080a-8807-449e-9077-837ec45b4c51) for task > 279bcb34-f705-4857-96ad-d96843b848fb.4b3abdcd-7ded-11e5-a82d-0240afabf713 > of framework 20151029-031549-1294671788-5050-4937-0000 > > I run master node with env: > > SSL_SUPPORT_DOWNGRADE=true > SSL_ENABLED=true > SSL_KEY_FILE=/home/ubuntu/xx.key > SSL_CERT_FILE=/home/ubuntu/xx.pem > > Slave node with env: > > SSL_ENABLED=true > SSL_KEY_FILE=/home/ubuntu/xx.key > SSL_CERT_FILE=/home/ubuntu/xx.pem > LIBPROCESS_ADVERTISE_IP=xxx.xxx.xxx.xxx > > When I remove all SSL envs. Slaves work well. > > Did I miss sth? > > Version: > > Mesos 0.24.1 > Maraton 0.9.2 > > OS > ubuntu 14.04 > > > > 发件人: Anindya Sinha <anindya.si...@gmail.com> > 答复: "user@mesos.apache.org" <user@mesos.apache.org> > 日期: 2015年10月28日 星期三 下午2:32 > 至: "user@mesos.apache.org" <user@mesos.apache.org> > 主题: Re: How to tell master which ip to connect. > > > > On Tue, Oct 27, 2015 at 7:43 PM, Xiaodong Zhang <xdzh...@alauda.io> wrote: > >> It works! Thanks a lot. >> > > Ok. So we should expose advertise_ip and advertise_port as command line > options for mesos-slave as well (instead of using the environment > variables)? Opened https://issues.apache.org/jira/browse/MESOS-3809. > > >> >> Another question. Do masters and slaves communicate each other via a >> safety way？Is the data encrypted? I want to make sure deploy masters and >> slaves into different IaaS is PROD-READY. >> >> 发件人: haosdent <haosd...@gmail.com> >> 答复: "user@mesos.apache.org" <user@mesos.apache.org> >> 日期: 2015年10月28日 星期三 上午10:23 >> 至: user <user@mesos.apache.org> >> 主题: Re: How to tell master which ip to connect. >> >> Do you try `export LIBPROCESS_ADVERTISE_IP=xxx` and >> `LIBPROCESS_ADVERTISE_PORT` when start slave? >> >> On Wed, Oct 28, 2015 at 10:16 AM, Xiaodong Zhang <xdzh...@alauda.io> >> wrote: >> >>> Hi teams: >>> >>> My scenarios is like this: >>> >>> My master nodes were deployed in AWS. My slaves were in AZURE.So they >>> communicate via public ip. >>> I got trouble when slaves try to register to master. >>> Now slaves can get master’s public ip address,and can send register >>> request.But they can only send there private ip to master.(Because they >>> don’t know there public ip,thus they can’t not bind a public ip via —ip >>> flag), thus masters can’t connect slaves.How can the slave to tell master >>> which ip master should connect(I can’t find any flags like —advertise_ip >>> in master). >>> >> >> >> >> -- >> Best Regards, >> Haosdent Huang >> > > -- Best Regards, Haosdent Huang
