Alpha can't connect with zero. rpc error

index · January 20, 2020, 12:49pm

Hi, I am completely new to Dgraph. I tried to install and run Dgraph on both MacOs and on a clean Ubuntu but the same error message was thrown after i started the zero and the alpha.

I installed Dgraph via curl with the command you show under the deploy section
curl https://get.dgraph.io -sSf | bash

Dgraph version v1.1.1 and Go version 1.13.5 are installed.

I start the zero with

dgraph zero --my=localhost:5080

which gives me the following response:

I0120 13:25:02.737570    7163 run.go:102] Setting up grpc listener at: 0.0.0.0:5080
I0120 13:25:02.737704    7163 run.go:102] Setting up http listener at: 0.0.0.0:6080
badger 2020/01/20 13:25:02 INFO: All 1 tables opened in 1ms
badger 2020/01/20 13:25:02 INFO: Replaying file id: 0 at offset: 1436
badger 2020/01/20 13:25:02 INFO: Replay took: 34.596µs
badger 2020/01/20 13:25:02 DEBUG: Value log discard stats empty
I0120 13:25:02.751779    7163 node.go:143] Setting raft.Config to: &{ID:1 peers:[] learners:[] ElectionTick:20 HeartbeatTick:1 Storage:0xc00015c570 Applied:0 MaxSizePerMsg:262144 MaxCommittedSizePerReady:67108864 MaxUncommittedEntriesSize:0 MaxInflightMsgs:256 CheckQuorum:false PreVote:true ReadOnlyOption:0 Logger:0x2409218 DisableProposalForwarding:false}
I0120 13:25:02.751991    7163 node.go:312] Found hardstate: {Term:7 Vote:1 Commit:9 XXX_unrecognized:[]}
I0120 13:25:02.752036    7163 node.go:321] Group 0 found 10 entries
I0120 13:25:02.752050    7163 raft.go:447] Restarting node for dgraphzero
I0120 13:25:02.752108    7163 log.go:34] 1 became follower at term 7
I0120 13:25:02.752157    7163 log.go:34] newRaft 1 [peers: [], term: 7, commit: 9, applied: 0, lastindex: 9, lastterm: 7]
I0120 13:25:02.752203    7163 run.go:266] Running Dgraph Zero...
I0120 13:25:02.753305    7163 node.go:180] Setting conf state to nodes:1 
I0120 13:25:02.753352    7163 raft.go:698] Done applying conf change at 0x1
I0120 13:25:03.752960    7163 log.go:34] 1 no leader at term 7; dropping index reading msg
W0120 13:25:05.753480    7163 node.go:669] [0x1] Read index context timed out
I0120 13:25:05.754887    7163 log.go:34] 1 no leader at term 7; dropping index reading msg
I0120 13:25:06.652715    7163 log.go:34] 1 is starting a new election at term 7
I0120 13:25:06.653276    7163 log.go:34] 1 became pre-candidate at term 7
I0120 13:25:06.653454    7163 log.go:34] 1 received MsgPreVoteResp from 1 at term 7
I0120 13:25:06.653617    7163 log.go:34] 1 became candidate at term 8
I0120 13:25:06.654191    7163 log.go:34] 1 received MsgVoteResp from 1 at term 8
I0120 13:25:06.654508    7163 log.go:34] 1 became leader at term 8
I0120 13:25:06.654848    7163 log.go:34] raft.node: 1 elected leader 1 at term 8
I0120 13:25:06.655385    7163 raft.go:663] I've become the leader, updating leases.
I0120 13:25:06.655490    7163 assign.go:41] Updated Lease id: 1. Txn Ts: 1
W0120 13:25:07.755277    7163 node.go:669] [0x1] Read index context timed out

Then I start the alpha with

dgraph alpha --lru_mb=1500 --my=localhost:7080 --zero=localhost:5080

this gives me the following response with the following error:

Error: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp: lookup IPADDR: Temporary failure in name resolution

I0120 13:31:37.000045    7432 run.go:511] x.Config: {PortOffset:0 QueryEdgeLimit:1000000 NormalizeNodeLimit:10000}
I0120 13:31:37.000117    7432 run.go:512] x.WorkerConfig: {ExportPath:export NumPendingProposals:256 Tracing:1 MyAddr:localhost:7080 ZeroAddr:localhost:5080 RaftId:0 WhiteListedIPRanges:[] MaxRetries:-1 StrictMutations:false AclEnabled:false AbortOlderThan:5m0s SnapshotAfter:10000 ProposedGroupId:0}
I0120 13:31:37.000164    7432 run.go:513] worker.Config: {PostingDir:p BadgerTables:mmap BadgerVlog:mmap WALDir:w MutationsMode:0 AuthToken: AllottedMemory:1500.0MB AccessJwtTtl:0s RefreshJwtTtl:0s AclRefreshInterval:0s}
I0120 13:31:37.000202    7432 server_state.go:101] Setting Badger table load option: mmap
I0120 13:31:37.000211    7432 server_state.go:113] Setting Badger value log load option: mmap
I0120 13:31:37.000222    7432 server_state.go:158] Opening write-ahead log BadgerDB with options: {Dir:w ValueDir:w SyncWrites:false TableLoadingMode:1 ValueLogLoadingMode:2 NumVersionsToKeep:1 ReadOnly:false Truncate:true Logger:0x2409218 Compression:2 EventLogging:true InMemory:false MaxTableSize:67108864 LevelSizeMultiplier:10 MaxLevels:7 ValueThreshold:1048576 NumMemtables:5 BlockSize:4096 BloomFalsePositive:0.01 KeepL0InMemory:true MaxCacheSize:10485760 NumLevelZeroTables:5 NumLevelZeroTablesStall:10 LevelOneSize:268435456 ValueLogFileSize:1073741823 ValueLogMaxEntries:10000 NumCompactors:2 CompactL0OnClose:true LogRotatesToFlush:2 ZSTDCompressionLevel:15 VerifyValueChecksum:false EncryptionKey:[] EncryptionKeyRotationDuration:240h0m0s ChecksumVerificationMode:0 managedTxns:false maxBatchCount:0 maxBatchSize:0}
I0120 13:31:37.006052    7432 log.go:34] All 0 tables opened in 0s
I0120 13:31:37.008262    7432 log.go:34] Replaying file id: 0 at offset: 0
I0120 13:31:37.008371    7432 log.go:34] Replay took: 5.015µs
I0120 13:31:37.008418    7432 server_state.go:101] Setting Badger table load option: mmap
I0120 13:31:37.008477    7432 server_state.go:113] Setting Badger value log load option: mmap
I0120 13:31:37.008492    7432 server_state.go:177] Opening postings BadgerDB with options: {Dir:p ValueDir:p SyncWrites:false TableLoadingMode:2 ValueLogLoadingMode:2 NumVersionsToKeep:2147483647 ReadOnly:false Truncate:true Logger:0x2409218 Compression:2 EventLogging:true InMemory:false MaxTableSize:67108864 LevelSizeMultiplier:10 MaxLevels:7 ValueThreshold:1024 NumMemtables:5 BlockSize:4096 BloomFalsePositive:0.01 KeepL0InMemory:true MaxCacheSize:1073741824 NumLevelZeroTables:5 NumLevelZeroTablesStall:10 LevelOneSize:268435456 ValueLogFileSize:1073741823 ValueLogMaxEntries:1000000 NumCompactors:2 CompactL0OnClose:true LogRotatesToFlush:2 ZSTDCompressionLevel:15 VerifyValueChecksum:false EncryptionKey:[] EncryptionKeyRotationDuration:240h0m0s ChecksumVerificationMode:0 managedTxns:false maxBatchCount:0 maxBatchSize:0}
I0120 13:31:37.020867    7432 log.go:34] All 0 tables opened in 0s
I0120 13:31:37.021843    7432 log.go:34] Replaying file id: 0 at offset: 0
I0120 13:31:37.024550    7432 log.go:34] Replay took: 5.22µs
I0120 13:31:37.029847    7432 run.go:422] gRPC server started.  Listening on port 9080
I0120 13:31:37.030219    7432 run.go:423] HTTP server started.  Listening on port 8080
I0120 13:31:37.029900    7432 groups.go:105] Current Raft Id: 0x0
I0120 13:31:37.030152    7432 worker.go:81] Worker listening at address: [::]:7080
I0120 13:31:37.131168    7432 pool.go:148] CONNECTING to localhost:5080
I0120 13:31:37.143463    7432 pool.go:148] CONNECTING to IPADDR:5080
W0120 13:31:37.162970    7432 pool.go:238] Connection lost with IPADDR:5080. Error: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp: lookup IPADDR: Temporary failure in name resolution"
W0120 13:35:02.591009    7432 pool.go:238] Connection lost with localhost:5080. Error: rpc error: code = Unavailable desc = transport is closing

The zero is sending repeatedly

I0120 13:35:02.256897    7413 zero.go:415] Got connection request: cluster_info_only:true 
I0120 13:35:02.258529    7413 zero.go:433] Connected: cluster_info_only:true

Dgraph ratel shows that a connection with localhost:8080 is not available and "Error: t: Please retry again, server is not ready to accept requests", after running a mutation.

Any idea what I’m doing wrong?

amanmangal · January 20, 2020, 12:57pm

Try deleting your w folder and restarting alpha.

index · January 20, 2020, 1:04pm

Deleted the w folder in my home directory. Started the alpha again but nothing changed…

amanmangal · January 20, 2020, 1:50pm

In that case, try this. Stop all the services and delete all the folders (p, zw, w). Now, run all the services. Thanks

MichelDiz · January 20, 2020, 2:20pm

I see these logs. And they can mean two things. Or you are running Dgraph using “IPADDR: 5080” instead of “localhost: 5080” or “192.168.10.88:5080” or something. Or maybe you need to do exactly what Aman said. Start from scratch. Because the path where the Dgraph is located is “contaminated” with previous configurations.

Make sure you’re in the right path.

cheers.

index · January 20, 2020, 2:42pm

Thanks @amanmangal, it seems to work now after deleting these three folders.

system · February 19, 2020, 2:42pm

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

Topic		Replies	Views
Dgraph Zero Reports Errors when Alpha Connects Dgraph dgraph , kind:enhancement , status:accepted , area:usability	1	552	July 14, 2020
Cannot connect to zero from alpha on another host Users	8	1947	April 11, 2019
How to configure port for alpha , zero and ratel Dgraph	8	1655	February 18, 2021
Why does alpha still connect to localshost:5080 after specifying the zero parameter? Dgraph kind:question	1	673	November 27, 2020
Failing to connect Alpha with Zero - Need help in setting the docker cluster setup Dgraph	17	1841	June 23, 2020

Alpha can't connect with zero. rpc error

Related Topics