mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anand Mazumdar (JIRA)" <>
Subject [jira] [Commented] (MESOS-4449) SegFault on agent during executor startup
Date Thu, 21 Jan 2016 18:14:39 GMT


Anand Mazumdar commented on MESOS-4449:

Thanks for reporting this. The culprit here seems to be an erroneous {{NULL}} dereference
introduced by me.

Patch for the fix:

> SegFault on agent during executor startup
> -----------------------------------------
>                 Key: MESOS-4449
>                 URL:
>             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 (
> - This only occurs with 0.26, not with 0.25.
>            Reporter: Philip Winder
>         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

View raw message