[
https://issues.apache.org/jira/browse/MESOS-4601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133290#comment-15133290
]
Neil Conway commented on MESOS-4601:
------------------------------------
{noformat}
F0204 03:34:54.241533 4236 process.cpp:892] Failed to initialize: Failed to
bind on 10.0.1.128:5051: Address already in use: Address already in use [98]
*** Check failure stack trace: ***
@ 0x7f762c7729fd google::LogMessage::Fail()
@ 0x7f762c77489d google::LogMessage::SendToLog()
@ 0x7f762c7725ec google::LogMessage::Flush()
@ 0x7f762c7727f9 google::LogMessage::~LogMessage()
@ 0x7f762c77376e google::ErrnoLogMessage::~ErrnoLogMessage()
@ 0x7f762dbad2a9 process::initialize()
@ 0x7f762dbae932 process::ProcessBase::ProcessBase()
@ 0x7f762dbdd791 process::reap()
@ 0x7f762dbe6395 process::subprocess()
@ 0x7f762d3914a9 HDFS::copyToLocal()
@ 0x40efbd download()
@ 0x40b9da main
@ 0x7f762b727efb (unknown)
@ 0x40d3b3 (unknown)
{noformat}
> Don't dump stack trace on failure to bind()
> -------------------------------------------
>
> Key: MESOS-4601
> URL: https://issues.apache.org/jira/browse/MESOS-4601
> Project: Mesos
> Issue Type: Bug
> Components: libprocess
> Reporter: Neil Conway
> Labels: errorhandling, libprocess, mesosphere, newbie
>
> We should do {{EXIT(EXIT_FAILURE)}} rather than {{LOG(FATAL)}}, both for this
> code path and a few other expected error conditions in libprocess network
> initialization.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
