[
https://issues.apache.org/jira/browse/MESOS-4449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15113104#comment-15113104
]
Joris Van Remoortere commented on MESOS-4449:
---------------------------------------------
[~philwinder] Once 0.27 is released (soon) we will be doing a set of point fix
releases.
We will include this in the point fix release for 0.26.
> SegFault on agent during executor startup
> -----------------------------------------
>
> Key: MESOS-4449
> URL: https://issues.apache.org/jira/browse/MESOS-4449
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.26.0
> Environment: Some setup details:
> - Master and agents running in separate docker containers on the same host.
> - Containers based upon Ubuntu 14.04 using Mesosphere produced Mesos deb
> files. For more details see
> (https://github.com/ContainerSolutions/minimesos-docker)
> - This only occurs with 0.26, not with 0.25.
> Reporter: Philip Winder
> Assignee: Anand Mazumdar
> Priority: Blocker
> Labels: mesosphere
> Fix For: 0.27.0
>
> Attachments: agent.txt, master.txt
>
>
> When repeatedly performing our system tests we have found that we get a
> segfault on one of the agents. It probably occurs about one time in ten. I
> have attached the full log from that agent. I've attached the log from the
> agent that failed and the master (although I think this is less helpful).
> To reproduce
> - I have no idea. It seems to occur at certain times. E.g. like if a packet
> is created right on a minute boundary or something. But I don't think it's
> something caused by our code because the timestamps are stamped by mesos. I
> was surprised not to find a bug already open.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
