[SERVER-36974] this problem started After an unclean shutdown on my mac Created: 04/Sep/18  Updated: 06/Sep/18  Resolved: 06/Sep/18

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Sayon Palit [X] Assignee: Nick Brewer
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Operating System: ALL
Backport Requested:
v3.6
Participants:

 Description   

2018-09-04T14:49:09.818+0530 I CONTROL  [initandlisten] db version v3.6.7

2018-09-04T14:49:09.818+0530 I CONTROL  [initandlisten] git version: 2628472127e9f1826e02c665c1d93880a204075e

2018-09-04T14:49:09.818+0530 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.1.0h  27 Mar 2018

2018-09-04T14:49:09.818+0530 I CONTROL  [initandlisten] allocator: system

2018-09-04T14:49:09.818+0530 I CONTROL  [initandlisten] modules: none

2018-09-04T14:49:09.818+0530 I CONTROL  [initandlisten] build environment:

2018-09-04T14:49:09.818+0530 I CONTROL  [initandlisten]     distarch: x86_64

2018-09-04T14:49:09.818+0530 I CONTROL  [initandlisten]     target_arch: x86_64

2018-09-04T14:49:09.819+0530 I CONTROL  [initandlisten] options: { repair: true, storage:

{ dbPath: "/data/db" }

}

2018-09-04T14:49:09.820+0530 I -        [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.

2018-09-04T14:49:09.820+0530 I STORAGE  [initandlisten] Detected WT journal files.  Running recovery from last checkpoint.

2018-09-04T14:49:09.820+0530 I STORAGE  [initandlisten] journal to nojournal transition config: create,cache_size=3584M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),cache_cursors=false,compatibility=(release="3.0",require_max="3.0"),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),

2018-09-04T14:49:10.506+0530 E STORAGE  [initandlisten] WiredTiger error (-31802) [1536052750:506698][1951:0x7fff99697380], connection: Version incompatibility detected: unsupported WiredTiger file version: this build requires a maximum version of 2, and the file is version 3: WT_ERROR: non-specific WiredTiger error

2018-09-04T14:49:10.536+0530 E -        [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 397

2018-09-04T14:49:10.537+0530 I STORAGE  [initandlisten] exception in initAndListen: Location28718: -31802: WT_ERROR: non-specific WiredTiger error, terminating

2018-09-04T14:49:10.537+0530 I NETWORK  [initandlisten] shutdown: going to close listening sockets...

2018-09-04T14:49:10.537+0530 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-27017.sock

2018-09-04T14:49:10.542+0530 I CONTROL  [initandlisten] now exiting

2018-09-04T14:49:10.542+0530 I CONTROL  [initandlisten] shutting down with code:100



 Comments   
Comment by Nick Brewer [ 06/Sep/18 ]

Sayon_Palit No worries, glad you were able to get it working.

-Nick

Comment by Sayon Palit [X] [ 05/Sep/18 ]

Its fine I just deleted and re-installed it after removing all the exports
from .bash_profile file ,and its up and running now.
But thank you for looking into my issue so promptly Nick.
I hope I didn't waste too much of your time.

Thanks,
Sayon

Comment by Nick Brewer [ 04/Sep/18 ]

Sayon_Palit Was MongoDB recently upgraded? I ask because, as this error states, there appears to be a compatibility issue:

2018-09-04T14:49:10.506+0530 E STORAGE  [initandlisten] WiredTiger error (-31802) [1536052750:506698][1951:0x7fff99697380], connection: Version incompatibility detected: unsupported WiredTiger file version: this build requires a maximum version of 2, and the file is version 3: WT_ERROR: non-specific WiredTiger error 

It would be useful to know:

  • What was the MongoDB version before the upgrade?
  • What process did you follow to perform the upgrade / did you follow a specific guide?

Thanks,
-Nick

Generated at Thu Feb 08 04:44:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.