-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Live Loader: Issue with dgraph's default addr #4019
Comments
Caused by #4020. |
This still happening on master - I've build it again in Darwin and tested.
git commit => a5dbfc8
|
I'll leave it opened to keep tracking it. And test it again after #4020 is solved. |
I did more tests around this Same error with: v1.0.15 v1.0.13 v1.0.6 I do not understand why this happens, because 127.0.0.1 is Localhost on any operating system. All the Logs
|
Seems like a machine config issue, @MichelDiz. I tried the same commands you shared on Mac and they work with the default with Dgraph v1.1.0:
|
I’ve created a VM with Windows 10 and tested it there. It works fine. So it is indeed something else very odd. I can't figure out what is it. So in case, this issue happens to other users, please set the addr as localhost. |
I ran into the same problem running self-hosted v24.0.2 on Sequoia. I solved it by running the live loader within the alpha container rather than from a new container; I had to add an additional CLI parameter specifying the zero node:
I suspect the issue is caused by the way docker networking works on a Mac. |
What version of Dgraph are you using?
1.1.0 (ibrahim:badger-update - but it's not related to that branch)
Have you tried reproducing the issue with the latest release?
Yes
What is the hardware spec (RAM, OS)?
Tested on Windows and Darwin
Steps to reproduce the issue (command/config used to run Dgraph).
Start live load with defaults settings. Or set the addr (flag -a)
Usage: dgraph live [flags] Flags: -a, --alpha string Comma-separated list of Dgraph alpha gRPC server addresses (default "127.0.0.1:9080")
This issue also happened in Dgo. As Live Loader uses Dgo, I think Dgo should be checked too.
The error logs
The text was updated successfully, but these errors were encountered: