-
Type: Bug
-
Resolution: Incomplete
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.2.1
-
Component/s: WiredTiger
-
Labels:None
-
ALL
After a power outage, the node is not booting up
istics=(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),
2019-10-03T11:33:37.224+0300 E STORAGE [initandlisten] WiredTiger (-31802) [1570091617:224206][8947:0x7f4131546dc0], file:WiredTiger.wt, connection: unable to read root page from file:WiredTiger.wt: WT_ERROR: non-specific WiredTiger error
2019-10-03T11:33:37.224+0300 E STORAGE [initandlisten] WiredTiger (0) [1570091617:224309][8947:0x7f4131546dc0], file:WiredTiger.wt, connection: WiredTiger has failed to open its metadata
2019-10-03T11:33:37.224+0300 E STORAGE [initandlisten] WiredTiger (0) [1570091617:224340][8947:0x7f4131546dc0], file:WiredTiger.wt, connection: This may be due to the database files being encrypted, being from an older version or due to corruption on disk
2019-10-03T11:33:37.224+0300 E STORAGE [initandlisten] WiredTiger (0) [1570091617:224374][8947:0x7f4131546dc0], file:WiredTiger.wt, connection: You should confirm that you have opened the database with the correct options including all encryption and compression options
2019-10-03T11:33:37.225+0300 I - [initandlisten] Assertion: 28718:-31802: WT_ERROR: non-specific WiredTiger error
2019-10-03T11:33:37.225+0300 I STORAGE [initandlisten] exception in initAndListen: 28718 -31802: WT_ERROR: non-specific WiredTiger error, terminating
2019-10-03T11:33:37.225+0300 I CONTROL [initandlisten] dbexit: rc: 100
I saw very old tickets where you attached WiredTiger.wt and WiredTiger.turtle
I attach those two, I saw the support team answer with a fixed version of the files