• Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Critical - P2 Critical - P2
    • 3.1.7
    • Affects Version/s: None
    • Component/s: None
    • None
    • Kernel Tools Iteration 7

      https://evergreen.mongodb.com/task_history/mongo-tools/legacy28?revision=3c38237c77f51d9d3c4edcc066e88d950739259c#/dumpauth.js=fail

      seems flaky but started failing at around "TOOLS-798 fixing old school single collection to standard output mode"

      log messages are a bit cryptic

      2015-06-26T20:18:13.046+0000 I -        shell: started program (sh3800):  mongodump.exe --db admin --authenticationDatabase=admin -u testuser -p testuser -h 127.0.0.1:31000 -vvv --collection tool_dumpauth.testcol --out -
       m31000| 2015-06-26T20:18:13.059+0000 I NETWORK  [initandlisten] connection accepted from 127.0.0.1:59573 #3 (2 connections now open)
       m31000| 2015-06-26T20:18:13.072+0000 I ACCESS   [conn3] Successfully authenticated as principal testuser on admin
      sh3800| 2015-06-26T20:18:13.073+0000	enqueued collection 'admin.tool_dumpauth.testcol'
      sh3800| 2015-06-26T20:18:13.075+0000	dump phase I: metadata, indexes, users, roles, version
      sh3800| 2015-06-26T20:18:13.075+0000	dump phase II: regular collections
      sh3800| 2015-06-26T20:18:13.075+0000	finalizing intent manager with longest task first prioritizer
      sh3800| 2015-06-26T20:18:13.075+0000	dumping with 4 job threads
      sh3800| 2015-06-26T20:18:13.075+0000	will listen for SIGTERM, SIGINT and SIGHUP
      sh3800| 2015-06-26T20:18:13.075+0000	starting dump routine with id=0
      sh3800| 2015-06-26T20:18:13.075+0000	starting dump routine with id=1
      sh3800| 2015-06-26T20:18:13.075+0000	ending dump routine with id=1, no more work to do
      sh3800| 2015-06-26T20:18:13.075+0000	starting dump routine with id=2
      sh3800| 2015-06-26T20:18:13.075+0000	ending dump routine with id=2, no more work to do
      sh3800| 2015-06-26T20:18:13.075+0000	starting dump routine with id=3
      sh3800| 2015-06-26T20:18:13.075+0000	ending dump routine with id=3, no more work to do
      sh3800| 2015-06-26T20:18:13.075+0000	writing admin.tool_dumpauth.testcol to stdout
      sh3800| 2015-06-26T20:18:13.075+0000		100 documents
      sh3800| WARNING: mongod wrote null bytes to output
      sh3800| WARNING: mongod wrote null bytes to output
      sh3800| WARNING: mongod wrote null bytes to output
      sh3800| WARNING: mongod wrote null bytes to output
      sh3800| WARNING: mongod wrote null bytes to output
      sh3800| WARNING: mongod wrote null bytes to output
      sh3800| WARNING: mongod wrote null bytes to output
      sh3800| WARNING: mongod wrote null bytes to output
      sh3800| WARNING: mongod wrote null bytes to output
      sh3800| WARNING: mongod wrote null bytes to output
      sh3800| !!!!!!!!!!
       m31000| 2015-06-26T20:18:13.076+0000 I NETWORK  [conn3] end connection 127.0.0.1:59573 (1 connection now open)
      assert: [1] != [0] are not equal : mongodump should succeed with authentication while using '--out'
      Error: [1] != [0] are not equal : mongodump should succeed with authentication while using '--out'
          at Error (<anonymous>)
          at doassert (src/mongo/shell/assert.js:11:14)
          at Function.assert.eq (src/mongo/shell/assert.js:38:5)
          at C:\data\mci\src\jstests\tool\dumpauth.js:41:8
      2015-06-26T20:18:13.078+0000 E QUERY    Error: [1] != [0] are not equal : mongodump should succeed with authentication while using '--out'
          at Error (<anonymous>)
          at doassert (src/mongo/shell/assert.js:11:14)
          at Function.assert.eq (src/mongo/shell/assert.js:38:5)
          at C:\data\mci\src\jstests\tool\dumpauth.js:41:8 at src/mongo/shell/assert.js:13
      failed to load: C:\data\mci\src\jstests\tool\dumpauth.js
      

            Assignee:
            gabriel.russell@mongodb.com Gabriel Russell (Inactive)
            Reporter:
            mikeo@mongodb.com Michael O'Brien
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: