[ 
https://issues.apache.org/jira/browse/MESOS-1629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14096387#comment-14096387
 ] 

Vinod Kone commented on MESOS-1629:
-----------------------------------

https://reviews.apache.org/r/24687/

> GLOG Initialized twice if the Framework Scheduler also uses GLOG
> ----------------------------------------------------------------
>
>                 Key: MESOS-1629
>                 URL: https://issues.apache.org/jira/browse/MESOS-1629
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Zuyu Zhang
>            Assignee: Vinod Kone
>
> {noformat}
> Could not create logging file: No such file or directory
> COULD NOT CREATE A LOGGINGFILE 20140722-205220.31450!F0722 20:52:20.494424 
> 31450 utilities.cc:317] Check failed: !IsGoogleLoggingInitialized() You 
> called InitGoogleLogging() twice!
> *** Check failure stack trace: ***
>     @           0x4399ce  google::LogMessage::Fail()
>     @           0x43991d  google::LogMessage::SendToLog()
>     @           0x43932e  google::LogMessage::Flush()
>     @           0x43c0e5  google::LogMessageFatal::~LogMessageFatal()
>     @           0x44089f  
> google::glog_internal_namespace_::InitGoogleLoggingUtilities()
>     @           0x43c409  google::InitGoogleLogging()
>     @     0x7f0bdd43b55c  mesos::internal::logging::initialize()
>     @     0x7f0bdcf9564d  mesos::scheduler::MesosProcess::MesosProcess()
>     @     0x7f0bdcf92de0  mesos::scheduler::Mesos::Mesos()
>     @           0x421483  heron::mesos::Scheduler::Scheduler()
>     @           0x4305dc  main
>     @     0x7f0bd97159c4  __libc_start_main
>     @           0x420869  (unknown)
> Aborted
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to