New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RoboMongo 0.9.0 : Script executed successfully, but there is no results to show #1269

Open
tishakariya opened this Issue Jan 3, 2017 · 6 comments

Comments

Projects
None yet
4 participants
@tishakariya

tishakariya commented Jan 3, 2017

robo
while executing command
db.getCollection('collectioname').find({});
Output shown is:
Script executed successfully, but there is no results to show
Where as there are (3000) documents in the collection, is there any issue??
RoboMongo Version : 0.9.0 Final
OS: Windows 7

@juliashibalko

This comment has been minimized.

Show comment
Hide comment
@juliashibalko

juliashibalko Jan 4, 2017

Collaborator

Hi @tishakariya, thanks for reporting the issue!
Could you please try this solution, it solved a lot of problems in the past: #1106 (comment)

Please let us know how it went.

Collaborator

juliashibalko commented Jan 4, 2017

Hi @tishakariya, thanks for reporting the issue!
Could you please try this solution, it solved a lot of problems in the past: #1106 (comment)

Please let us know how it went.

@tishakariya

This comment has been minimized.

Show comment
Hide comment
@tishakariya

tishakariya Jan 4, 2017

Hey, Thanks for your reply @juliashibalko, it did not work with that,
still the same error.
The server i am trying to access is a Cloud server running on MongoDB 3.4.0.

tishakariya commented Jan 4, 2017

Hey, Thanks for your reply @juliashibalko, it did not work with that,
still the same error.
The server i am trying to access is a Cloud server running on MongoDB 3.4.0.

@juliashibalko

This comment has been minimized.

Show comment
Hide comment
@juliashibalko

juliashibalko Jan 10, 2017

Collaborator

@tishakariya thanks for details. Could you please share more details to help us with reproducing:

  1. Are you using connection with SSL, SSH or Authentication (if yes, is this admin)?
  2. If it possible, could you tell us more about documents stored in DB? Do they have big size?
    Thanks in advance!
Collaborator

juliashibalko commented Jan 10, 2017

@tishakariya thanks for details. Could you please share more details to help us with reproducing:

  1. Are you using connection with SSL, SSH or Authentication (if yes, is this admin)?
  2. If it possible, could you tell us more about documents stored in DB? Do they have big size?
    Thanks in advance!
@timkarnold

This comment has been minimized.

Show comment
Hide comment
@timkarnold

timkarnold Feb 8, 2017

Seeing this randomly as well. Seems influenced network latency, as it was occurring more frequently when tethered with a slow data connection. Re-attempting the query usually return results after one or more additional attempts.

  1. Authentication as admin, no SSL
  2. Seems to happen on both large and small size document queries

timkarnold commented Feb 8, 2017

Seeing this randomly as well. Seems influenced network latency, as it was occurring more frequently when tethered with a slow data connection. Re-attempting the query usually return results after one or more additional attempts.

  1. Authentication as admin, no SSL
  2. Seems to happen on both large and small size document queries
@Getz85

This comment has been minimized.

Show comment
Hide comment
@Getz85

Getz85 Feb 16, 2017

Same issue here. It looks like the message is displayed only on time-consuming request (ie > 5 seconds).

For information, I tried with all 0.9.0-RCX version since the RC6, and the problem appeared with the 0.9.0-RC8 release.

So I suggest to other user with that problem to switch temporarily to RC7 version.

Getz85 commented Feb 16, 2017

Same issue here. It looks like the message is displayed only on time-consuming request (ie > 5 seconds).

For information, I tried with all 0.9.0-RCX version since the RC6, and the problem appeared with the 0.9.0-RC8 release.

So I suggest to other user with that problem to switch temporarily to RC7 version.

@juliashibalko

This comment has been minimized.

Show comment
Hide comment
@juliashibalko

juliashibalko Jun 28, 2017

Collaborator

Hello guys!
@tishakariya could you please check issue with Robo3T v.1.1 and share results if possible? We implemented support of 3.4 MongoDB and I hope the issue won't be reproduced under this version. Please see new release here https://robomongo.org/download.

@timkarnold @Getz85 could you please try this solution, it solved a lot of problems in the past (increase shell timeout in Options > Change Shell Timeout: #1106 (comment). Check blog http://blog.robomongo.org/robomongo-is-robo-3t/#4a. Please let us know how it went.

Collaborator

juliashibalko commented Jun 28, 2017

Hello guys!
@tishakariya could you please check issue with Robo3T v.1.1 and share results if possible? We implemented support of 3.4 MongoDB and I hope the issue won't be reproduced under this version. Please see new release here https://robomongo.org/download.

@timkarnold @Getz85 could you please try this solution, it solved a lot of problems in the past (increase shell timeout in Options > Change Shell Timeout: #1106 (comment). Check blog http://blog.robomongo.org/robomongo-is-robo-3t/#4a. Please let us know how it went.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment