Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-5998

Multiple version incompatible error log strings

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.2.0
    • Component/s: None
    • None
    • 0
    • Storage - Ra 2020-04-20, Storage - Ra 2020-05-04

      WT-4127 added a common prefix (Version incompatibility detected:) to help MongoDB suppress benign startup messages due to trying different compatibility versions. However I'm seeing that early versions of 4.2 that don't understand log version 4 are generating the old-style log message:

      [js_test:disallow_44_to_426_to_424] 2020-04-09T11:40:58.189-0400 d20020| 2020-04-09T11:40:58.189-0400 E  STORAGE  [initandlisten] WiredTiger error (-31802) [1586446858:189094][6455:0x7fe418334b00], connection: __log_open_verify, 928: unsupported WiredTiger file version: this build only supports versions up to 3, and the file is version 4: WT_ERROR: non-specific WiredTiger error Raw: [1586446858:189094][6455:0x7fe418334b00], connection: __log_open_verify, 928: unsupported WiredTiger file version: this build only supports versions up to 3, and the file is version 4: WT_ERROR: non-specific WiredTiger error
      

            Assignee:
            alex.cameron@mongodb.com Alex Cameron (Inactive)
            Reporter:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: