>From the stderr log, nothing can be figure out. From stout log, it says server 
>running at host:port. But If I do telnet or curl, it does not show me any 
>reponse.output of stderr log :
I0412 08:16:12.842341  9909 exec.cpp:134] Version: 0.27.1I0412 08:16:12.844701  
9934 exec.cpp:208] Executor registered on slave 
87849fd2-fda9-4d6a-870f-de101a5bdc59-S3js-bson: Failed to load c++ bson 
extension, using pure JS version 

    On Tuesday, 12 April 2016 1:39 PM, Abhishek Amralkar 
<[email protected]> wrote:
 

 anything is sandbox logs, why the tasks are getting killed? `stderr` and 
`stdout`?

On 12-Apr-2016, at 1:35 PM, haosdent <[email protected]> wrote:
>Its frequently changing the deployment status to Staged
Do you find any related log in mesos when marathon lauch the task?
On Tue, Apr 12, 2016 at 3:55 PM, nirmalendu swain <[email protected]> 
wrote:

Changing the network type to HOST does not work. Its frequently changing the 
deployment status to Staged and then to no task.

On Tuesday, 12 April 2016 11:49 AM, haosdent <[email protected]> wrote:


How about change the network type from BRIDGE to HOST?
On Tue, Apr 12, 2016 at 2:13 PM, nirmalendu swain <[email protected]> 
wrote:

Hi Mesos user,I am running mesos marathon using dcos for spinning up AWS 
instances. I have successfully built the mongodb as a docker container, but 
when I try to deploy my dockerized app, it does n't deploy. My App is dependent 
upon mongo which is passed as environment variable in the json file to be run 
by dcos command. If a i do a telnet/curl, it does n't receive at the desired 
host:port. from the mesos logs, it does not seem to throw any error/exception. 
Doing a copy-past of my backend-app.json file which falis to deploy.

{    "id": "/todo-with-backend",    "instances": 2,    "container": {        
"type": "DOCKER",        "docker": {            "image": "tldr/todo-backend",   
         "network": "BRIDGE",            "portMappings": [                {     
               "containerPort": 8080,                    "hostPort": 0,         
           "protocol": "tcp"                }            ]        }    
},"env":{       "MONGO_URL":"10.0.2.252:5530" },    "healthChecks": [{        
"protocol": "HTTP",        "portIndex": 0    }],    "labels":{        
"HAPROXY_GROUP":"external",        "<Using the same ELB as that of mongo json 
file>"    },    "cpus": 0.25,    "mem": 256.0}
I have gone inside the host and checked that env value is reflecting 
correctly.Please help me out in analyzing the issue.
Regards,Nirmal





-- 
Best Regards,
Haosdent Huang





-- 
Best Regards,
Haosdent Huang



  

Reply via email to