Error connecting to rethinkDB from golang
php editor Baicao encountered a problem when using golang to connect to rethinkDB. The error message that he could not connect to the rethinkDB server confused him. In response to this problem, he conducted a series of troubleshooting and debugging, and finally found a solution. In this article, we will discuss possible problems and solutions when connecting to rethinkDB from golang.
Question content
I use rethinkdb to run the docker container, and then run go file to connect to the database, but an error occurs when connecting.
Hello everyone. I need help with rethinkdb, I ran the docker container:
docker run --name rth -p 8100:8080 -d rethinkdb
Then visit http://localhost:8100 and there is the homepage of rethinkdb, so everythink is fine. But when I try to connect to the database from golang, I get some errors:
package main import ( r "gopkg.in/rethinkdb/rethinkdb-go.v6" "log" "fmt" ) func main() { _, err := r.connect(r.connectopts{ address: "localhost:28015", database: "test", }) if err != nil { fmt.println(err) log.fatal("could not connect") } }
This error occurs after running go run main.go
:
rethinkdb: dial tcp 127.0.0.1:28015: connect: connection refused 2023/05/18 01:38:39 could not connect exit status 1
Thanks The reason this is happening is that the port is incorrect (28015), but if I change it, except port = 8100, I get the same problem. If I enter 8100 instead of 28015 and get this error:
rethinkdb: Unexpected EOF: HTTP/ 400 Bad Request 2023/05/18 01:38:52 Could not connect exit status 1
Maybe someone knows how to solve this problem)
Workaround
-p 8100:8080
Map the port 8080
in the container to Port 8100
on the host. You are not mapping any other ports, so when you try to access any port other than 8100
(for example, 127.0.0.1:28015
), your request will not reach the container. Something else on the host might be listening on that port, or there might not be anything listening.
You mentioned that you can access the admin interface at http://localhost:8100
; if you check the logs you will notice something like:
listening for administrative http connections on port 8080 listening for client driver connections on port 28015
So the server is listening for connections on multiple ports. Port 8080
(mapped to 8100
) is the management http interface, 28015
is used for driver connections (this is in the documentation). Your code is trying to connect to port 28015
(which is correct), but you have not mapped that port, so it is not accessible on the host; fix this:
docker run --name rth -p 8100:8080 -p 28015:28015 -d rethinkdb
This will map port 28015
in the container to port 28015
on the host (you can use a different host port if needed; just remember to update the code). We can now successfully connect to the following:
package main import ( "fmt" "log" r "gopkg.in/rethinkdb/rethinkdb-go.v6" ) func main() { _, err := r.Connect(r.ConnectOpts{ Address: "localhost:28015", Database: "test", }) if err != nil { fmt.Println(err) log.Fatal("Could not connect") } fmt.Println("Connected") }
The above is the detailed content of Error connecting to rethinkDB from golang. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

Under the BeegoORM framework, how to specify the database associated with the model? Many Beego projects require multiple databases to be operated simultaneously. When using Beego...

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

What should I do if the custom structure labels in GoLand are not displayed? When using GoLand for Go language development, many developers will encounter custom structure tags...

The difference between string printing in Go language: The difference in the effect of using Println and string() functions is in Go...

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...
