[SERVER-18614] mongodb keyFile between replicas throws Permission denied Created: 21/May/15 Updated: 21/May/15 Resolved: 21/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Replication, Security |
| Affects Version/s: | 3.0.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Juan Manuel Diego G | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: |
|
| Participants: |
| Description |
|
I have a single node ReplicaSet with auth activated, a root user and a keyFile I've created with this tutorial, I also have two more mongod processes in the same server in different ports (37017 and 47017) and the same replSet name, but when I try to add the secondaries in the mongo shell connected to PRIMARY with rs.add("172.31.48.41:37017") I get:
Then I went to the mongod process log of the PRIMARY and found out this:
And the log of the mongod that should become SECONDARY shows nothing, the last two lines are:
It's clear that I cannot rs.initiate() in this node because it will self vote to be PRIMARY and that would create a conflict, so the line that states "Did not find local replica set configuration document at startup" is to be ignores as far as I know. So I would think that the permission should be ok since I'm using the same key file in every mongod process and the replSet is the same in every config file, and that's all the tutorial states to be needed, but obviously something is missing. Any ideas? Is this a bug? |
| Comments |
| Comment by Ramon Fernandez Marina [ 21/May/15 ] | ||||||||||||||||||||||||||||||||||||||||||||
|
The replica set is configured to talk to 172.31.48.41, but accodring to netstat there's no mongod process listening there. Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. Regards, | ||||||||||||||||||||||||||||||||||||||||||||
| Comment by Juan Manuel Diego G [ 21/May/15 ] | ||||||||||||||||||||||||||||||||||||||||||||
|
I'm have an open shell to 37017, so... netstat | grep 37017 gives me:
There is no reference to mongod in the netstat output, but neither for the netstat | grep 27017 | ||||||||||||||||||||||||||||||||||||||||||||
| Comment by Ramon Fernandez Marina [ 21/May/15 ] | ||||||||||||||||||||||||||||||||||||||||||||
|
If I understand correctly there's no mongod listening on port 37017. Can you please check with netstat that there's a mongod running on that port? | ||||||||||||||||||||||||||||||||||||||||||||
| Comment by Juan Manuel Diego G [ 21/May/15 ] | ||||||||||||||||||||||||||||||||||||||||||||
|
Just to make sure, I'll include both config files: Primary process config file
Secondary process config file
|