[SERVER-25730] Mongodb 3.2.X MMapv1 crash Created: 22/Aug/16 Updated: 06/Sep/16 Resolved: 06/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.2.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dharshan Rangegowda | Assignee: | Kelsey Schubert |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
My MongoDB 3.2.x mmapv1 server crashed with the following stack trace. I have xxxed out some of the collection names. The server is running on AWS and there don't appear to be any AWS or EBS issues. 2016-08-22T16:57:32.425+0000 I ACCESS [conn39] Successfully authenticated as principal admin on admin } on: { ts: Timestamp 1471885053000|1, t: 0, h: 314096183130207904, v: 2, op: "i", ns: "xxxxxxxxx.feedback_responses", o: { _id: ObjectId('57bb2efd4543 324038840000'), AttorneyFeedback: "insufficient_time", Comments: "", AttorneyId: ObjectId('578817ef454332332c630100'), JobId: ObjectId('57b2179345433250e9790000'), ClientId: ObjectId('578818 17454332332cf00100'), ModifiedDateTime: new Date(1471885053506), CreatedDateTime: new Date(1471885053506) } } ***aborting after fassert() failure |
| Comments |
| Comment by Kelsey Schubert [ 06/Sep/16 ] | |
|
We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, | |
| Comment by Kelsey Schubert [ 23/Aug/16 ] | |
|
Thank you for opening this ticket. Please answer the following questions so we can continue to investigate this issue.
I have created a secure upload portal for you to use. Files uploaded to this portal will be visible only to MongoDB employees investigating this issue and are routinely deleted after some time. Thank you for your help, |