why applications running in mesos is not being registered in consul? -


i using mesos-consul , deployed via marathon. json config job

{   "id": "/mesos-consul",   "cmd": null,   "cpus": 0.1,   "mem": 256,   "disk": 0,   "instances": 1,   "constraints": [     [       "hostname",       "like",       "fwvm.*"     ]   ],   "acceptedresourceroles": [],   "container": {     "type": "docker",     "volumes": [],     "docker": {       "image": "ciscocloud/mesos-consul",       "network": "bridge",       "portmappings": [],       "privileged": false,       "parameters": [],       "forcepullimage": false     }   },   "portdefinitions": [     {       "port": 10000,       "protocol": "tcp",       "name": "default",       "labels": {}     }   ],   "args": [     "--zk=zk://zookeeper.service.consul:2181/mesos",     "--log-level=debug",     "--consul",     "--refresh=5s"   ] } 

i running consul 1 server , 1 client.

consul members info node  address            status  type    build  protocol  dc vm1   10.21.10.22:8301  alive   server  0.7.5  2         devops vm2   10.21.10.25:8301  alive   client  0.7.5  2         devops 

mesos , marathon looks good. still not working

mesos-consul logs showing

i0410 14:45:17.917712 18194 exec.cpp:162] version: 1.2.0 i0410 14:45:17.929821 18200 exec.cpp:237] executor registered on agent 92704ba7-7324-4e74-a7fd-7b7c642766b2-s0 i0410 14:45:17.932121 18197 docker.cpp:850] running docker -h unix:///var/run/docker.sock run --cpu-shares 102 --memory 268435456 --env-file /tmp/ydr5nl -v /var/lib/mesos/slaves/92704ba7-7324-4e74-a7fd-7b7c642766b2-s0/frameworks/2679cb7f-1fc2-4e8b-be3c-44f0fb54f618-0000/executors/mesos-consul.36b6d6d3-1dce-11e7-a717-0242b31c8310/runs/6a22da5d-4a33-4d1d-ada7-cd688474e4fc:/mnt/mesos/sandbox --net bridge --label=mesos_task_id=mesos-consul.36b6d6d3-1dce-11e7-a717-0242b31c8310 --name mesos-92704ba7-7324-4e74-a7fd-7b7c642766b2-s0.6a22da5d-4a33-4d1d-ada7-cd688474e4fc ciscocloud/mesos-consul --zk=zk://http://10.202.11.22:2181/mesos --log-level=debug --consul --refresh=5s time="2017-04-10t09:15:22z" level=info msg="using zookeeper: zk://http://10.202.11.22:2181/mesos"  time="2017-04-10t09:15:22z" level=debug msg="zookeeper address" zk="zk://http://10.202.11.22:2181/mesos"  

got issue fixed now. network related issue. alpine linux trying query

nameserver 127.0.0.1

replaced our dns server.


Comments

Popular posts from this blog

Command prompt result in label. Python 2.7 -

javascript - How do I use URL parameters to change link href on page? -

amazon web services - AWS Route53 Trying To Get Site To Resolve To www -