[SERVER-3953] Cannot initialize set when using --keyFile Created: 26/Sep/11 Updated: 11/Jul/16 Resolved: 30/Sep/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Security |
| Affects Version/s: | 2.0.0 |
| Fix Version/s: | 2.0.1, 2.1.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kristina Chodorow (Inactive) | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
http://groups.google.com/group/mongodb-user/browse_thread/thread/db02517210b6a706 |
| Comments |
| Comment by Bernie David [ 25/Nov/11 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I just wiped the same node three times trying to reproduce the exact error and I couldn't, so the circumstances must have been more complex than just a wipe and resync. There were also mongodb restarts and attempts to rs.reconfig going on at the same time, so I won't open a new ticket till I can reproduce the problem. I will say that removing the --keyFile parameter (and then restoring after initial sync) was the fix to my previous problem, so I am probably only slightly crazy. Thanks for your quick response. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Eliot Horowitz (Inactive) [ 25/Nov/11 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
@bernie - can you open a new ticket with exactly what's happening in your case? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Bernie David [ 25/Nov/11 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I'm glad I found this bug because I was going bonkers trying to figure out why my sharded replica sets, protected by --keyFile (and --auth) would not allow a new node or a wiped node to initialize unless I removed --keyFile. Maybe I can bring in new members by a dump/restore and not through a rebuild sync. If I take away the keyfile setting to do an initialize – even for a minute – I am killing my shard. This is definitely not good. My version is 2.0.1 so the fix is not working for me, as far as I can tell. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by auto [ 09/Oct/11 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Author: {u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: check auth on _isSelf call | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kristina Chodorow (Inactive) [ 30/Sep/11 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Great! I built what I was pretty sure was the fix into the custom build, so glad that worked out. I'll request a backport to 2.0.1, watch this ticket to see if it makes it into 2.0.1 or just 2.1.0. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by auto [ 30/Sep/11 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Author: {u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: check auth on _isSelf call | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Rasitha Wijesinghe [ 30/Sep/11 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
FYI - tried updating my existing dev replica set (node by node without creating downtime) and that also worked well. I didn't test reading/writing data while the replica set was running both versions side by side, but at least from the logs and http interface, everything looked good. And within few minutes I was able to upgrade other two nodes in the replica set. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Rasitha Wijesinghe [ 30/Sep/11 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
That version is working correctly. Was able to create an admin user, add a second node and an arbiter to the replica set configuration. Everything seems to be working correctly. Looks like next week Thursday we should be able to get the release version of this? Thanks for getting to this quickly. Here's the log:
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kristina Chodorow (Inactive) [ 29/Sep/11 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Okay! That took forever to build. Can you try running rs.initiate() with this and paste the logs: http://downloads.mongodb.org/win32/mongodb-win32-x86_64-rsinit-latest.zip | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Rasitha Wijesinghe [ 29/Sep/11 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Yes, Win 64bit. Thx! | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kristina Chodorow (Inactive) [ 29/Sep/11 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Great, thanks! What environment are you on? Windows 64-bit? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Rasitha Wijesinghe [ 29/Sep/11 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
I wasn't using --bind_ip. Yes, I can try a custom build. Please let me know where I can download the files. Thanks! | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kristina Chodorow (Inactive) [ 29/Sep/11 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Are you using --bind_ip? Would you be willing to try a custom build? |