Referee does not accept connection

Question

(MongoDB version 2.6.3)

I have a set of replicas: 2 nodes + arbiter. The replica set works without problems, but I can’t connect to the arbiter:

Failed to connect to myarbiter.com, reason: errno:111 Connection refused 2014-07-16T13:41:59.513+0000 Error: couldn't connect to server myarbiter.com ( myIP), connection attempt failed at src/mongo/shell/mongo.js:148 exception: connect failed 

Courios is what I can add and remove node to my replica set. Connection to the secondary or primary, I can see the Referee:

 "_id" : 2, "name" : "myarbiter:myport", "health" : 1, "state" : 7, "stateStr" : "ARBITER", "uptime" : 4, "lastHeartbeat" : ISODate("2014-07-16T13:25:13Z"), "lastHeartbeatRecv" : ISODate("2014-07-16T13:25:13Z"), "pingMs" : 111 

If I have the tail mongod.log (on the Arbitrator), I see

 2014-07-16T13:48:15.583+0000 [initandlisten] connection accepted from SOME_IP:SOME_PORT #46 (37 connections now open) 2014-07-16T13:48:15.754+0000 [conn42] authenticate db: admin { authenticate: 1, user: "MYUSER", nonce: "xxx", key: "xxx" } 2014-07-16T13:48:15.754+0000 [conn42] Failed to authenticate MYUSER@admin with mechanism MONGODB-CR: AuthenticationFailed UserNotFound Could not find user MYUSER@admin 2014-07-16T13:48:15.974+0000 [initandlisten] connection accepted from SOME_IP:SOME_POR #47 (38 connections now open) 

With my other set of replicas, I can always connect to Arbiter without any problems. Any idea what is going on?

Edit: If I delete the replica information and delete auth, I can connect to this node without any problems. No problem with the firewall :)

Answer 1

You say that you have a different set of replicas that works without problems. Does it work on the same version of MongoDB as the problem?

MongoDB has an open ticket on referee configuration and connection restrictions. It seems that some changes have occurred recently - you can look and see the information useful to you: https://jira.mongodb.org/browse/SERVER-5479 p>