[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: File mongodb.log    
Operating System: ALL
Steps To Reproduce:
  1. log in to database:
    $ mongo -u <username> -p <password> --authenticationDatabase admin
  2. switch to some user database:
    > use apidb
  3. try to list indices of a collection:
    > db.users.getIndices()
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.
Then I tried to create single-field index. Segmentation fault occured as well.
Finally, I tried to list indices of some user collection, which resulted in segmentation fault too.

For actions described above I was using mongo CLI client.

Stack trace below:

2016-08-12T15:13:37.524+0200 mongo got signal 11 (Segmentation fault), stack trace: 
2016-08-12T15:13:37.534+0200 0x7dec69 0x5e4619 0x7f509b26c3c0 0x9ca61c 0xa3e598 0xa3e5d4 0xa4395e 0x9d956b 0x9e4a81 0x9e4e85 0x8837c0 0x9a3d78 0x94003d 0x32ae44c06362 
 mongo(_ZN5mongo15printStackTraceERSo+0x39) [0x7dec69]
 mongo(_Z12quitAbruptlyi+0x119) [0x5e4619]
 /lib64/libc.so.6(+0x333c0) [0x7f509b26c3c0]
 mongo(_ZN2v88internal6String11WriteToFlatItEEvPS1_PT_ii+0x3bc) [0x9ca61c]
 mongo(_ZN2v88internal33GenericStringUtf16CharacterStream10FillBufferEjj+0x38) [0xa3e598]
 mongo(_ZN2v88internal28BufferedUtf16CharacterStream9ReadBlockEv+0x34) [0xa3e5d4]
 mongo(_ZN2v88internal7Scanner10InitializeEPNS0_20Utf16CharacterStreamE+0x5e) [0xa4395e]
 mongo(_ZN2v88internal6Parser9ParseLazyEPNS0_20Utf16CharacterStreamEPNS0_9ZoneScopeE+0x3b) [0x9d956b]
 mongo(_ZN2v88internal6Parser9ParseLazyEv+0x161) [0x9e4a81]
 mongo(_ZN2v88internal9ParserApi5ParseEPNS0_15CompilationInfoEi+0x205) [0x9e4e85]
 mongo(_ZN2v88internal8Compiler11CompileLazyEPNS0_15CompilationInfoE+0xf0) [0x8837c0]
 mongo(_ZN2v88internal10JSFunction11CompileLazyENS0_6HandleIS1_EENS0_18ClearExceptionFlagE+0x198) [0x9a3d78]
 mongo(_ZN2v88internal11CallIC_MissENS0_9ArgumentsEPNS0_7IsolateE+0x27d) [0x94003d]
 [0x32ae44c06362]



 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,
Thomas

Comment by Maciej Kwiatkowski [ 03/Oct/16 ]

Thomas, I'm sorry for delayed reply.
I could not upgrade the MongoDB at all, due to some linux distribution limits (Gentoo haven't marked the 3.* branch stable yet). Thus, I'm unable to check if upgrading fixes the problem. If this is the only way you can help - closing the issue is OK with me

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,
Thomas

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,
Thomas

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,
Ramón.

Generated at Thu Feb 08 04:09:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.