[SERVER-32962] mongodb terminate unexpectedly when i dump the data Created: 29/Jan/18  Updated: 21/Mar/18  Resolved: 16/Feb/18

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

Type: Question Priority: Major - P3
Reporter: Cong Ma [X] Assignee: Mark Agarunov
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

windows 64-bit


Attachments: Text File MongoDB.log     File MongoDB.log.2018-01-28T01-49-15     File WiredTiger.lock     File WiredTiger.turtle     File WiredTiger.wt     PNG File clipboard.png     File repair-SERVER-32962.tar.gz    
Participants:

 Description   

I was dumping the database, it worked well. But after several minutes, the mongodb terminate unexpectedly and raised the exception, "read tcp 127.0.0.1:50872->127.0.0.1:80: wsarecv: An existing connection was forcibly closed by the remote host." At that time, I runed the shadowsocks in my PC, which is a VPN app. Maybe it affexted the normal work. Now, the mongodb cannot connect. it raised the exception,"1067".
I try several ways to solve it,but it failed. As like, reset the path and delete the file "mongodb.lock".
Can you help me to solve it? Thanks a lot!



 Comments   
Comment by Cong Ma [X] [ 23/Feb/18 ]

WiredTiger.turtle WiredTiger.wt MongoDB.log

Comment by Cong Ma [X] [ 23/Feb/18 ]

Thank you very much! I tried it, it works. But I encounter the problem again when I dumped the dataset, it happened in the same collection. I think maybe the reason of this problem happened is the destruction of this cllection, not the influence of the VPN. Can you help me to solve it again? I have upload the relevant files. Thank you!

Comment by Mark Agarunov [ 01/Feb/18 ]

Hello Smile_,

Thank you for providing these files. I've attached a repair attempt of the files you provided. Please extract these files and replace them in your $dbpath and let us know if it resolves the issue. If you are still seeing errors after replacing these files, please provide the complete logs from the affected node(s) so that we can further investigate.

The VPN was likely responsible for the initial error you saw, as it indicates that the connection was killed, likely due to the vpn reconfiguring network settings. The second error is unlikely to be related to the vpn and generally indicates inconsistencies in the underlying filesystem.

Thanks,
Mark

Comment by Cong Ma [X] [ 01/Feb/18 ]

WiredTiger.turtle WiredTiger.wt
Thanks for your help! Can you tell me the reason why it could be affected by the VPN?

Comment by Cong Ma [X] [ 01/Feb/18 ]

WiredTiger.turtle WiredTiger.wt
Thanks for your help! Can you tell me the reason why it could be affected by the VPN?

Comment by Mark Agarunov [ 30/Jan/18 ]

Hello Smile_,

Thank you for providing the logs. Looking over this, the error seems to indicate there may be inconsistencies in the database. So that we can attempt a repair, could you please provide the WiredTiger.turtle and WiredTiger.wt files from your $dbpath?

Thanks,
Mark

Comment by Cong Ma [X] [ 30/Jan/18 ]

thanks a lot!

Comment by Cong Ma [X] [ 30/Jan/18 ]

MongoDB.log.2018-01-28T01-49-15

Comment by Mark Agarunov [ 29/Jan/18 ]

Hello Smile_,

Thank you for the report. To get a better idea of why mongod is not starting for you, could you provide the complete output from attempting to start mongod, as well as the complete log files from all affected nodes? This should give some insight into this behavior.

Thanks,
Mark

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