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

mongodump segfaults when host is passed a replSet string

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.2.0
    • Component/s: Tools
    • Labels:
      None
    • ALL

      When mongodump is run against a replica set string :

      ./mongodump --host foo/host1,host2 it throws a segmentation fault. See below :

      sid@ferrari:~/10gen/mongo$ ./mongodump --host foo/ferrari:31000,ferrari:31001
      Mon Sep 10 13:11:12 starting new replica set monitor for replica set foo with seed of ferrari:31000,ferrari:31001
      Mon Sep 10 13:11:12 successfully connected to seed ferrari:31000 for replica set foo
      Mon Sep 10 13:11:12 changing hosts to { 0: "ferrari:31000", 1: "ferrari:31001" } from foo/
      Mon Sep 10 13:11:12 trying to add new host ferrari:31000 to replica set foo
      Mon Sep 10 13:11:12 successfully connected to new host ferrari:31000 in replica set foo
      Mon Sep 10 13:11:12 trying to add new host ferrari:31001 to replica set foo
      Mon Sep 10 13:11:12 successfully connected to new host ferrari:31001 in replica set foo
      Mon Sep 10 13:11:12 Primary for replica set foo changed to ferrari:31000
      Mon Sep 10 13:11:12 replica set monitor for replica set foo started, address is foo/ferrari:31000,ferrari:31001
      Mon Sep 10 13:11:12 [ReplicaSetMonitorWatcher] starting
      connected to: foo/ferrari:31000,ferrari:31001
      Mon Sep 10 13:11:12 all dbs
      Logstream::get called in uninitialized state
      Mon Sep 10 13:11:12 deleting replica set monitor for: foo/ferrari:31000,ferrari:31001
      Segmentation fault
      

            Assignee:
            tad Tad Marshall
            Reporter:
            siddharth.singh@10gen.com siddharth.singh@10gen.com
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: