[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: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
We encountered this issue since 3.2.8. 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. 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 Kind regards, |
| 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, |