-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 3.2.10
-
Component/s: None
-
None
-
ALL
-
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
We run MongoDB 3.2 in an OpenShift cluster using the official RedHat pod (hence the not quite up-to-date version). For reasons unknown yet, the pod failed to stop cleanly, corrupting the WiredTiger data files.
The error is basically the same as described in SERVER-23346, SERVER-27777, SERVER-25770, SERVER-28242 and possibly others. However, none of the tickets we found includes instructions on how to fix the problem ourselves.
We have tried to run an image with 3.6, that did not help. When running a 4.0 image, the output is more and it tries to repair, but only to fail with "** IMPORTANT: UPGRADE PROBLEM: The data files need to be fully upgraded to version 3.6 before attempting an upgrade to 4.0".
A file-based restore does not help either, mongodb fails to start with checksum errors. Our customer did not create dumps.
Can you help us? The database is currently down...
Reading from the other logs, I have attached some files in order to get repair files. Please indicate if those are enough.
Best Regards
Christian Cremer