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

[freynolds]

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]

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: https://github.com/paralect/robomongo/issues/1106#issuecomment-230258348

Please let us know how it went.

Best Regards,
Gokhan

[molgrum]

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

[simsekgokhan]

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]

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]

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]

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]

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]

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]

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 [email protected]  // 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 [email protected]    // 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]

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]

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

[hazratgs]

Why is this problem still not solved?

[simsekgokhan]

Hi @hazratgs , we will investigate when we have the chance. You may use this workaround solution https://github.com/Studio3T/robomongo/issues/1241#issuecomment-271249193 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]

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

[williamknn]

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

[chautob0t]

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

[kennyevo]

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]

same problem robo3T 1.2.1

[M-Ulyanov]

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

[andrewtackett]

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

[M-Ulyanov]

Now I use without problems NoSQLBooster

[KensingtonTech]

This is absurd. The issue has been open for four years and is still there. When will this be fixed?

[Piotr-Filochowski]

I had the same issue, it appeared randomly after using Robo3T for a year.
The workaround that worked for me was to not use SSH tunnel connection in Robo3T, but to configure SSH tunnel in Putty, and then connect without ssh in Robo3T.

[Lunarix]

I had the same problem, using Robo3T, only for big documents.

I solved it with the description above:

Using Ubuntu to connect to an Ubuntu server:
ssh -i /key.pem -L 27018:127.0.0.1:27017 [email protected] -p xx

You may add -p and your SSH port if you changed it!

Then you can add a new connection in Robo3T:
Address: localhost
Port: 27018

Configure your authentication and DO NOT active SSH.

It should work then, at least it does for me now.

[devpurohit]

I had the same problem, using Robo3T, only for big documents.

I solved it with the description above:

Using Ubuntu to connect to an Ubuntu server:
ssh -i /key.pem -L 27018:127.0.0.1:27017 [email protected] -p xx

You may add -p and your SSH port if you changed it!

Then you can add a new connection in Robo3T:
Address: localhost
Port: 27018

Configure your authentication and DO NOT active SSH.

It should work then, at least it does for me now.

You're a lovely human being.