You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Zogg (JIRA)" <ji...@apache.org> on 2016/03/29 20:25:25 UTC

[jira] [Created] (MESOS-5061) process.cpp:1966] Failed to shutdown socket with fd x: Transport endpoint is not connected

Zogg created MESOS-5061:
---------------------------

             Summary: process.cpp:1966] Failed to shutdown socket with fd x: Transport endpoint is not connected
                 Key: MESOS-5061
                 URL: https://issues.apache.org/jira/browse/MESOS-5061
             Project: Mesos
          Issue Type: Bug
          Components: containerization, modules
    Affects Versions: 0.27.2, 0.28.0, 0.27.1, 0.27.0
         Environment: Centos 7.1
            Reporter: Zogg
             Fix For: 0.26.0


When launching a task through Marathon and asking the task to assign an IP (using Calico networking):

{noformat}
{
    "id":"/calico-apps",
    "apps": [
        {
            "id": "hello-world-1",
            "cmd": "ip addr && sleep 30000",
            "cpus": 0.1,
            "mem": 64.0,
            "ipAddress": {
                "groups": ["calico-k8s-network"]
            }
        }
    ]
}
{noformat}

Mesos slave fails to launch a task, locking in STAGING state forewer, with error:
{noformat}
[centos@rtmi-worker-001 mesos]$ tail mesos-slave.INFO
I0325 20:35:43.420171 13495 slave.cpp:2642] Got registration for executor 'calico-apps_hello-world-1.23ff72e9-f2c9-11e5-bb22-be052ff413d3' of framework 23b404e4-700a-4348-a7c0-226239348981-0000 from executor(1)@10.0.0.10:33443
I0325 20:35:43.422652 13495 slave.cpp:1862] Sending queued task 'calico-apps_hello-world-1.23ff72e9-f2c9-11e5-bb22-be052ff413d3' to executor 'calico-apps_hello-world-1.23ff72e9-f2c9-11e5-bb22-be052ff413d3' of framework 23b404e4-700a-4348-a7c0-226239348981-0000 at executor(1)@10.0.0.10:33443
E0325 20:35:43.423159 13502 process.cpp:1966] Failed to shutdown socket with fd 22: Transport endpoint is not connected
I0325 20:35:43.423316 13501 slave.cpp:3481] executor(1)@10.0.0.10:33443 exited
{noformat}

However, when deploying a task without ipAddress field, mesos slave launches a task successfully. 

Tested with various Mesos/Marathon/Calico versions. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)