dgraph-ratel

[in0ig]

From Installed Binary

dgraph-ratel -version

Ratel Version:

localhost:8000
errot：We seem to have difficulties loading latest client. Try using the pac

[MichelDiz]

Please fulfill the requested template. Or any additional information regard your issue.

[in0ig]

After dgraph-ratel is launched, it is accessed by browser.

Tip: We seem to have difficulties loading latest client. Try using the using

They are all running files in the binary package of 1.08.

[MichelDiz]

Ratel is working as expected here. Tested on Linux, Mac and Windows.
If you need to install this version https://discuss.dgraph.io/t/ratel-installer-for-linux-macos-and-windows-preview-version-ratel-update-from-v1-0-6/2884

I need more context of what you're going through.

Cheers.

[in0ig]

I downloaded ratel-app, the supported system requirement is el7?

[in0ig]

I downloaded the dgraph-1.0.8 binary. Is it a command to open two files separately? The dgraph zero, dgraph server and dgraph-rate commands can be accessed in the browser. Do I need other files?

[in0ig]

[in0ig]

Your latest binary version doesn't have a full tutorial (page rendering or bug). The installation tutorials you can find now are all through docker. I can't pass localhost:8000 after running dgraph-rate

[paulftw]

On the screenshot you've provided Ratel is trying to find dgraph server on 10.17.28.18:8888 but it seems like there's no server listening on that machine/port.

How are you running dgraph? windows/linux/mac, under docker or local binaries?

For me the easiest way to start playing with dgraph was using docker and docker-compose.
Maybe try that and see if it works better?

[in0ig]

I am using a local binary. Dgraph zero, dgraph server are already running, in the console you can use the curl to operate on the dgraph. I can't use docker.

[MichelDiz]

If you are using a local binary, the URL to Dgraph is localhos:8080 and Ratel localhos:8000

As Paul has noted, you are pointing to a seemingly external IP. You need to make sure this IP is serving correctly. The machine that you are using in "10.17.28.18:8888" must have the port open in the firewall, it must be visible on the network. And another detail is you configured the Dgraph to use port 8888? Show the command used to create the Dgraph Serve please.

[MichelDiz]

Another detail, as you are trying to use our Tour the Dgraph port must be 8080, you can not use our Tour on port 8888.

Please read this issue https://github.com/dgraph-io/dgraph/issues/1885

Please let us know if you succeeded.

[in0ig]

This is my startup step:
1.# dgraph zero

Dgraph version : v1.0.8
Commit SHA-1 : 1dd8376
Commit timestamp : 2018-08-31 10:47:07 -0700
Branch : HEAD

For Dgraph official documentation, visit https://docs.dgraph.io.
For discussions about Dgraph , visit https://discuss.dgraph.io.
To say hi to the community , visit https://dgraph.slack.com.

Licensed under Apache 2.0 + Commons Clause. Copyright 2015-2018 Dgraph Labs, Inc.

Setting up grpc listener at: 0.0.0.0:5080
Setting up http listener at: 0.0.0.0:6080
2018/09/09 15:42:48 raft.go:363: Restarting node for dgraphzero
2018/09/09 15:42:48 raft.go:567: INFO: 1 became follower at term 2
2018/09/09 15:42:48 raft.go:315: INFO: newRaft 1 [peers: [], term: 2, commit: 3, applied: 0, lastindex: 3, lastterm: 2]
Running Dgraph zero...
2018/09/09 15:42:48 raft.go:539: Done applying conf change at 1
2018/09/09 15:42:51 raft.go:749: INFO: 1 is starting a new election at term 2
2018/09/09 15:42:51 raft.go:594: INFO: 1 became pre-candidate at term 2
2018/09/09 15:42:51 raft.go:664: INFO: 1 received MsgPreVoteResp from 1 at term 2
2018/09/09 15:42:51 raft.go:580: INFO: 1 became candidate at term 3
2018/09/09 15:42:51 raft.go:664: INFO: 1 received MsgVoteResp from 1 at term 3
2018/09/09 15:42:51 raft.go:621: INFO: 1 became leader at term 3
2018/09/09 15:42:51 node.go:301: INFO: raft.node: 1 elected leader 1 at term 3

2.# dgraph server --lru_mb=2048 --my=10.17.28.18:7080 --zero=10.17.28.18:5080

Dgraph version : v1.0.8
Commit SHA-1 : 1dd8376
Commit timestamp : 2018-08-31 10:47:07 -0700
Branch : HEAD

For Dgraph official documentation, visit https://docs.dgraph.io.
For discussions about Dgraph , visit https://discuss.dgraph.io.
To say hi to the community , visit https://dgraph.slack.com.

Licensed under Apache 2.0 + Commons Clause. Copyright 2015-2018 Dgraph Labs, Inc.

2018/09/09 15:43:46 server.go:118: Setting Badger option: ssd
2018/09/09 15:43:46 server.go:134: Setting Badger table load option: mmap
2018/09/09 15:43:46 server.go:147: Setting Badger value log load option: none
2018/09/09 15:43:46 server.go:158: Opening postings Badger DB with options: {Dir:p ValueDir:p SyncWrites:true TableLoadingMode:2 ValueLogLoadingMode:2 NumVersionsToKeep:2147483647 MaxTableSize:67108864 LevelSizeMultiplier:10 MaxLevels:7 ValueThreshold:32 NumMemtables:5 NumLevelZeroTables:5 NumLevelZeroTablesStall:10 LevelOneSize:268435456 ValueLogFileSize:1073741824 ValueLogMaxEntries:1000000 NumCompactors:3 managedTxns:false DoNotCompact:false maxBatchCount:0 maxBatchSize:0 ReadOnly:false Truncate:true}
2018/09/09 15:43:46 groups.go:80: Current Raft Id: 1
2018/09/09 15:43:46 worker.go:86: Worker listening at address: 0.0.0.0:7080
2018/09/09 15:43:46 gRPC server started. Listening on port 9080
2018/09/09 15:43:46 HTTP server started. Listening on port 8080
2018/09/09 15:43:46 pool.go:108: == CONNECTED ==> Setting 10.17.28.18:5080
2018/09/09 15:43:46 groups.go:107: Connected to group zero. Assigned group: 1
2018/09/09 15:43:46 pool.go:108: == CONNECTED ==> Setting localhost:5080
2018/09/09 15:43:46 draft.go:76: Node ID: 1 with GroupID: 1
2018/09/09 15:43:46 draft.go:963: Restarting node for group: 1
2018/09/09 15:43:46 raft.go:567: INFO: 1 became follower at term 6
2018/09/09 15:43:46 raft.go:315: INFO: newRaft 1 [peers: [], term: 6, commit: 16, applied: 0, lastindex: 16, lastterm: 6]
2018/09/09 15:43:46 groups.go:361: Serving tablet for: predicate
2018/09/09 15:43:46 groups.go:361: Serving tablet for: name
2018/09/09 15:43:46 mutation.go:174: Done schema update predicate:"predicate" value_type:STRING list:true
2018/09/09 15:43:46 groups.go:361: Serving tablet for: revenue
2018/09/09 15:43:46 groups.go:361: Serving tablet for: director
2018/09/09 15:43:46 groups.go:361: Serving tablet for: starring
2018/09/09 15:43:46 groups.go:361: Serving tablet for: release_date
2018/09/09 15:43:46 groups.go:361: Serving tablet for: release_date
2018/09/09 15:43:46 groups.go:361: Serving tablet for: running_time
2018/09/09 15:43:46 groups.go:507: Got address of a Zero server: localhost:5080
2018/09/09 15:43:46 groups.go:361: Serving tablet for: running_time
2018/09/09 15:43:46 mutation.go:174: Done schema update predicate:"name" value_type:STRING directive:INDEX tokenizer:"term"
2018/09/09 15:43:46 mutation.go:174: Done schema update predicate:"release_date" value_type:DATETIME directive:INDEX tokenizer:"year"
2018/09/09 15:43:46 mutation.go:174: Done schema update predicate:"revenue" value_type:FLOAT
2018/09/09 15:43:46 mutation.go:174: Done schema update predicate:"running_time" value_type:INT
2018/09/09 15:43:49 raft.go:749: INFO: 1 is starting a new election at term 6
2018/09/09 15:43:49 raft.go:594: INFO: 1 became pre-candidate at term 6
2018/09/09 15:43:49 raft.go:664: INFO: 1 received MsgPreVoteResp from 1 at term 6
2018/09/09 15:43:49 raft.go:580: INFO: 1 became candidate at term 7
2018/09/09 15:43:49 raft.go:664: INFO: 1 received MsgVoteResp from 1 at term 7
2018/09/09 15:43:49 raft.go:621: INFO: 1 became leader at term 7
2018/09/09 15:43:49 node.go:301: INFO: raft.node: 1 elected leader 1 at term 7
2018/09/09 15:43:49 mutation.go:174: Done schema update predicate:"predicate" value_type:STRING list:true

3.# dgraph-ratel
2018/09/09 15:44:31 Listening on port 8000...

When I booted up, I accessed the 8000 port through the browser and reported an error.
“We seem to have difficulties loading latest client.
Try using the packaged version instead.”

[MichelDiz]

This warning only happens when your machine is without internet.
The Ratel binary accesses the content via CDN.

Please check your internet settings.
Closing this issue because there is no reason other than lack of connection.

Cheers.

With Internet