[SERVER-25701] Invalid query triggers stack trace Created: 19/Aug/16 Updated: 23/Aug/16 Resolved: 23/Aug/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.0.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charles Page [X] | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 14.04 |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | Unknown Just before the crash MongoDB logged: |
||||||||
| Participants: | |||||||||
| Description |
| Comments |
| Comment by Kelsey Schubert [ 23/Aug/16 ] | |
|
Hi Charles_CC, Thank for uploading the surrounding context. I see that mongod received an invalid query and produced a stack trace. Consequently, it closed the client connection and continued normal operation. I've updated the summary of this ticket to better reflect what transpired.
To clarify, a stack trace resulting from a failed check does not indicate that mongod's availability was compromised. In MongoDB 3.1.5, this check happens earlier and a comprehensive error message is printed instead of the stack trace ( For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group. Kind regards, | |
| Comment by Charles Page [X] [ 19/Aug/16 ] | |
|
I've attached the log file, the crash occurs at line 9168. | |
| Comment by Kelsey Schubert [ 19/Aug/16 ] | |
|
Hi Charles_CC, Would you please attach the complete logs including the time before and after this issue? Thank you, |