[SERVER-6549] The correct password may auth fail occasionally. Created: 21/Jul/12 Updated: 11/Jul/16 Resolved: 26/Jul/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | 2.2.0-rc0 |
| Fix Version/s: | 2.2.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | NOVALUE yangfenqiang | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | connection | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu 12.04 LTS |
||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
I have to use "while" for a connection auth, because some ratio to auth fail by using the same correct password. My code: App program log: 192.168.130.15:9001: { errmsg: "need...", code: 8003, ok: 0.0 }. config mongod 1(192.168.130.14:9001) log: config mongod 2(192.168.130.15:9001) log: mongos locate on 192.168.130.14 |
| Comments |
| Comment by auto [ 26/Jul/12 ] |
|
Author: {u'date': u'2012-07-26T08:42:27-07:00', u'email': u'spencer@10gen.com', u'name': u'Spencer T Brody'}Message: |
| Comment by Spencer Brody (Inactive) [ 25/Jul/12 ] |
|
Thank you for attaching the new logs and simplified test file, that's really helpful. I noticed there are always 15 successful attempts before a failed attempt, and at every timestamp where there is a failed attempt there is a message in the mongos log that looks like "scoped connection to 192.168.130.14:9001,192.168.130.15:9001,192.168.130.16:9001 not being returned to the pool". I'm going to take a look at the mongos code and continue investigating. Thanks for your help bringing this issue to our attention! |
| Comment by NOVALUE yangfenqiang [ 24/Jul/12 ] |
|
Hi, Spencer: |
| Comment by Spencer Brody (Inactive) [ 23/Jul/12 ] |
|
I don't see any auth failure messages in the logs you attached, are you certain they're from a run that failed? |
| Comment by NOVALUE yangfenqiang [ 23/Jul/12 ] |
|
The full mongos and config server log is added. |
| Comment by NOVALUE yangfenqiang [ 23/Jul/12 ] |
|
Simple code for test auth. id.exe run same para ("./id.exe 36308763") two times, but one auth failed. yz-uc-core-a04$ ./id.exe 98203809 192.168.130.15:9001: { errmsg: "need...", code: 8003, ok: 0.0 }uid:36308763 Aborted (core dumped) yz-uc-core-a04$ ./id.exe 124381883 |
| Comment by Spencer Brody (Inactive) [ 23/Jul/12 ] |
|
Do you have a test case than can reproduce the problem? Does it only happen with users on the admin database, or does it happen on other databases as well? Does it only happen after adding a new user, or does it also happen to users that have been around for a long time? After authenticating successfully as a given user once, will you ever see the problem resurface with the same user? Can you attach the full mongos and config server logs from a run of this that includes the auth failures? |
| Comment by NOVALUE yangfenqiang [ 21/Jul/12 ] |
|
The same program has never auth failed with mongod version 2.0.6. |
| Comment by NOVALUE yangfenqiang [ 21/Jul/12 ] |
|
sorry, Affects Version/s is 2.2.0-rc0 |