[SERVER-3929] Arbitrary replica set authentication "need to login" errors. Created: 22/Sep/11  Updated: 04/Feb/15  Resolved: 28/Oct/11

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

Type: Bug Priority: Major - P3
Reporter: Kyle Banker Assignee: Kristina Chodorow (Inactive)
Resolution: Duplicate Votes: 8
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File chris_output.txt     File logReplica01.tar.gz     File logReplica02.tar.gz     File logReplica03.tar.gz     Text File rs_info.txt     File some-mongodb-outputs    
Issue Links:
Depends
Operating System: ALL
Participants:

 Description   

http://groups.google.com/group/mongodb-user/browse_thread/thread/ce29159aff9b1e00/a155009133f1957a



 Comments   
Comment by Kristina Chodorow (Inactive) [ 12/Dec/11 ]

Restarting the member that has an "auth error" errmsg should help.

Comment by David Chancogne [ 12/Dec/11 ]

Is there a workaround for this until 2.0.2 is released?
Thank you.

Comment by Kristina Chodorow (Inactive) [ 28/Oct/11 ]

Fixed by SERVER-3715

Comment by Kristina Chodorow (Inactive) [ 12/Oct/11 ]

@Chris: that looks like a separate problem... can you file a Jira issue for it?

Comment by Chris Adams [ 12/Oct/11 ]

Kristina - I tried out the development release and am unable to run rs.initiate() due to another error showing up. Any ideas? I have attached a snipped from my log as well as the output of rs.initiate() and rs.status().

Comment by Kristina Chodorow (Inactive) [ 11/Oct/11 ]

Okay, the fix is in the Development Release (Unstable) download. If you are following this bug, please try that and let me know if it works for you so I can work on getting it backported to the 2.0 branch.

Comment by Markus Schirp [ 08/Oct/11 ]

It happens again. This time reboots did not help. 'Im stuck with 3 nodes in "need to login". Im on 2.0.0.

I did a rs.reconfig setting an other primary (using priority adjustments) and suddenly it works again

Comment by Kristina Chodorow (Inactive) [ 07/Oct/11 ]

I think I made a change that fixes this, or at least should give us a clearer idea of what's going wrong, on the 2.1.0 branch. If someone is willing to try it, let me know what system you're on and I'll make a custom build for you.

Comment by Chris Adams [ 07/Oct/11 ]

I am seeing the same error on a test setup. The replica set members will join and sync but after a restart of mongod on the members, they are all unable to communicate with other members of the set. This causes all members to go to secondary status. I have attached a copy of my rs.status(), output after restarting all mongod instances. Disabling Replication Set authentication by removing the keyFile option in the mongodb.conf on all instances fixes the issue.

Comment by Markus Schirp [ 30/Sep/11 ]

The Primary did not accept the new replica member until I restarted it too.

Comment by Markus Schirp [ 30/Sep/11 ]

I was hit exactly from the same issue.

In my case I thankfully did not have to reboot the primary. Only the secondary.

Comment by Alê Borba [ 28/Sep/11 ]

the problem returns without a aparent reason.

Comment by Alê Borba [ 27/Sep/11 ]

Hi Kristina,

Im reboot all nodes and then they works fine again. But I'm affraid this happens again.

Comment by Kristina Chodorow (Inactive) [ 27/Sep/11 ]

@Alê Borba: thank you for the logs!

As a general update on this: it looks like something went wrong with heartbeating from 3->2, but that 2 was still syncing from 3 fine, which is odd. So, I'm trying to track down what could have happened there, I'll update you guys as soon as I figure anything out.

Comment by kuku [ 25/Sep/11 ]

Is 2.0 bugs? What time updated version?

Comment by kuku [ 25/Sep/11 ]

Is 2.0 bugs? What time updated version?

Comment by Alê Borba [ 24/Sep/11 ]

Here my 3 replicas log files

Comment by Kristina Chodorow (Inactive) [ 23/Sep/11 ]

Can you attach your logs from the three servers?

Comment by kuku [ 23/Sep/11 ]

Someone solve? I'm going to use the generation, for environmental officials in support of a ~

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