You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Dominic Hamon (JIRA)" <ji...@apache.org> on 2014/09/15 20:50:33 UTC

[jira] [Closed] (MESOS-1735) Better Startup Failure For Duplicate Master

     [ https://issues.apache.org/jira/browse/MESOS-1735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominic Hamon closed MESOS-1735.
--------------------------------
    Resolution: Won't Fix

The error being printed is not unique to running duplicate mesos masters as another process may be bound to the requested port. As such, the error message is accurate.

Correctly identifying that another master is already running is a larger scope issue that doesn't seem particularly useful to add.

> 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)