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

config database not restored during dumprestore9.js test

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.1.1
    • Affects Version/s: None
    • Component/s: Tools
    • Linux
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      shell: started program /data/slave/Linux_64bit_v8/mongo/mongorestore /data/db/dumprestore9-dump1/ --host localhost:30998 --restoreShardingConfig --forceConfigRestore
      sh12192| connected to: localhost:30998
      sh12192| Mon Mar  5 18:53:08 WARNING: this will drop the config database, overriding any sharding configuration you currently have.
      sh12192| Mon Mar  5 18:53:08 DO NOT RUN THIS COMMAND WHILE YOUR CLUSTER IS ACTIVE
      sh12192| Mon Mar  5 18:53:08 Running with --forceConfigRestore. Continuing.
      sh12192| Mon Mar  5 18:53:08 Error dropping config database. Aborting
      assert failed : Config data wasn't restored properly
      Error: Printing Stack Trace
          at src/mongo/shell/utils.js:37:7
          at src/mongo/shell/utils.js:58:1
          at src/mongo/shell/utils.js:66:1
          at /data/slave/Linux_64bit_v8/mongo/jstests/tool/dumprestore9.js:59:1
      Mon Mar  5 18:53:08 exec error: src/mongo/shell/utils.js:59 assert failed : Config data wasn't restored properly
      throw msg;
            ^
      
      failed to load: /data/slave/Linux_64bit_v8/mongo/jstests/tool/dumprestore9.js
      

      http://buildbot.mongodb.org/builders/Linux%2064-bit%20v8/builds/3097/steps/test_1/logs/stdio

            Assignee:
            siddharth.singh@10gen.com siddharth.singh@10gen.com
            Reporter:
            ian@mongodb.com Ian Whalen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: