[SERVER-50858] Mongo db crashed and generate many WiredTigerLog files Created: 10/Sep/20 Updated: 15/Mar/21 Resolved: 15/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.4.15 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Petr Dragunov | Assignee: | Eric Sedor |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
VMware host, windows server 2008 |
||
| Participants: |
| Description |
|
Hello colleuges,
We are use Mongo db version v3.4.15 on Windows server 2008.
Then mongod`s proccess trying restart again, again and are generate many WiredTigerLog files
repair, mongo_prune_js scriprt not help.
I realy not understand why db was crashed and what doing next, Do you have any idea? I very hope on you help. |
| Comments |
| Comment by Eric Sedor [ 15/Mar/21 ] | ||
|
Hi, We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, | ||
| Comment by Eric Sedor [ 19/Nov/20 ] | ||
|
We still need additional information. If this is still an issue for you, would you please provide the wiredTiger.wt and wiredTiger.turtle files so that we can attempt a metadata-only repair effort? Thanks, | ||
| Comment by Eric Sedor [ 21/Sep/20 ] | ||
|
First, can you please provide the full logs from the repair attempt? Second, please attach copies of the wiredTiger.wt and wiredTiger.turtle files and we can attempt a metadata-only repair effort using internal tools. Keep in mind that this repair effort may not be successful. Thanks, | ||
| Comment by Petr Dragunov [ 13/Sep/20 ] | ||
|
Thank for response >The ideal resolution is to perform a clean resync from an unaffected node in a replica set. Unfortanately it is not posible I did
and recieved of follow error and minidump file was also created
| ||
| Comment by Eric Sedor [ 11/Sep/20 ] | ||
|
MongoDB 3.4 reached end of life in January of this year, but we can try to help. Please make a complete copy of the database's $dbpath directory to safeguard so that you can work off of the current $dbpath. The ideal resolution is to perform a clean resync from an unaffected node in a replica set. If this is not an option can you try mongod --repair using the latest version of MongoDB (instead of --repair with MongoDB 3.4)? |