[SERVER-50601] server abort, crash Created: 28/Aug/20 Updated: 27/Oct/23 Resolved: 03/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, WiredTiger |
| Affects Version/s: | 3.6.18 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | sergio d | Assignee: | Dmitry Agranat |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | FA_50853 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
| Comments |
| Comment by sergio d [ 03/Sep/20 ] |
|
Thank you, do you have any reference documents on how to resolve this HW issue? |
| Comment by Dmitry Agranat [ 03/Sep/20 ] |
|
Hi sergioduarte.dba@gmail.com it looks like you've attached data from another member, which did not experienced this issue. In any case, Fatal Assertion 50853 indicates a HW issue which you'll need to address. After the HW issue is addressed, you can resync this node from another healthy member. |
| Comment by sergio d [ 02/Sep/20 ] |
|
Hi Dima, Done. The file /var/ log/dmesg does not exist Regards, |
| Comment by Dmitry Agranat [ 30/Aug/20 ] |
|
Hi sergioduarte.dba@gmail.com, Would you please archive (tar or zip) the full mongod.log files and the $dbpath/diagnostic.data directory (the contents are described here) and upload them to this support uploader location? Also, please upload the syslog and the output from the /var/log/dmesg. Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time. Thanks, |