[SERVER-37710] Can not start the server Created: 23/Oct/18  Updated: 23/Oct/18  Resolved: 23/Oct/18

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

Type: Bug Priority: Major - P3
Reporter: Danny Assignee: Danny Hatcher (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

2018-10-23T11:01:33.173+0800 I CONTROL [initandlisten] MongoDB starting : pid=10234 port=55050 dbpath=/data/mongodb32/data 64-bit host=iZ23fzysy64Z
2018-10-23T11:01:33.173+0800 I CONTROL [initandlisten] db version v3.2.10
2018-10-23T11:01:33.173+0800 I CONTROL [initandlisten] git version: 79d9b3ab5ce20f51c272b4411202710a082d0317
2018-10-23T11:01:33.173+0800 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.1e-fips 11 Feb 2013
2018-10-23T11:01:33.173+0800 I CONTROL [initandlisten] allocator: tcmalloc
2018-10-23T11:01:33.173+0800 I CONTROL [initandlisten] modules: none
2018-10-23T11:01:33.173+0800 I CONTROL [initandlisten] build environment:
2018-10-23T11:01:33.173+0800 I CONTROL [initandlisten] distmod: rhel62
2018-10-23T11:01:33.173+0800 I CONTROL [initandlisten] distarch: x86_64
2018-10-23T11:01:33.173+0800 I CONTROL [initandlisten] target_arch: x86_64
2018-10-23T11:01:33.173+0800 I CONTROL [initandlisten] options: { config: "/data/mongodb32/mongod.conf", net:

{ bindIp: "0.0.0.0", port: 55050 }

, processManagement: { fork: true, pidFilePath: "/data/mongodb32/mongod.pid" }, security: { authorization: "enabled" }, storage: { dbPath: "/data/mongodb32/data" }, systemLog: { destination: "file", path: "/data/mongodb32/log/mongod.log", quiet: false, verbosity: 1 } }
2018-10-23T11:01:33.173+0800 D NETWORK [initandlisten] fd limit hard:100000 soft:100000 max conn: 80000
2018-10-23T11:01:33.192+0800 I - [initandlisten] Detected data files in /data/mongodb32/data created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2018-10-23T11:01:33.192+0800 I STORAGE [initandlisten] wiredtiger_open config: create,cache_size=8G,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),
2018-10-23T11:01:33.220+0800 E STORAGE [initandlisten] WiredTiger (-31802) [1540263693:220964][10234:0x7f337487fd40], txn-recover: unsupported WiredTiger file version: this build only supports major/minor versions up to 1/0, and the file is version 2/0: WT_ERROR: non-specific WiredTiger error
2018-10-23T11:01:33.221+0800 E STORAGE [initandlisten] WiredTiger (0) [1540263693:221034][10234:0x7f337487fd40], txn-recover: WiredTiger is unable to read the recovery log.
2018-10-23T11:01:33.221+0800 E STORAGE [initandlisten] WiredTiger (0) [1540263693:221057][10234:0x7f337487fd40], txn-recover: This may be due to the log files being encrypted, being from an older version or due to corruption on disk
2018-10-23T11:01:33.221+0800 E STORAGE [initandlisten] WiredTiger (0) [1540263693:221079][10234:0x7f337487fd40], txn-recover: You should confirm that you have opened the database with the correct options including all encryption and compression options
2018-10-23T11:01:33.221+0800 E STORAGE [initandlisten] WiredTiger (-31802) [1540263693:221105][10234:0x7f337487fd40], txn-recover: Recovery failed: WT_ERROR: non-specific WiredTiger error
2018-10-23T11:01:33.226+0800 I - [initandlisten] Assertion: 28595:-31802: WT_ERROR: non-specific WiredTiger error
2018-10-23T11:01:33.226+0800 I STORAGE [initandlisten] exception in initAndListen: 28595 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2018-10-23T11:01:33.226+0800 I CONTROL [initandlisten] dbexit: rc: 100



 Comments   
Comment by Danny Hatcher (Inactive) [ 23/Oct/18 ]

Hello Danny,

This error is generally due to an improper downgrade. Please see SERVER-31575 as an example. Can you confirm if this is your situation? You should not experience this problem against a fresh database install or when following proper downgrade procedure regarding Feature Compatibility Version.

Please also note that MongoDB 3.2 has reached end-of-life as of September so we recommend upgrading to 3.4, 3.6, or 4.0.

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