Error on start service twice

Users
1

I followed https://docs.dgraph.io/get-started/ , for the first time ,it’s OK
Then I shutdown the two services( dgraphzero and dgraph ) by ctrl+c and started them again.
Both of them got errors, and even the dgraph service could not run
Paste the errors (only part of all the errors since errors are the same ).

Errors on dgraphzero:
…
2017/10/20 08:11:11 pool.go:150: Echo error from localhost:12345. Err: rpc error: code = Unavailable desc = grpc: the connection is unavailable
2017/10/20 08:11:21 pool.go:150: Echo error from localhost:12345. Err: rpc error: code = Unavailable desc = grpc: the connection is unavailable
2017/10/20 08:11:31 pool.go:150

Errors on dgraph:
…
2017/10/20 08:11:01 groups.go:112: Error while connecting with group zero: rpc error: code = Unknown desc = Node is already part of group
2017/10/20 08:11:01 groups.go:112: Error while connecting with group zero: rpc error: code = Unknown desc = Node is already part of group

And I tested on binary and docker mode, both had this problem

1 Like
2

btw, lastest version (0.8.3)

3

https://github.com/dgraph-io/dgraph/issues/1613
looks like it is a dup for this issue

4

That particular issue was fixed in master (though don’t use master).

What you need to do is to first bring zero back up. It would complain about no connection to dgraph, but you can ignore those warnings.

Then bring up dgraph. Note that you have to wait 10 seconds before dgraph can reconnect to zero after a restart (in master this delay doesn’t exist anymore) – after that zero should accept dgraph, and connection warnings should go away.

2 Likes
5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.