[SERVER-46269] WT_ERROR: non-specific WiredTiger error Created: 20/Feb/20  Updated: 06/Dec/22  Resolved: 24/Feb/20

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

Type: Bug Priority: Major - P3
Reporter: Lucky La Torre Assignee: Backlog - Triage Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive wiredtigerfiles.zip    
Assigned Teams:
Server Triage
Operating System: ALL
Steps To Reproduce:
  1. snapshot of an ebs thats used in a different production database
  2. snapshot was created as a volume
  3. same versions, 3.4.24

 

mongod.conf

[root@ip-172-17-0-111 data]# cat /etc/mongod.conf
# mongod.conf# for documentation of all options, see:
#   http://docs.mongodb.org/manual/reference/configuration-options/# where to write logging data.
systemLog:
  destination: file
  logAppend: true
  path: /var/log/mongodb/mongod.log# Where and how to store data.
storage:
  dbPath: /var/lib/mongo/data
  journal:
    enabled: true
#  engine:
#  mmapv1:
#  wiredTiger:# how the process runs
processManagement:
  fork: true  # fork and run in background
  pidFilePath: /var/run/mongodb/mongod.pid  # location of pidfile# network interfaces
net:
  port: 27017
  bindIp: 0.0.0.0  # Listen to local interface only, comment to listen on all interfaces.

Participants:

 Description   

Hi Mongo Team

 

Can someone help me in trying to fix my mongo wiredtiger? 

[root@ip-172-17-0-111 data]#  mongod --repair   --dbpath=/var/lib/mongo/data --storageEngine wiredTiger
2020-02-20T05:13:41.166+0000 I CONTROL  [initandlisten] MongoDB starting : pid=717 port=27017 dbpath=/var/lib/mongo/data 64-bit host=ip-172-17-0-111.ap-northeast-2.compute.internal
2020-02-20T05:13:41.166+0000 I CONTROL  [initandlisten] db version v3.4.24
2020-02-20T05:13:41.166+0000 I CONTROL  [initandlisten] git version: 865b4f6a96d0f5425e39a18337105f33e8db504d
2020-02-20T05:13:41.166+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.0-fips 29 Mar 2010
2020-02-20T05:13:41.166+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2020-02-20T05:13:41.166+0000 I CONTROL  [initandlisten] modules: none
2020-02-20T05:13:41.166+0000 I CONTROL  [initandlisten] build environment:
2020-02-20T05:13:41.166+0000 I CONTROL  [initandlisten]     distmod: amazon
2020-02-20T05:13:41.166+0000 I CONTROL  [initandlisten]     distarch: x86_64
2020-02-20T05:13:41.166+0000 I CONTROL  [initandlisten]     target_arch: x86_64
2020-02-20T05:13:41.166+0000 I CONTROL  [initandlisten] options: { repair: true, storage: { dbPath: "/var/lib/mongo/data", engine: "wiredTiger" } }
2020-02-20T05:13:41.166+0000 W -        [initandlisten] Detected unclean shutdown - /var/lib/mongo/data/mongod.lock is not empty.
2020-02-20T05:13:41.188+0000 W STORAGE  [initandlisten] Recovering data from the last clean checkpoint.
2020-02-20T05:13:41.188+0000 I STORAGE  [initandlisten]
2020-02-20T05:13:41.188+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2020-02-20T05:13:41.188+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
2020-02-20T05:13:41.188+0000 I STORAGE  [initandlisten] Detected WT journal files.  Running recovery from last checkpoint.
2020-02-20T05:13:41.188+0000 I STORAGE  [initandlisten] journal to nojournal transition config: create,cache_size=7507M,session_max=20000,eviction=(threads_min=4,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),verbose=(recovery_progress),
2020-02-20T05:13:41.204+0000 E STORAGE  [initandlisten] WiredTiger error (-31802) [1582175621:204286][717:0x7f674fd20580], txn-recover: unsupported WiredTiger file version: this build  only supports major/minor versions up to 1/0,  and the file is version 3/0: WT_ERROR: non-specific WiredTiger error
2020-02-20T05:13:41.204+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1582175621:204336][717:0x7f674fd20580], txn-recover: WiredTiger is unable to read the recovery log.
2020-02-20T05:13:41.204+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1582175621:204363][717:0x7f674fd20580], txn-recover: This may be due to the log files being encrypted, being from an older version or due to corruption on disk
2020-02-20T05:13:41.204+0000 E STORAGE  [initandlisten] WiredTiger error (0) [1582175621:204380][717:0x7f674fd20580], txn-recover: You should confirm that you have opened the database with the correct options including all encryption and compression options
2020-02-20T05:13:41.204+0000 E STORAGE  [initandlisten] WiredTiger error (-31802) [1582175621:204401][717:0x7f674fd20580], txn-recover: Recovery failed: WT_ERROR: non-specific WiredTiger error
2020-02-20T05:13:41.206+0000 I -        [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error src/mongo/db/storage/wiredtiger/wiredtiger_kv_engine.cpp 254
2020-02-20T05:13:41.206+0000 I STORAGE  [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2020-02-20T05:13:41.206+0000 I NETWORK  [initandlisten] shutdown: going to close listening sockets...
2020-02-20T05:13:41.206+0000 I NETWORK  [initandlisten] removing socket file: /tmp/mongodb-27017.sock
2020-02-20T05:13:41.206+0000 I NETWORK  [initandlisten] shutdown: going to flush diaglog...
2020-02-20T05:13:41.206+0000 I CONTROL  [initandlisten] now exiting
2020-02-20T05:13:41.206+0000 I CONTROL  [initandlisten] shutting down with code:100



 Comments   
Comment by Carl Champain (Inactive) [ 24/Feb/20 ]

Hi lucky.latorre@lenddo.com,

MongoDB 3.4 only understands WT log format version 1. WT log format version 3 was introduced in MongoDB 4.0. So, it appears that the data files are on a higher version than the MongoDB binary. From the logs you provided:

this build only supports major/minor versions up to 1/0, and the file is version 3/0

That said, MongoDB 3.4 is already end-of-lifed, which means it is unsupported by us. We strongly recommend you upgrade to a supported version. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag. I will now close this ticket.

Thanks,

Carl

Generated at Thu Feb 08 05:10:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.