[COMPASS-3104] Connection to cluster via mongos fails: An error occurred while loading navigation: Can't use 'local' database through mongos Created: 02/Sep/18  Updated: 10/Jan/24  Resolved: 02/Nov/18

Status: Closed
Project: Compass
Component/s: Connectivity
Affects Version/s: 1.15.1, 1.15.4
Fix Version/s: 1.16.0

Type: Bug Priority: Critical - P2
Reporter: Brian Blevins Assignee: Durran Jordan
Resolution: Fixed Votes: 7
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Can_t_use_local_database_through_mongos.png     PNG File Schermata 2018-10-22 alle 12.04.18.png     PNG File Screen Shot 2018-10-19 at 3.16.23 PM.png     PNG File Screenshot 2018-09-28 15.40.33.png     PNG File after_connect.png     PNG File before_connect.png     PNG File cluster_mongod_in_ops_manager.png     PNG File cluster_mongos_in_ops_manager.png     JPEG File mongo_print.jpg     PNG File same_problem_on_atlas_sharded_cluster.png    
Issue Links:
Related
Sprint: Iteration Mango Miso, Iteration Naan, Iteration Qbert

 Description   

After upgrading from Compass 1.15.0 to 1.15.1 on MacOSX, I am no longer able to successfully access a MongoDB version 3.6.7 sharded cluster via the mongos router. Compass gives the following error message with the arrows beside "DBS" spinning. The same connection settings and credentials worked in version 1.15.0.

> An error occurred while loading navigation: Can't use 'local' database through mongos

Cluster has Username/Password authentication enabled.



 Comments   
Comment by Githook User [ 05/Nov/18 ]

Author:

{'name': 'Durran Jordan', 'email': 'durran@gmail.com', 'username': 'durran'}

Message: COMPASS-3104: Filter out admin & local databases
Branch: master
https://github.com/10gen/compass/commit/03ae3a594398453f9f03ed44010f93a4b5e5801e

Comment by Durran Jordan [ 02/Nov/18 ]

This is fixed in master and also backported to the 1.16-releases branch. 1.16.0 stable will be out Monday or Tuesday.

Comment by Githook User [ 02/Nov/18 ]

Author:

{'name': 'Durran Jordan', 'email': 'durran@gmail.com', 'username': 'durran'}

Message: COMPASS-3104: Filter out admin & local databases
Branch: 1.16-releases
https://github.com/10gen/compass/commit/274b55b77541f81c48235a1bc242a4d4c913c15e

Comment by Githook User [ 02/Nov/18 ]

Author:

{'name': 'Durran Jordan', 'email': 'durran@gmail.com', 'username': 'durran'}

Message: COMPASS-3104: Filter out admin & local databases
Branch: COMPASS-3104
https://github.com/10gen/compass/commit/b6b2df9c106fb0860da486f7f92da10c103f32ec

Comment by Githook User [ 02/Nov/18 ]

Author:

{'name': 'Durran Jordan', 'email': 'durran@gmail.com', 'username': 'durran'}

Message: COMPASS-3104: Filter out admin & local databases
Branch: master
https://github.com/mongodb-js/data-service/commit/fb154bf4633a54fe91736c726b4a3d454fd6b86d

Comment by Thiago T. Maia [ 22/Oct/18 ]

Same issue on 1.15.4 (Community) connecting to mongos 3.2.12

Comment by Marco Lanzotti [ 22/Oct/18 ]

Same issue on 1.15.4 connecting to mongos 4.0.3

Comment by Githook User [ 01/Oct/18 ]

Author:

{'name': 'Lucas Hrabovsky', 'email': 'hrabovsky.lucas@gmail.com', 'username': 'imlucas'}

Message: COMPASS-3104: Testing improvements and investigation (#137)

  • :zap: Project level fixups
  • Remove old mongodb-js-fmt related stuff
  • Update travis to use npm@6 and `npm ci` as compass now does
  • Fix pretest and posttest mongodb-runner commands
  • Fix node_js travis version
  • Disable node_modules cache to see if weird server error goes away
  • Ah! Ports were different
  • > mongodb already running, but its on `localhost:27017` and we need `localhost:27018` for the tests so starting up a new one.
  • 2 mongod's were being started using the same dbpath which is why all of those weird " MongoError: unable to open cursor at URI statistics:table:collection-2-1468183063611865655. reason: No such file or directory" errors were popping up
  • Also why tests were hanging before
  • debugging travis

Rollback 4063342b1ae108c994a22a164430094e65ddb4d0

Puts mocha@3.x and tests now pass as expected.

  • Update to latest mongodb-runner. See mongodb-js/runner#136
  • Update to latest runner
  • Update mongodb-runner so cluster topology can be tested against latest mongodb server releases
  • Expand travis test matrix to include cluster topology for all server versions
  • Remove high volume debugging now that runner is fixed
  • :necktie: Run prettier
  • Fix set isMongos|Writable on connect

Was only being updated before when SDAM topologyChanged fired. So initially, would always both be false until an SDAM change.

Comment by Lucas Hrabovsky (Inactive) [ 28/Sep/18 ]

Confirmed this has been fixed in 1.15.4. Please re-open if the problem persists.

Comment by Githook User [ 26/Sep/18 ]

Author:

{'name': 'Lucas Hrabovsky', 'email': 'hrabovsky.lucas@gmail.com', 'username': 'imlucas'}

Message: COMPASS-3104: Fix CI

Rollback 4063342b1ae108c994a22a164430094e65ddb4d0

Puts mocha@3.x and tests now pass as expected.
Branch: fixups
https://github.com/mongodb-js/data-service/commit/db99db0af0306a61fe2f92bad11506dbcefffc21

Comment by Githook User [ 20/Sep/18 ]

Author:

{'name': 'Lucas Hrabovsky', 'email': 'hrabovsky.lucas@gmail.com', 'username': 'imlucas'}

Message: COMPASS-3104: Add sharding topology back to test matrix
Branch: fixups
https://github.com/mongodb-js/data-service/commit/c6b14dab0dc4170aa6b48481994441f6a9c7adb7

Generated at Wed Feb 07 22:32:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.