[SERVER-26868] mongodb 3.2.10 crash (Segmentation fault) Created: 01/Nov/16  Updated: 02/Nov/16  Resolved: 02/Nov/16

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

Type: Bug Priority: Critical - P2
Reporter: Rong Xia Assignee: Kelsey Schubert
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File stacktrace.txt    
Issue Links:
Duplicate
duplicates SERVER-24386 3.2.6 Segmentation Fault after a netw... Closed
Operating System: ALL
Participants:

 Description   

We encountered this issue since 3.2.8.
I noticed others were facing the similar issue, e.g https://jira.mongodb.org/browse/SERVER-25465
So, I waited for 3.2.10 stable release, hope it can fix the issue. But unfortunately, after upgrading to 3.2.10, we still see this issue.

There is no obvious pattern about which specific query caused crash. But it happens from time to time(mongodb run 1 or 2 days, then crash), especially when query load is heavy. Every time after crash, I need to manually restart the server. Manual restart is impractical for PROD environment.
Can you take a look at my attached log?

thanks



 Comments   
Comment by Kelsey Schubert [ 02/Nov/16 ]

Hi rongxia

Thanks for opening this ticket. I've examined the stack trace you have provided and identified that you are encountering SERVER-24386. We have been able to reproduce this issue and have a fix currently in code review. Please watch SERVER-24386 for updates on our progress to resolve this bug.

Kind regards,
Thomas

Comment by Rong Xia [ 01/Nov/16 ]

The log is about 2M size. Not big size. But the queries contain bank business information. How to avoid leaking sensitive information? Is there a safe way to pass you the log file?

thanks

Comment by Ramon Fernandez Marina [ 01/Nov/16 ]

Sorry you're running into this rongxia. Can you please upload the full logs for the affected node? The window from the last restart until you see this problem would be the most useful.

Thanks,
Ramón.

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