Skip to content
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

Error when saving document: 6 network error while attempting to run command 'getlasterror' on host '127.0.0.1:54208' #1241

Open
freynolds opened this issue Nov 24, 2016 · 21 comments

Comments

@freynolds
Copy link

@freynolds freynolds commented Nov 24, 2016

Hi, ussing Robomongo 0.9.0 I'm getting that error
Error when saving document: 6 network error while attempting to run command 'getlasterror' on host '127.0.0.1:54208'

I'm using SSH tunnel to a GCE mongos.

This happens normally when it's a big document.
I didn't had this error on 0.8.4

My regards.
Francisco.

@simsekgokhan
Copy link
Collaborator

@simsekgokhan simsekgokhan commented Nov 26, 2016

Hi Francisco, as I understand your problem is for big documents which I assume takes more time.
You can try this solution, it solved a lot of problems in the past: #1106 (comment)

Please let us know how it went.

Best Regards,
Gokhan

@molgrum
Copy link

@molgrum molgrum commented Dec 14, 2016

I have the same problem, workaround did not work. Tried some RCs also.

@simsekgokhan
Copy link
Collaborator

@simsekgokhan simsekgokhan commented Dec 26, 2016

Hi @molgrum , thanks for reporting the problem.
Can you give details about your problem? Robomongo version, local OS and remote mongodb server OS versions. Do you get the same error string?

@molgrum
Copy link

@molgrum molgrum commented Dec 28, 2016

I've tried maybe ten different versions of Robomongo in Fedora 24, either i get this error when saving documents or i get empty collections.
Will provide server MongoDB server version later on!

@molgrum
Copy link

@molgrum molgrum commented Dec 28, 2016

What strikes me is a colleague is using Ubuntu and i got the exact same binary, installed 23-bit libraries, still my copy does not work...

@palasgaonkar
Copy link

@palasgaonkar palasgaonkar commented Jan 2, 2017

Hi,
I am facing the same issue while trying to update large documents over ssh connection.
Edits for smaller documents work just fine. The work-around did not work for me. Also I get the error immediately as in there is no waiting for time out to happen.
robomongo version -- Robomongo 0.9.0-RC9
remote mongodb server -- 3.2.8
local OS -- Ubuntu 14.10

@TomiS
Copy link

@TomiS TomiS commented Jan 3, 2017

Experiencing the same issue. Could it have something to do with document size? I manage to update a small document but when I try to update a larger one in the same collection, it fails.

@simsekgokhan
Copy link
Collaborator

@simsekgokhan simsekgokhan commented Jan 9, 2017

Hi @TomiS , thanks for reporting the problem.
We are currently unable to reproduce the problem. Can you let us know a sample document or size of a document (and the document count if it is also important) so that we can reproduce and investigate the problem?
And please also share Robomongo, local and remote OS versions.

@simsekgokhan
Copy link
Collaborator

@simsekgokhan simsekgokhan commented Jan 9, 2017

Hi All, we have reproduced the problem in our labs. After initial investigation, it seems like the problem is reproducible only with SSH enabled. So probably a timeout problem related to SSH. Disabling SSH the problem was not reproducible.

Until this problem is investigated and fixed in the code, you can try the following workaround solution.
It solved the problem in our labs.

Workaround Solution for MAC/Llinux:
i. Use ssh port forwarding option from MAC terminal to remote mongodb server:

   // if password is used
   ssh -L localport:mongodb_ip:port user@ssh_server_ip
   ssh -L 27018:192.168.3.28:27017 user@192.168.3.28  // working example

   // if private key is used
   ssh -i /path/to/private_key.pem -L localport:mongodb_ip:port user@ssh_server_ip   
   ssh -i temp/priv_key.pem -L 27018:192.168.3.48:27017 user@192.168.3.48    // working example

ii. Go to Robomongo, create connection with localhost:27018
(Note: No need to enable SSH on Robomongo, ssh tunneling is enabled and handled by MAC terminal.)

Workaround Solution for Windows:
Putty can be used to do SSH with port forwarding.
How to information is available, will be given on request if anybody using Robomongo in windows.

@Igor-Belyaev
Copy link

@Igor-Belyaev Igor-Belyaev commented Feb 23, 2017

Hi! We using Robomongo in Windows and get this problem while inserting big document through ssh-connection. Please, consult me how I can use Putty for resolve this trouble.

@Igor-Belyaev
Copy link

@Igor-Belyaev Igor-Belyaev commented Feb 23, 2017

Thanks, I did setup for putty's port forwarding. And I hope this problem will be fixed in next release of Robomongo.

@hazratgs
Copy link

@hazratgs hazratgs commented May 4, 2017

Why is this problem still not solved?

@simsekgokhan
Copy link
Collaborator

@simsekgokhan simsekgokhan commented May 6, 2017

Hi @hazratgs , we will investigate when we have the chance. You may use this workaround solution #1241 (comment) until we fix this problem, seems like it worked for some people. If you share your OS, we can help with setting up this workaround solution.

@zkyne
Copy link

@zkyne zkyne commented Aug 24, 2017

I have the same problem.Has the problem been solved?

@williamknn
Copy link

@williamknn williamknn commented Jan 11, 2018

I've the same problem in the latest version of Robo3T (1.1.1) running on Ubuntu 14.04 LTS.

@chautob0t
Copy link

@chautob0t chautob0t commented Apr 5, 2018

The problem still exists. Robo3T 1.2 on Ubuntu 16.04. @simsekgokhan's workaround works for me.

@kennyevo
Copy link

@kennyevo kennyevo commented May 9, 2018

Robo3T 1.2 on OSX 10.13.5 beta still happening, the workaround gives me "Network unreachable" error

The correct ssh command that worked for me was:
ssh -i path_to/priv_key.pem -L 27018:localhost:27017 user@mongo_server_ip

@juanantoniomosquera
Copy link

@juanantoniomosquera juanantoniomosquera commented Dec 5, 2018

same problem robo3T 1.2.1

@M-Ulyanov
Copy link

@M-Ulyanov M-Ulyanov commented Dec 23, 2018

I have this error with big documents in Robo 3T 1.2.1
Studio 3T has no such problems

@andrewtackett
Copy link

@andrewtackett andrewtackett commented Oct 25, 2019

I still have this problem in Robo 3T 1.3.1 on Ubuntu 16.04. The workaround did not work.

@M-Ulyanov
Copy link

@M-Ulyanov M-Ulyanov commented Oct 26, 2019

Now I use without problems NoSQLBooster

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.