[SERVER-44580] Crash of 3.6.11 Created: 12/Nov/19 Updated: 18/Dec/19 Resolved: 18/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.6.11 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Nick Hristov | Assignee: | Eric Sedor |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | I do not have much additional information to add. There was no special or unusual activity against the server when the crash happened.
|
| Participants: |
| Description |
|
Version:
Backtrace:
|
| Comments |
| Comment by Eric Sedor [ 18/Dec/19 ] |
|
Understood nick@turvo.com; if you have trouble again please don't hesitate to comment here or open a new ticket. Thanks, |
| Comment by Nick Hristov [ 09/Dec/19 ] |
|
I am pretty sure its gone by now. |
| Comment by Eric Sedor [ 06/Dec/19 ] |
|
We understand the information might not be available, but we would need it to potentially diagnose the problem. Are you able to provide the above? Thanks, |
| Comment by Eric Sedor [ 15/Nov/19 ] |
|
I've created a secure upload portal for you. Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time. Can you please upload the mongodb log file leading up to the crash? The log lines preceding the backtrace may provide additional useful information. Would you please also archive (tar or zip) the $dbpath/diagnostic.data directory (the contents are described here) and attach it to this ticket? Thank you in advance. |