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

WiredTiger fails to start after trying to upgrade from 3.2.1 to 3.2.2

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: 3.2.3
    • Fix Version/s: None
    • Component/s: WiredTiger
    • Labels:
      None
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      apt-get update && apt-get upgrade && apt-get dist-upgrade
      press 'Y'

      MongoDB data directory is attached - since it contains only test data there is no need to keep it secret.

      Show
      apt-get update && apt-get upgrade && apt-get dist-upgrade press 'Y' MongoDB data directory is attached - since it contains only test data there is no need to keep it secret.

      Description

      After upgrading MongoDB to version 3.2.2 the database fails to start with the following error:

      2016-02-17T08:55:21.482+0100 I CONTROL  [main] ***** SERVER RESTARTED *****
      2016-02-17T08:55:21.492+0100 I CONTROL  [initandlisten] MongoDB starting : pid=31130 port=27017 dbpath=/var/lib/mongodb 64-bit host=srv05
      2016-02-17T08:55:21.492+0100 I CONTROL  [initandlisten] db version v3.2.2
      2016-02-17T08:55:21.492+0100 I CONTROL  [initandlisten] git version: 6e71d0d568e134c029203593b00a0103e7cdf30b
      2016-02-17T08:55:21.492+0100 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1f 6 Jan 2014
      2016-02-17T08:55:21.492+0100 I CONTROL  [initandlisten] allocator: tcmalloc
      2016-02-17T08:55:21.492+0100 I CONTROL  [initandlisten] modules: none
      2016-02-17T08:55:21.492+0100 I CONTROL  [initandlisten] build environment:
      2016-02-17T08:55:21.492+0100 I CONTROL  [initandlisten]     distmod: debian71
      2016-02-17T08:55:21.492+0100 I CONTROL  [initandlisten]     distarch: x86_64
      2016-02-17T08:55:21.492+0100 I CONTROL  [initandlisten]     target_arch: x86_64
      2016-02-17T08:55:21.492+0100 I CONTROL  [initandlisten] options: { config: "/etc/mongod.conf", net: { bindIp: "127.0.0.1,192.168.2.83", port: 27017 }, processManagement: { fork: false }, setParameter: { enableLocalhostAuthBypass: "true" }, storage: { dbPath: "/var/lib/mongodb", engine: "wiredTiger", journal: { enabled: true } }, systemLog: { destination: "file", logAppend: true, path: "/var/log/mongodb/mongodb.log" } }
      2016-02-17T08:55:21.523+0100 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=4G,session_max=20000,eviction=(threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),checkpoint=(wait=60,log_size=2GB),statistics_log=(wait=0),
      2016-02-17T08:55:22.186+0100 E STORAGE  [initandlisten] WiredTiger (22) [1455695722:186444][31130:0x7f13f13bcd00], WT_SESSION.create: table:_mdb_catalog: does not match existing configuration: Invalid argument
      2016-02-17T08:55:22.186+0100 I -        [initandlisten] Fatal Assertion 28562
      2016-02-17T08:55:22.186+0100 I -        [initandlisten]
       
      ***aborting after fassert() failure
      

      Downgrading to 3.2.1 or 3.2.0 did NOT fix it.
      Happened only on our Ubuntu (Test) server, not on our Debian (Development) servers - the latter ones may have had their databases dropped more recently than the Ubuntu one.

        Attachments

        1. mongod.conf
          0.3 kB
        2. mongodb.tar.gz
          135.20 MB

          Issue Links

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: