[SERVER-7882] Segmentation Fault in mongod Created: 08/Dec/12 Updated: 10/Dec/14 Resolved: 18/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Roy Smith | Assignee: | Thomas Rueckstiess |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux gilbert 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux |
||
| Attachments: |
|
| Operating System: | ALL |
| Steps To Reproduce: | Unknown |
| Participants: |
| Description |
|
In the past two days, I've gotten two segfaults from mongod. I'm attaching the stack dumps from the mongod log file. This is on a development machine which has been stable for quite a while. I believe the last database maintenance I did was to install 2.2.0, which looks like it must have been the end of August, and I've been running fine since then. I was planning to upgrade to 2.2.2 soon, but I'll hold off on that for the moment. |
| Comments |
| Comment by Stennie Steneker (Inactive) [ 18/Mar/14 ] | |
|
Hi Roy, I noticed this issue has been languishing for a long time without a public update. It looks like there was no conclusive determination from the log files you provided. Given the elapsed time it no longer seems prudent to investigate, so I'm going to close this as Incomplete. Regards, | |
| Comment by Roy Smith [ 18/Dec/12 ] | |
|
OK, I just uploaded mongodb.log.segfault.gz. That file covers both events. These happened on a single-node configuration on a development system. No sharding, no replicas. The database had been restored from a dump of our production instance, which is a replica set (but still no sharding). | |
| Comment by Thomas Rueckstiess [ 18/Dec/12 ] | |
|
Hi Roy, Could you please upload the full log file for the 7th and 8th of Dec to our servers? We can't diagnose the problem without any context. Please compress your logs and upload them to our secure customer site. You can do this using the following command:
Substitute <filename> with the name of the file(s) you want to upload. Note the colon ':' at the end of the command. When you are prompted for a password, please just press ENTER. Also, do you have a sharded environment or just a replica set? Was that particular node a primary or secondary? And were other nodes affected as well? Regards, |