[COMPASS-5269] 1.29-beta6 to 4.4.9/5.0.3 community shows no databases Created: 08/Nov/21 Updated: 27/Oct/23 Resolved: 19/May/23 |
|
| Status: | Closed |
| Project: | Compass |
| Component/s: | Data |
| Affects Version/s: | 1.29.4 |
| Fix Version/s: | No version |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Rob Gillan | Assignee: | Unassigned |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
OSX 10.15.7 or Ubuntu 21.10, Compass 1.29-beta6, mongo 4.4.9/5.0.3 |
||
| Attachments: |
|
| Documentation Changes: | Not Needed |
| Description |
| Comments |
| Comment by Rhys Howell [ 19/May/23 ] |
|
This has likely gone away with recent releases of Compass. There were bugs around showing errors in the Performance tab in this release, as well as connectivity with sharded instances. rob@nisient.com - sorry for the late reply - If you've upgraded and still see this issue please let us know and we'll reopen. |
| Comment by Rob Gillan [ 10/Nov/21 ] |
|
So immediately after connection, we get a blank screen. First time hitting the performance tab shows an error. Back to databases then performance again and the data/graphs start to flow All from the same instance of Compass |
| Comment by Sergey Petushkov [ 10/Nov/21 ] |
|
Hey rob@nisient.com, a small follow-up. So we were able to reproduce an issue with the sharded cluster, we are not sure if that's the same issue you are encountering, so a few additional questions:
|
| Comment by Sergey Petushkov [ 10/Nov/21 ] |
|
Hey rob@nisient.com! Thanks for trying it out with the current GA and confirming that this doesn't happen there. So far we can't reproduce so we have to ask you to help us a bit more with debugging the issue if possible. So first, this beta version allows you to see the application logs that might highlight the issue. If you can share this file with us, that would be great! You can access it from the Help menu in Compass beta: We currently don't have a defined way of securely sharing these log files with us (we're working on it!), so even though we are trying our best to never include any information that can be considered secret or private there, please take a look at the file content before sharing and check if there is anything there that you don't want us, or anyone else, to see and remove it. If sharing a log file is not an option, maybe you can look through it for any possible error occurrences that that will catch your eye? The log format is the same that MongoDB is using, we are most probably looking for something having an error in the COMPASS-DATA-SERVICE component, but anything suspicious is helpful. If there is nothing suspicious is in the logs, can you check the application devtools accessed through the View menu: And check the console for any suspicious errors or warnings there? If this also doesn't bring anything suspicious, there are a few last things we would appreciate if you could share with us and try out:
|
| Comment by Rob Gillan [ 09/Nov/21 ] |
|
Does not happen with 1.28, and has only started since we upgraded from 4.4.6/7/8 to 4.4.9, and upgraded froom 5.0.2 to 5.0.3 (three different sharded clusters tested) |
| Comment by Le Roux Bodenstein [ 09/Nov/21 ] |
|
Just to confirm: This doesn't happen on 1.28 and is new to 1.29-beta? |
| Comment by Rob Gillan [ 08/Nov/21 ] |
|
sorry, Problem statement should read... Since updating to 4.4.9/5.0.3 |