You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2013/07/16 00:14:48 UTC
[jira] [Commented] (MESOS-508) Master crash due to Broken Pipe
[ https://issues.apache.org/jira/browse/MESOS-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709051#comment-13709051 ]
Benjamin Mahler commented on MESOS-508:
---------------------------------------
https://reviews.apache.org/r/12146/
https://reviews.apache.org/r/12154/
https://reviews.apache.org/r/12148/
> Master crash due to Broken Pipe
> -------------------------------
>
> Key: MESOS-508
> URL: https://issues.apache.org/jira/browse/MESOS-508
> Project: Mesos
> Issue Type: Bug
> Components: master
> Affects Versions: 0.14.0
> Environment: RHEL5
> Reporter: Guodong Wang
> Assignee: Benjamin Mahler
> Priority: Minor
>
> The master receives Broken Pipe signal
> I0608 10:25:11.896606 19079 hierarchical_allocator_process.hpp:569] Framework 201306071736-252063498-5050-19065-0000 filtered slave 201306071736-252063498-5050-19065-2 for 5secs
> I0608 10:25:11.896785 19079 hierarchical_allocator_process.hpp:569] Framework 201306071736-252063498-5050-19065-0000 filtered slave 201306071736-252063498-5050-19065-3 for 5secs
> W0608 10:25:12.738118 19082 logging.cpp:52] Received signal 'Broken pipe', escalating to SIGABRT
> *** Aborted at 1370658312 (unix time) try "date -d @1370658312" if you are using GNU date ***
> PC: @ 0x30c7e0e38d (unknown)
> *** SIGABRT (@0x4a79) received by PID 19065 (TID 0x4bab6940) from PID 19065; stack trace: ***
> @ 0x30c7e0e4c0 (unknown)
> @ 0x30c7e0e38d (unknown)
> @ 0x2b3c35618218 mesos::internal::logging::handler()
> @ 0x30c7e0e4c0 (unknown)
> @ 0x30c72cab4a (unknown)
> @ 0x2b3c357700f1 process::send_file()
> @ 0x2b3c358bd272 ev_invoke_pending
> @ 0x2b3c358c1e0f ev_run
> @ 0x2b3c35766c5b process::serve()
> @ 0x30c7e06367 (unknown)
> @ 0x30c72d30ad (unknown)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira