Can't initiate replica set in Ubuntu

Question

Whenever I type: rs.initiate(), I get the following error message:

{
    "info2" : "no configuration explicitly specified -- making one",
    "me" : "VMHOSTNAME:27017",
    "ok" : 0,
    "errmsg" : "No host described in new configuration 1 for replica set rs0 maps to this node",
    "code" : 93
}

I'm running under google-cloud-engine with latest MongoDB.

Any suggestions on how to solve this?

Helfand

Have you tried making a replica set configuration explicitly? It sounds like the autoconfig process is having trouble coming up with a hostname that maps to the node, which is symptomatic of some networking problem. – Klagenfurt

Answer 1

You could try passing a parameter to the .initiate() command.

Like so:

rs.initiate({_id:"yourReplSetName", members: [{"_id":1, "host":"yourHost:yourPort"}]})

This did the trick for me.

Aesculapian

Thanks. MongoDB official documentation sucks. – Gastrology

Answer 2

Your VMHOSTNAME must be an alias for 127.0.0.1 in your /etc/hosts file to make it work.

See here https://jira.mongodb.org/browse/SERVER-16157

Flaxseed

In particular, it cannot be an alias for 127.0.1.1 as it is by default on Ubuntu, as pointed out in this answer: dba.stackexchange.com/questions/105035/… – Garek

Answer 3

The problem might be in your mongo config. Look for the following line and comment it out:

#bindIp: 127.0.0.1  # Listen to local interface only, comment to listen on all interfaces.

Thighbone

This was the simplest fix on an (Amazon) AWS EC2 instance! – Respect

Answer 4

Yeah, exactly, or you can change your hostname to something that is already in your /etc/hosts pointing to 127.0.0.1 such as localhost.

With a mac you can do this by typing sudo scutil –-set HostName localhost.

Digest

Answer 5

If you find the VMHOSTNAME in the /etc/hostnames file and the referenced mongo instance is running then its possibly a port number error. In my case it was. Shards tipically started at port 27018.

Tantara