Gets stuck on 'Starting replica set...'

[vkarpov15]

Gets stuck on 'Starting replica set...'

[parthnaik]

Setting it to use 4.2.0 worked for me.

[fabien]

Version 4.4.1 isn't working for me either.

[codedavinci]

@fabien +1, we've tried everything to make it work with the version 4.4.1 but it seems that it doesn't want to download it

[codedavinci]

Just checked the source code and it hard codes to get a version up to 4.2 with the current download link

[bhelfert]

I have tried to run it with my locally installed version 4.4.1, using run-rs -m, but the initialization seems to get stuck:

> rs.status()
{
	"operationTime" : Timestamp(0, 0),
	"ok" : 0,
	"errmsg" : "no replset config has been received",
	"code" : 94,
	"codeName" : "NotYetInitialized",
	"$clusterTime" : {
		"clusterTime" : Timestamp(0, 0),
		"signature" : {
			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
			"keyId" : NumberLong(0)
		}
	}
}

It might be the case that the replSetInitiate command was not run or the rs.initiate() call has not happened.

If someone likes to dig deeper, see ReplSet.start().

It still works with 4.2.11.

[vkarpov15]

This looks like an issue with mongodb-topology-manager depending on a MongoDB log message that changed slightly in MongoDB 4.4. There was a fix for this issue but it hasn't been published to npm.

Seeing that mongodb-topology-manager hasn't seen a new release in years, I think we may need to fork it. In the short term, we can probably create a quick patch for this.

[vkarpov15]

Fix is in v0.7.2, see e50337f

[bhelfert]

@vkarpov15 Wow, great! It works! Thank you very much for fixing it both in general and so fast :)!!