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 Hindman (JIRA)" <ji...@apache.org> on 2012/07/21 02:46:34 UTC

[jira] [Closed] (MESOS-220) Slave throws exception in librocess when master is down

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

Benjamin Hindman closed MESOS-220.
----------------------------------

    
> Slave throws exception in librocess when master is down
> -------------------------------------------------------
>
>                 Key: MESOS-220
>                 URL: https://issues.apache.org/jira/browse/MESOS-220
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Vinod Kone
>
> This happened when the master was down (during a deploy)/
> I0625 22:20:22.007020 14393 detector.cpp:575] Master detector got new master pid: master@10.35.9.132:5050
> I0625 22:20:22.007113 14393 slave.cpp:324] New master detected at master@10.35.9.132:5050
> I0625 22:20:22.007361 14393 slave.cpp:1069] Process exited: master@10.35.9.132:5050
> W0625 22:20:22.007411 14393 slave.cpp:1072] WARNING! Master disconnected! Waiting for a new master to be elected.
> F0625 22:20:22.137459 14394 process.cpp:1551] Check failed: sockets.count(s) > 0 
> *** Check failure stack trace: ***
>     @     0x7fb84d7707bd  google::LogMessage::Fail()
>     @     0x7fb84d776427  google::LogMessage::SendToLog()
>     @     0x7fb84d77206c  google::LogMessage::Flush()
>     @     0x7fb84d7722d6  google::LogMessageFatal::~LogMessageFatal()
>     @     0x7fb84d78e3a2  process::SocketManager::next()
>     @     0x7fb84d7910de  process::send_data()
>     @     0x7fb84d7a9343  ev_invoke_pending
>     @     0x7fb84d7ae778  ev_loop
>     @     0x7fb84d77e1eb  process::serve()
>     @       0x37e500673d  (unknown)
>     @       0x37e40d3f6d  (unknown)
> Bottle server starting up (using WSGIRefServer())...
> Listening on http://0.0.0.0:8081/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira