Florian Leibert (flo) created MESOS-306:
-------------------------------------------
Summary: Mesos-master frequently crashes
Key: MESOS-306
URL: https://issues.apache.org/jira/browse/MESOS-306
Project: Mesos
Issue Type: Bug
Environment: git revision 735a95a3e07f7727873102f10be97a3af9f71488
Ubuntu 12.04.
GCC 4.6.3.
1 slave, 1 framework
Reporter: Florian Leibert (flo)
This isn't a production problem
2012-11-08T23:51:44.413588+00:00 F1108 user.notice 23: - 51:44.413082 25542
process.cpp:1847] Check failed: outgoing.count(s) > 0
2012-11-08T23:51:44.413847+00:00 localhost user.notice *** - Check failure
stack trace: ***
2012-11-08T23:51:44.415051+00:00 localhost user.notice - @
0x7fdfd41f97cd google::LogMessage::Fail()
2012-11-08T23:51:44.416053+00:00 localhost user.notice - @
0x7fdfd41fbf5f google::LogMessage::SendToLog()
2012-11-08T23:51:44.416879+00:00 localhost user.notice - @
0x7fdfd41f93cb google::LogMessage::Flush()
2012-11-08T23:51:44.417800+00:00 localhost user.notice - @
0x7fdfd41fc7ed google::LogMessageFatal::~LogMessageFatal()
2012-11-08T23:51:44.419206+00:00 localhost user.notice - @
0x7fdfd40eb7b2 process::SocketManager::next()
2012-11-08T23:51:44.420778+00:00 localhost user.notice - @
0x7fdfd40e56de process::send_data()
2012-11-08T23:51:44.422754+00:00 localhost user.notice - @
0x7fdfd42390ff ev_invoke_pending
2012-11-08T23:51:44.424959+00:00 localhost user.notice - @
0x7fdfd423d434 ev_loop
2012-11-08T23:51:44.425862+00:00 localhost user.notice - @
0x7fdfd40e6a1c process::serve()
2012-11-08T23:51:44.426145+00:00 localhost user.notice - @
0x7fdfd3430e9a start_thread
2012-11-08T23:51:44.426398+00:00 localhost user.notice - @
0x7fdfd315ddbd (unknown)
2012-11-08T23:51:44.554052+00:00 Bottle user.notice server - starting up (using
WSGIRefServer())...
2012-11-08T23:51:44.554052+00:00 Listening user.notice on - http://0.0.0.0:8080/
2012-11-08T23:51:44.554092+00:00 Use user.notice Ctrl-C - to quit.
2012-11-08T23:51:44.554092+00:00 localhost user.notice -
--
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
