[SERVER-39389] --repair crash mongod when repair work almost done Created: 06/Feb/19  Updated: 06/Feb/19  Resolved: 06/Feb/19

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

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

Attachments: Text File mongod.log    
Issue Links:
Duplicate
duplicates SERVER-38177 Repair with bind_ip results in a null... Closed
Operating System: ALL
Steps To Reproduce:

1 Prepare a clean standalone mongod server.

2 Edit mongod.cfg, add "bindIp" to it, just like this:

net:
  bindIp: 127.0.0.1

3 run command line:

mongod.exe --config mongod.cfg --repair

4 When repair works almost done, mongod crashed. the logs i had attach to attachment. according to the logs, the transport layer cause this problem.

 

And i find out that, to resolve the problem, should delete "bindIp" from mongod.cfg,just like this:

net:
#  bindIp: 127.0.0.1

Then run command line to repair database "mongod.exe --config mongod.cfg --repair"

After repair database files, add "bindIp" to mongod.cfg.

Start mongod normally with command line "mongod.exe --config mongod.cfg"

It work successfully.

Participants:

 Description   

My database with wiredtiger storage engine occur some error when suddenly power down.

So, i start mongod with --repair in command line.

When repair works almost done, mongod crash with some transport layer error.

This problem occur under windows version mongodb-win32-x86_64-2008plus-ssl-4.0.5



 Comments   
Comment by Danny Hatcher (Inactive) [ 06/Feb/19 ]

Hello,

You are encountering SERVER-38177. This is a known issue that has been fixed in MongoDB 4.0.6. As 4.0.6 has not yet been released, the workaround you found is the recommended process; simply remove the bindIp value from the config as it has no use on a repairing node regardless.

I will close this ticket as a duplicate of SERVER-38177.

Thank you,

Danny

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