[SERVER-36088] Replica set connection strings trigger access violation on 4.0 shell + Windows Created: 12/Jul/18 Updated: 04/Sep/18 Resolved: 02/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | 4.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Carlos Roberto Campos | Assignee: | Nick Brewer |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Win10 running on VMWare on Mac |
||
| Issue Links: |
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
I am having this error while trying to use Shell to connect to the atlas server. This is running in a Virtual Windows 10, running from a MacBook using VMWare Fusion. I was able to connect to the local server from the Win10, plus I as able to install the Shell in the Mac itself and the same connection string worked fine. I tried giving more permissions do the mongodb directory plus running the Command Prompt with Administrative rights with no success. Here is the details for the error
|
| Comments |
| Comment by Carlos Roberto Campos [ 19/Jul/18 ] | |||||||||||||||||||||||||||||||||||
|
Awesome Nick!!! | |||||||||||||||||||||||||||||||||||
| Comment by Nick Brewer [ 19/Jul/18 ] | |||||||||||||||||||||||||||||||||||
|
ccamposh I've tested connecting to an Atlas cluster via a SRV record using the 4.0.1 shell on a Windows, and I can confirm that it's working. That error message does indicate a connectivity issue, and I can recreate it myself by disabling external access to my Atlas cluster - as a test, you could try temporarily whitelisting all external addresses on your Atlas cluster to verify this. Since the underlying bug in this case has been resolved, I'm going to close this ticket. Thanks again for bringing this to our attention. Nick | |||||||||||||||||||||||||||||||||||
| Comment by Andrew Morrow (Inactive) [ 18/Jul/18 ] | |||||||||||||||||||||||||||||||||||
|
Thanks ccamposh for trying out the newer shell. I'm quite confident now that the indicated SERVER ticket was the cause of your crash. | |||||||||||||||||||||||||||||||||||
| Comment by Carlos Roberto Campos [ 18/Jul/18 ] | |||||||||||||||||||||||||||||||||||
|
After running this Mongo version, the exception has changed, but still having issues to connect. I verified the internet connection and the port access and everything is fine. At the same time, I ran the mongo 4.0 in the host mac machine and it is capable to connect, so it does not appear to be a network issue.
| |||||||||||||||||||||||||||||||||||
| Comment by Andrew Morrow (Inactive) [ 18/Jul/18 ] | |||||||||||||||||||||||||||||||||||
|
ccamposh - Even better, please use this link to get the most recent v4.0.1-pre build of just the shell: https://s3.amazonaws.com/mciuploads/mongodb-mongo-v4.0/windows-64-2k8-ssl/9c0c1bd5b8cc3ba6b9990fb58cbdf5cde575c634/binaries/mongo-shell-mongodb_mongo_v4.0_windows_64_2k8_ssl_9c0c1bd5b8cc3ba6b9990fb58cbdf5cde575c634_18_07_13_23_36_00.zip | |||||||||||||||||||||||||||||||||||
| Comment by Andrew Morrow (Inactive) [ 18/Jul/18 ] | |||||||||||||||||||||||||||||||||||
|
ccamposh - My apologies, v4.0.1 hasn't quite yet been released. However, you should be able to try the latest v4.0 nightly builds. You can download them from the downloads ceneter by selecting "v4.0 nightly" from https://www.mongodb.com/download-center#development. | |||||||||||||||||||||||||||||||||||
| Comment by Andrew Morrow (Inactive) [ 18/Jul/18 ] | |||||||||||||||||||||||||||||||||||
|
Hi ccamposh - Would you please try the v4.0.1 shell? I suspect that you are encountering | |||||||||||||||||||||||||||||||||||
| Comment by Nick Brewer [ 16/Jul/18 ] | |||||||||||||||||||||||||||||||||||
|
Thanks for your report. I've managed to recreate this in my testing, and I've passed this along to our platform team for additional investigation. In the meantime, you can use the version 3.6.6 shell to connect to your Atlas cluster. Nick |