mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph Wu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-7565) Container with "Contiv" networking fails upon startup
Date Thu, 25 May 2017 21:45:04 GMT

    [ https://issues.apache.org/jira/browse/MESOS-7565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16025439#comment-16025439
] 

Joseph Wu commented on MESOS-7565:
----------------------------------

It appears that, with your networking setup, the executor cannot open a connection to the
agent (presumably located at {{192.168.110.2}}).  That's why the executor logs {{Agent exited
... shutting down}}.

> Container with "Contiv" networking fails upon startup
> -----------------------------------------------------
>
>                 Key: MESOS-7565
>                 URL: https://issues.apache.org/jira/browse/MESOS-7565
>             Project: Mesos
>          Issue Type: Bug
>          Components: network
>    Affects Versions: 1.2.2, 1.3.1
>         Environment: centos 7.3
>            Reporter: Hao Yixin
>
> When launching a task through Marathon and asking the task to assign an IP (using Contiv
networking):
> Log from mesos-slave:
> I0525 18:52:15.898908  1210 linux_launcher.cpp:429] Launching container c4b299e6-629a-4a99-bd88-cfbca0262b1a
and cloning with namespaces CLONE_NEWNS | CLONE_NEWUTS | CLONE_NEWNET
> I0525 18:52:15.900668  1210 systemd.cpp:96] Assigned child process '3985' to 'mesos_executors.slice'
> I0525 18:52:15.902612  1206 containerizer.cpp:1623] Checkpointing container's forked
pid 3985 to '/var/lib/mesos/meta/slaves/00e6894c-d896-4a3d-8e79-679077f2af81-S4/frameworks/00e6894c-d896-4a3d-8e79-679077f2af81-0000/executors/container.1467.373c1d9b-4138-11e7-9117-024221dd5669/runs/c4b299e6-629a-4a99-bd88-cfbca0262b1a/pids/forked.pid'
> I0525 18:52:15.903939  1206 cni.cpp:888] Bind mounted '/proc/3985/ns/net' to '/run/mesos/isolators/network/cni/c4b299e6-629a-4a99-bd88-cfbca0262b1a/ns'
for container c4b299e6-629a-4a99-bd88-cfbca0262b1a
> I0525 18:52:16.347486  1206 cni.cpp:1301] Got assigned IPv4 address '192.168.110.2/24'
from CNI network 'netcontiv' for container c4b299e6-629a-4a99-bd88-cfbca0262b1a
> I0525 18:52:16.347533  1206 cni.cpp:1307] Got assigned IPv6 address '' from CNI network
'netcontiv' for container c4b299e6-629a-4a99-bd88-cfbca0262b1a
> I0525 18:52:16.347687  1206 cni.cpp:1010] Unable to find DNS nameservers for container
c4b299e6-629a-4a99-bd88-cfbca0262b1a, using host '/etc/resolv.conf'
> I0525 18:52:24.579439  1206 containerizer.cpp:2508] Container c4b299e6-629a-4a99-bd88-cfbca0262b1a
has exited
> I0525 18:52:24.579493  1206 containerizer.cpp:2102] Destroying container c4b299e6-629a-4a99-bd88-cfbca0262b1a
in RUNNING state
> I0525 18:52:24.579560  1206 linux_launcher.cpp:505] Asked to destroy container c4b299e6-629a-4a99-bd88-cfbca0262b1a
> I0525 18:52:24.580025  1206 linux_launcher.cpp:548] Using freezer to destroy cgroup mesos/c4b299e6-629a-4a99-bd88-cfbca0262b1a
> I0525 18:52:24.580930  1206 cgroups.cpp:2692] Freezing cgroup /sys/fs/cgroup/freezer/mesos/c4b299e6-629a-4a99-bd88-cfbca0262b1a
> I0525 18:52:24.582156  1206 cgroups.cpp:1405] Successfully froze cgroup /sys/fs/cgroup/freezer/mesos/c4b299e6-629a-4a99-bd88-cfbca0262b1a
after 1.18784ms
> I0525 18:52:24.583359  1206 cgroups.cpp:2710] Thawing cgroup /sys/fs/cgroup/freezer/mesos/c4b299e6-629a-4a99-bd88-cfbca0262b1a
> I0525 18:52:24.584491  1206 cgroups.cpp:1434] Successfully thawed cgroup /sys/fs/cgroup/freezer/mesos/c4b299e6-629a-4a99-bd88-cfbca0262b1a
after 1.093888ms
> I0525 18:52:24.681495  1203 cni.cpp:1479] Unmounted the network namespace handle '/run/mesos/isolators/network/cni/c4b299e6-629a-4a99-bd88-cfbca0262b1a/ns'
for container c4b299e6-629a-4a99-bd88-cfbca0262b1a
> I0525 18:52:24.681591  1203 cni.cpp:1490] Removed the container directory '/run/mesos/isolators/network/cni/c4b299e6-629a-4a99-bd88-cfbca0262b1a'
> I0525 18:52:24.691004  1203 slave.cpp:5168] Executor 'container.1467.373c1d9b-4138-11e7-9117-024221dd5669'
of framework 00e6894c-d896-4a3d-8e79-679077f2af81-0000 terminated with signal Killed
> I0525 18:52:24.691063  1203 slave.cpp:4215] Handling status update TASK_FAILED (UUID:
e90f3161-d136-4607-a67c-a621df9e82e4) for task container.1467.373c1d9b-4138-11e7-9117-024221dd5669
of framework 00e6894c-d896-4a3d-8e79-679077f2af81-0000 from @0.0.0.0:0
> Log from sandbox:
> I0525 18:52:36.583499  4041 exec.cpp:162] Version: 1.3.0
> E0525 18:52:39.593489  4050 process.cpp:2450] Failed to shutdown socket with fd 6, address
192.168.110.2:34176: Transport endpoint is not connected
> I0525 18:52:39.593582  4048 exec.cpp:497] Agent exited ... shutting down
> However, when deploying a task without ipAddress field, mesos slave launches a task successfully.
> Tested with various Mesos/Marathon/Contiv versions.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message