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

dur/md5.js failed on V2.4 Windows 64-bit 2008R2+

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Cannot Reproduce
    • None
    • None
    • Testing Infrastructure
    • V2.4 Windows 64-bit 2008R2+
    • ALL

    Description

      This is an odd one...

      V2.4 Windows 64-bit 2008R2+ Build #92 (Tue Aug 6, rev 3fc69c4aa)
      http://buildlogs.mongodb.org/V2.4%20Windows%2064-bit%202008R2%2B/builds/92/test/durability/md5.js

      dur_md5 step 6 run mongod again recovery should fail
       
      ...
       
      FAIL md5.js expected mongod to fail but didn't? mongod exitCode: -529697949
      2013-08-06 11:54:40 EDT	
      assert failed
      Error: Printing Stack Trace
          at printStackTrace (src/mongo/shell/utils.js:37:15)
          at doassert (src/mongo/shell/assert.js:6:5)
          at assert (src/mongo/shell/assert.js:14:5)
          at D:\slave\Windows_64bit_2008R2+_V2.4\mongo\jstests\dur\md5.js:92:5
      Tue Aug 06 11:54:40.378 assert failed at src/mongo/shell/assert.js:7
      failed to load: D:\slave\Windows_64bit_2008R2+_V2.4\mongo\jstests\dur\md5.js

      Well, that's what the test thinks. But in fact the mongod that it started on port 30002 DID fail.

       m30002| Tue Aug 06 11:54:35.761 [initandlisten] recover lsn: 0
       m30002| Tue Aug 06 11:54:35.761 [initandlisten] recover /data/db/dur_md5dur\journal\j._0
       m30002| Tue Aug 06 11:54:35.761 [initandlisten] JHeader::fileId=18416839699567025206
       m30002| Tue Aug 06 11:54:35.761 [initandlisten] couldn't uncompress journal section
       m30002| Tue Aug 06 11:54:35.761 [initandlisten] Assertion: 15874:couldn't uncompress journal section
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] mongod.exe    ...\src\mongo\util\stacktrace.cpp(167)                   mongo::printStackTrace+0x3e
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] mongod.exe    ...\src\mongo\util\assert_util.cpp(159)                  mongo::msgasserted+0xc1
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] mongod.exe    ...\src\mongo\db\dur_recover.cpp(117)                    mongo::dur::JournalSectionIterator::JournalSectionIterator+0xd4
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] mongod.exe    ...\src\mongo\db\dur_recover.cpp(380)                    mongo::dur::RecoveryJob::processSection+0x18e
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] mongod.exe    ...\src\mongo\db\dur_recover.cpp(473)                    mongo::dur::RecoveryJob::processFileBuffer+0x3c8
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] mongod.exe    ...\src\mongo\db\dur_recover.cpp(502)                    mongo::dur::RecoveryJob::processFile+0x324
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] mongod.exe    ...\src\mongo\db\dur_recover.cpp(517)                    mongo::dur::RecoveryJob::go+0x12b
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] mongod.exe    ...\src\mongo\db\dur_recover.cpp(556)                    mongo::dur::_recover+0x126
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] mongod.exe    ...\src\mongo\db\dur_recover.cpp(577)                    mongo::dur::recover+0xc0
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] mongod.exe    ...\src\mongo\db\dur.cpp(852)                            mongo::dur::startup+0x71
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] mongod.exe    ...\src\mongo\db\db.cpp(624)                             mongo::_initAndListen+0x88e
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] mongod.exe    ...\src\mongo\db\db.cpp(685)                             mongo::initAndListen+0x21
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] mongod.exe    ...\src\mongo\db\db.cpp(1297)                            mongoDbMain+0x165
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] mongod.exe    ...\src\mongo\db\db.cpp(729)                             main+0x9
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] mongod.exe    f:\dd\vctools\crt_bld\self_64_amd64\crt\src\crt0.c(278)  __tmainCRTStartup+0x13b
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] kernel32.dll                                                           BaseThreadInitThunk+0xd
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] dbexception during recovery: 15874 couldn't uncompress journal section
       m30002| Tue Aug 06 11:54:36.900 [initandlisten] exception in initAndListen: 15874 couldn't uncompress journal section, terminating
      2013-08-06 11:54:38 EDT	
       m30002| Tue Aug 06 11:54:36.900 dbexit: 

      I see above that the exit code is some huge negative number. Is that correct and expected, or a sign of something strange?

      Attachments

        Activity

          People

            Unassigned Unassigned
            matt.kangas Matt Kangas
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: