[SERVER-25577] Segmentation fault when accessing index information Created: 12/Aug/16 Updated: 04/Oct/16 Resolved: 03/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | 2.6.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Maciej Kwiatkowski | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: |
|
| Participants: |
| Description |
|
I have installed MongoDB 2.6.8 on up-to-date Gentoo server, then I have started playing around because it is my first time with MongoDB. Everything went smooth until I wanted to create a compound index. Segmentation fault occured. For actions described above I was using mongo CLI client. Stack trace below:
|
| Comments |
| Comment by Kelsey Schubert [ 04/Oct/16 ] |
|
Hi mkwiatkowski, Thanks for the update. This segmentation faults occurs within v8, which was replaced with SpiderMonkey in MongoDB 3.2. So we are confident that this issue will be resolved in MongoDB 3.2. As you may know, MongoDB 2.6 will be no longer supported at the end of this month. Therefore, this issue will not be corrected in MongoDB 2.6. Thank you for your understanding, |
| Comment by Maciej Kwiatkowski [ 03/Oct/16 ] |
|
Thomas, I'm sorry for delayed reply. |
| Comment by Kelsey Schubert [ 03/Oct/16 ] |
|
Hi mkwiatkowski, Since we haven't heard back from you, I assume that upgrading to the latest version of MongoDB resolved this issue. If that is not the case, please let us know. Thank you, |
| Comment by Kelsey Schubert [ 06/Sep/16 ] |
|
Hi mkwiatkowski, Would you please upgrade to the latest version of MongoDB (3.2.9) and confirm that the issue is resolved? Thank you, |
| Comment by Maciej Kwiatkowski [ 12/Aug/16 ] |
|
Ramon, I have attached system log, but I'm not sure if this is what you need when saying "logs for this node". Actually nothing is being logged when segmentation fault happens, it just quits mongo shell. |
| Comment by Maciej Kwiatkowski [ 12/Aug/16 ] |
|
mongodb daemon log |
| Comment by Ramon Fernandez Marina [ 12/Aug/16 ] |
|
mkwiatkowski, can you please upload the logs for this node from the last restart until you got this error? Thanks, |