Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-6110

mongos crashes on startup

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.0.6
    • Component/s: None
    • Labels:
      None
    • Environment:
      ubuntu 10.04
    • Linux

      my 3rd config server died and I brought it back online (same ip/hostname).

      Now, from another box, I try to start mongos it crashes:
      Fri Jun 15 23:10:30 /ebs/mongo/LATEST/bin/mongos db version v2.0.6, pdfile version 4.5 starting (--help for usage)
      Fri Jun 15 23:10:30 git version: e1c0cbc25863f6356aa4e31375add7bb49fb05bc
      Fri Jun 15 23:10:30 build info: Linux ip-10-110-9-236 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_41
      Fri Jun 15 23:10:30 SyncClusterConnection connecting to [ge2.mongo.config.a.domain.com:27019]
      Fri Jun 15 23:10:30 SyncClusterConnection connecting to [ge2.mongo.config.b.domain.com:27019]
      Fri Jun 15 23:10:30 SyncClusterConnection connecting to [ge2.mongo.config.c.domain.com:27019]
      Fri Jun 15 23:10:31 [Balancer] about to contact config servers and shards
      Fri Jun 15 23:10:31 [websvr] admin web console waiting for connections on port 28017
      Fri Jun 15 23:10:31 [Balancer] SyncClusterConnection connecting to [ge2.mongo.config.a.domain.com:27019]
      Fri Jun 15 23:10:31 [mongosMain] waiting for connections on port 27017
      Fri Jun 15 23:10:31 [Balancer] SyncClusterConnection connecting to [ge2.mongo.config.b.domain.com:27019]
      Fri Jun 15 23:10:31 [Balancer] SyncClusterConnection connecting to [ge2.mongo.config.c.domain.com:27019]
      Fri Jun 15 23:10:31 [Balancer] starting new replica set monitor for replica set ge-1 with seed of ge2.mongo.1.a.domain.com:27017,ge2.mongo.1.b.domain.com:27017
      Fri Jun 15 23:10:34 [Balancer] successfully connected to seed ge2.mongo.1.a.domain.com:27017 for replica set ge-1
      Fri Jun 15 23:10:39 [Balancer] Socket recv() timeout 10.71.xx.xx:27017
      Fri Jun 15 23:10:39 [Balancer] SocketException: remote: 10.71.xx.xx:27017 error: 9001 socket exception [3] server [10.71.89.8:27017]
      Fri Jun 15 23:10:39 [Balancer] DBClientCursor::init call() failed
      Received signal 11
      Backtrace: 0x54e5b5 0x7f6ea4effaf0 0x585f03 0x588061 0x5888bd 0x756723 0x756eab 0x75c402 0x7dbbd4 0x7dc15f 0x52503f 0x5273b4 0x8069e0 0x7f6ea5a039ca 0x7f6ea4fb270d
      /ebs/mongo/LATEST/bin/mongos(_ZN5mongo17printStackAndExitEi+0x75)[0x54e5b5]
      /lib/libc.so.6(+0x33af0)[0x7f6ea4effaf0]
      /ebs/mongo/LATEST/bin/mongos(_ZN5mongo17ReplicaSetMonitor16_checkConnectionEPNS_18DBClientConnectionERSsbi+0x1543)[0x585f03]
      /ebs/mongo/LATEST/bin/mongos(_ZN5mongo17ReplicaSetMonitorC1ERKSsRKSt6vectorINS_11HostAndPortESaIS4_EE+0x381)[0x588061]
      /ebs/mongo/LATEST/bin/mongos(_ZN5mongo17ReplicaSetMonitor3getERKSsRKSt6vectorINS_11HostAndPortESaIS4_EE+0x1fd)[0x5888bd]
      /ebs/mongo/LATEST/bin/mongos(_ZN5mongo5Shard7_rsInitEv+0x133)[0x756723]
      /ebs/mongo/LATEST/bin/mongos(_ZN5mongo5Shard8_setAddrERKSs+0x13b)[0x756eab]
      /ebs/mongo/LATEST/bin/mongos(_ZN5mongo15StaticShardInfo6reloadEv+0xab2)[0x75c402]
      /ebs/mongo/LATEST/bin/mongos(_ZN5mongo8Balancer5_initEv+0x44)[0x7dbbd4]
      /ebs/mongo/LATEST/bin/mongos(_ZN5mongo8Balancer3runEv+0x3f)[0x7dc15f]
      /ebs/mongo/LATEST/bin/mongos(_ZN5mongo13BackgroundJob7jobBodyEN5boost10shared_ptrINS0_9JobStatusEEE+0xbf)[0x52503f]
      /ebs/mongo/LATEST/bin/mongos(_ZN5boost6detail11thread_dataINS_3_bi6bind_tIvNS_4_mfi3mf1IvN5mongo13BackgroundJobENS_10shared_ptrINS7_9JobStatusEEEEENS2_5list2INS2_5valueIPS7_EENSD_ISA_EEEEEEE3runEv+0x74)[0x5273b4]
      /ebs/mongo/LATEST/bin/mongos(thread_proxy+0x80)[0x8069e0]
      /lib/libpthread.so.0(+0x69ca)[0x7f6ea5a039ca]
      /lib/libc.so.6(clone+0x6d)[0x7f6ea4fb270d]

            Assignee:
            matulef Kevin Matulef
            Reporter:
            mikek Mike Khristo
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: