singa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chen Peng (JIRA)" <>
Subject [jira] [Created] (SINGA-150) "called InitGoogleLogging() twice!" error
Date Thu, 17 Mar 2016 23:47:33 GMT
Chen Peng created SINGA-150:

             Summary: "called InitGoogleLogging() twice!" error
                 Key: SINGA-150
             Project: Singa
          Issue Type: Bug
         Environment: Ubuntu 12.04.5 LTS (GNU/Linux 3.13.0-83-generic x86_64)
            Reporter: Chen Peng

When launching SINGA on pseudo-distributed mode (single node) according to
and train it according to, two nodes (node0 and node1)
are created.

When executing the command `./scheduler /root/incubator-singa/│  zookeeper-3.4.6
examples/cifar10/job.conf -scheduler_conf ./scheduler.conf -singa_conf /roo│root@node1:~/incubator-singa/thirdparty#
t/incubator-singa/conf/singa.conf ', the following error is displayed:

I0317 23:08:19.499140   298] Scheduler initialized
F0317 23:08:19.503722   298] Check failed: !IsGoogleLoggin
gInitialized() You called InitGoogleLogging() twice!
*** Check failure stack trace: ***
    @     0x7f9178664612  google::LogMessage::Fail()
    @     0x7f917866455e  google::LogMessage::SendToLog()
    @     0x7f9178663f60  google::LogMessage::Flush()
    @     0x7f9178666e74  google::LogMessageFatal::~LogMessageFatal()
    @     0x7f917866ac21  google::glog_internal_namespace_::InitGoogleLoggi
    @     0x7f917866717f  google::InitGoogleLogging()
    @     0x7f9177ccff6d  mesos::internal::logging::initialize()
    @     0x7f9177eba176  mesos::MesosSchedulerDriver::initialize()
    @     0x7f9177eba95c  mesos::MesosSchedulerDriver::MesosSchedulerDriver
    @           0x408c3d  main
    @     0x7f9174109ec5  (unknown)
    @           0x408669  (unknown)

This message was sent by Atlassian JIRA

View raw message