[SERVER-7465] Crash on the master while creating a replicaset Created: 25/Oct/12 Updated: 19/Mar/13 Resolved: 12/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ran Tavory | Assignee: | Michael Grundy |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
$ uname -a |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
I used a single mongodb server and then wanted to create a replicaset to improve durability. Created a secondary and an arbiter. ) wait.... And then out of nowhere, the master node sees: 0xade6e1 0x5582d9 0x558862 0x7f3b3ce47c60 0x7f3b3c185bf6 0x580ee5 0x94e796 0x94227e 0x6b26b9 0xb5ba7d 0xb5d052 0x56fa52 0x5dbf11 0x7f3b3ce3ed8c 0x7f3b3c1e104d This happend a few times during the initial sync process. The sync isn't over, it's still running... On another set of mongodb servers I did exactly the same, but there it went smoothly and the replicaset was created successfully. I'm still running the faulting server in hope that it would finish its replication to the secondary (it'll take a few hours) but anyway, the crash itself is bad enough to report... |
| Comments |
| Comment by Ran Tavory [ 11/Mar/13 ] |
|
Hi Mike, sorry I don't work there anymore... – |
| Comment by Michael Grundy [ 11/Mar/13 ] |
|
Hi - Have you seen any recurrences of this issue? I noticed you were running version 2.2.0 when you initially posted this. We've fixed some critical bugs in 2.2.0 since then and recommend you update to the latest stable release of 2.2, which is 2.2.3, as soon as possible. If you are still seeing this issue with 2.2.3, I'd recommend posting on one of our free support channels. Please include larger chunks of the log before and after the stack trace. Filing tickets under the SERVER project is not the best way to get visibility for issues you encounter, as we use this project for tracking bugs and feature requests. If you have a support contract with 10gen, then filing commercial support tickets is your best option. If not, the 10gen development and support teams actively monitor posts to stackoverflow (http://stackoverflow.com/questions/tagged/mongodb) and to the mongo google group (https://groups.google.com/forum/?fromgroups#!forum/mongodb-user) Mike |