You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2014/09/02 21:00:21 UTC
[jira] [Commented] (MESOS-1735) Better Startup Failure For
Duplicate Master
[ https://issues.apache.org/jira/browse/MESOS-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118544#comment-14118544 ]
Benjamin Mahler commented on MESOS-1735:
----------------------------------------
We could use the EXIT approach from stout/exit.hpp here to avoid the abort / stacktrace and to include a helpful message.
> Better Startup Failure For Duplicate Master
> -------------------------------------------
>
> Key: MESOS-1735
> URL: https://issues.apache.org/jira/browse/MESOS-1735
> Project: Mesos
> Issue Type: Bug
> Components: master
> Affects Versions: 0.20.0
> Environment: Ubuntu 12.04
> Reporter: Ken Sipe
>
> The error message is cryptic when starting a mesos-master when a mesos-master is already running. The error message is:
> mesos-master --ip=192.168.74.174 --work_dir=~/mesos
> WARNING: Logging before InitGoogleLogging() is written to STDERR
> F0826 20:24:56.940961 3057 process.cpp:1632] Failed to initialize, bind: Address already in use [98]
> *** Check failure stack trace: ***
> Aborted (core dumped)
> This can be a new person's first experience. It isn't clear to them that the process is already running. And they are lost as to what to do next.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)