[SERVER-10331] Mongodb SEGFAULTS with a null pointer Created: 25/Jul/13 Updated: 02/Aug/13 Resolved: 25/Jul/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency, Stability |
| Affects Version/s: | 2.2.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Blocker - P1 |
| Reporter: | Jim | Assignee: | Michael Grundy |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | crash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Centos 6.2, pymongo-2.1.1-1, pulp-2.1.3-1 |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | Linux | ||||||||
| Steps To Reproduce: |
-------------------------------------
Wed Jul 24 10:25:24 0x59e416 0x47adbd 0x3a41032900 |
||||||||
| Participants: | |||||||||
| Description |
|
I am trying to use pulp, which a program that manages package repositories, and uses mongodb as a backend. However, it has been causing mongodb to segfault. https://bugzilla.redhat.com/show_bug.cgi?id=986070 http://pastebin.com/VgfHZj0q (the file being piped in just contains "db.queued_calls.drop();" ). The second link in particular seems to point the finger at mongo. Pulp has a db purging call queued, and on its startup it segfaults mongodb, which itself complains about a null pointer, and what appears to a threading problem (as soon as anything thread but the first does anything it gets said null pointer) |
| Comments |
| Comment by Jim [ 25/Jul/13 ] |
|
Thanks for the help; its good to have confirmation that this is a known issue that was indeed fixed. |
| Comment by Jim [ 25/Jul/13 ] |
|
Also, after opening this case I found this bug: https://jira.mongodb.org/browse/SERVER-9014, of which this looks as though it may be a duplicate. I upgraded one of my servers to 2.4.5, and it hasnt segfaulted in the ~20 min since... |
| Comment by Michael Grundy [ 25/Jul/13 ] |
|
Hi Jim - Glad you found the pattern, that is fixed in 2.4.2, but we recommend you update to the latest, which is currently 2.4.5 and available at http://downloads.mongodb.org Thanks! |
| Comment by Jim [ 25/Jul/13 ] |
|
Full log from a run of this |
| Comment by Michael Grundy [ 25/Jul/13 ] |
|
Could you post the complete mongod log from your test case? The backtrace looks like it is from the mongo shell, not mongod. Thanks! |