[SERVER-49753] Shell should provide helpful diagnostics when it fails to select a server but succeeded in discovering some servers or received an OperationFailure Created: 21/Jul/20 Updated: 06/Dec/22 Resolved: 24/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.0-rc12 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Oleg Pudeyev (Inactive) | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Do | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Service Arch
|
| Participants: |
| Description |
|
I attempted to connect to a deployment using mongo shell and received the following output:
This output says:
Given this output, one might try to fix the whitelist but the problem is not at all in network connectivity, but rather there is some kind of an internal issue with this deployment. The error that the Ruby driver, for example, produces when trying to connect to this deployment is:
(Full log: https://gist.github.com/p-mongo/06d779ac56d403d4833aa845994d77f8) From this error one can clearly see that the deployment has two secondaries and no primary, therefore the issue is not the ip whitelist. I see that the shell also has a --verbose option which provides much more log output than the Ruby driver does and in this output you can see some of the responses succeeding. Still the error message can be improved to not suggest ip whitelist as a possible cause when it is not in fact a possible cause. (via https://stackoverflow.com/questions/63006012/trying-to-connect-cluster-to-application#63006012) |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 24/Feb/22 ] | |||||||||||||
|
We haven’t heard back from you for at least one calendar year, so this issue is being closed. If this is still an issue for you, please provide additional information and we will reopen the ticket. | |||||||||||||
| Comment by Oleg Pudeyev (Inactive) [ 16/Aug/20 ] | |||||||||||||
|
The shell also suggests IP whitelist check on auth failure:
If authentication failed (or any OperationFailure was received for that matter), the problem cannot be a whitelist issue. |