zeromicro / zeromicro/zero-doc

Error while dialing dial tcp 127.0.0.1:2379: connect: connection refused

Open
#163 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
600
Forks
249
PR merge metrics
No merged PRs in 30d

Description

Command: go run check.go -f etc/check.yaml

Output:
Starting rpc server at 0.0.0.0:8080...
{"level":"warn","ts":"2022-12-27T19:20:55.154-0800","logger":"etcd-client","caller":"v3@v3.5.5/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0x14000290380/127.0.0.1:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: last connection error: connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:2379: connect: connection refused""}
{"@timestamp":"2022-12-27T19:20:55.155-08:00","caller":"zrpc/server.go:91","content":"context deadline exceeded","level":"error"}
panic: context deadline exceeded

goroutine 1 [running]:
github.com/zeromicro/go-zero/zrpc.(*RpcServer).Start(0x1027e6bc0?)
{HOME}go/pkg/mod/github.com/zeromicro/go-zero@v1.4.3/zrpc/server.go:92 +0x80
main.main()
{HOME}/Desktop/myapp/bookstore/rpc/check/check.go:38 +0x228
exit status 2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with go run check.go -f etc/check.yaml and start at check.go:38, where the RPC server start fails. Inspect the configured endpoint shown in the output, 127.0.0.1:2379, and compare it with the service setup described by the repository. Done means the command starts successfully or the required configuration and startup steps are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.