[SERVER-13858] couldn't initiate : can't find self in the replset config Created: 07/May/14  Updated: 10/Dec/14  Resolved: 27/Jun/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.7.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Durga Deep Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-4418 rs.initiate(); failed Closed
is related to SERVER-4784 replSetInitiate without arguments bre... Closed
Operating System: ALL
Steps To Reproduce:

1) Started mongodb with --replSet flag

2) Define a conf -
{ _id:"nstunnel", "version" : 1, members:[ {_id:0, host:"127.0.0.1:27517"}, {_id:1, host:"127.0.0.1:27617"}, {_id:2, host:"127.0.0.1:27717"} ] }

3) rs.initiate(conf)

Getting error..couldn't initiate : can't find self in the replset config

Participants:

 Description   

> conf = {   _id:"nstunnel",   "version" : 1,  members:[      {_id:0, host:"127.0.0.1:27517"},      {_id:1, host:"127.0.0.1:27617"},      {_id:2, host:"127.0.0.1:27717"}    ]  }
{
	"_id" : "nstunnel",
	"version" : 1,
	"members" : [
		{
			"_id" : 0,
			"host" : "127.0.0.1:27517"
		},
		{
			"_id" : 1,
			"host" : "127.0.0.1:27617"
		},
		{
			"_id" : 2,
			"host" : "127.0.0.1:27717"
		}
	]
}
> rs.initiate(conf);
{
	"ok" : 0,
	"errmsg" : "couldn't initiate : can't find self in the replset config"
}



 Comments   
Comment by Thomas Rueckstiess [ 27/Jun/14 ]

Hi Akka,

We haven't heard back from you so I'm assuming this is no longer an issue for you. If you'd like to follow up, feel free to re-open the ticket and provide the requested information.

Thanks,
Thomas

Comment by Ramon Fernandez Marina [ 10/Jun/14 ]

Hi durgadeep,

we still need more information to diagnose this ticket. If this is still an issue for you, can you please send use the log file for the node where you run rs.initiate() when mongod has been started with -v? Also, could you upload your stunnel.conf file?

Thanks,
Ramón.

Comment by Andy Schwerin [ 08/May/14 ]

Interesting network topology. To clarify, on every host, the RS members have the same port? That is, let's say you've got members 1, 2 and 3. Is it the case that on all hosts running RS members, member 1 is accessed via localhost:27517, 2 via localhost:27617 and 3 via localhost:27717? It's important that two nodes don't believe they're both member 1, e.g.

Could you start one mongod with -v before running rs.initiate() on it, and then attach the logs to this ticket?

Comment by Durga Deep [ 07/May/14 ]

hey... this is with stunnel configuration for mongodb.

SO basically our stunnel.conf is listening using local host on different ports.

Comment by Thomas Rueckstiess [ 07/May/14 ]

Hi Akka,

I tested this and can't reproduce it. We also have jstests that would have caught such a regression.
What port is the mongod running on where you call the rs.initiate()? Can you share the full log file of that node? We'd need to see the log entries from when the node started up if possible.

Thanks,
Thomas

Generated at Thu Feb 08 03:33:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.