-
Notifications
You must be signed in to change notification settings - Fork 108
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
"The connection was closed by the other party" error #300
Comments
How do you stop/restart rethinkdb? |
Hi, i have the same issue, my rethinkdn server is on a VM on Virtualbox in a Debian Machine, i have 5 docker containers that perform tasks over the rethinkdb server but suddenly i got this error and all mi microservices cant perform any task because this error, what can i do for fix this? there is a way to do an shared pool resource for rethinkdb for all my microservices? regards |
Hum, my guess is that Virtualbox or docker is killing the connection without properly passing a FIN packet. As far as I know, docker works fine, but I heard a few person having issues with Virtualbox and TCP connections. |
Hi, ive change the RethinkDB machine from Virtualbox to Parallels on clean install, and i have the same issue.... |
Can you try without a VM? |
ok, ill install rethink on my mac os host machine. |
same issue, and get The connection was closed before the query could be completed for.... |
Same issue here! I'm running RethinkDB on my host machine (which is a Mac) and then connect to it from Docker containers |
That's a bit of an old issue. My guess is that something in your stack doesn't keep the TCP connection open. You can try with a simple dump TCP connection ( |
Hey,
I'm seeing this error - "The connection was closed by the other party", which looks like this one - #192. I added ping interval "5", but I still get this error. I'm on OS X with version 2.3.23 of rethinkdbdash.
If I stop rethinkdb and then restart it, on "healthy" I perform another query and I get this error.
The text was updated successfully, but these errors were encountered: