-
Notifications
You must be signed in to change notification settings - Fork 8
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
Neither "./services orion" nor "./services scorpio" commands can be invoked. #23
Comments
I am unable to reproduce this. It is probably down to the setup of your local machine. I have re-run the scripts locally and via GitHub Actions see here for the log. I have also created the start-up on GitPod and it runs to completion. If you are still facing issues, then I would suggest you try the GitPod version which spins up all the dependencies in the cloud, and is less prone to issues running on a local machine. |
I followed the tutorial and did the following: $ ./services create
Pulling Docker images
Using default tag: latest
latest: Pulling from curlimages/curl
Digest: sha256:f7f265d5c64eb4463a43a99b6bf773f9e61a50aaa7cefaf564f43e42549a01dd
Status: Image is up to date for curlimages/curl:latest
docker.io/curlimages/curl:latest
WARN[0000] The "host" variable is not set. Defaulting to a blank string.
[+] Running 11/11
?zookeeper Pulled 2.7s
?neo4j Pulled 3.0s
?api-gateway Pulled 2.8s
?orion Pulled 2.4s
? entity-service Pulled 3.0s
?postgres Pulled 2.9s
?scorpio Pulled 2.0s
? search-service Pulled 2.7s
? subscription-service Pulled 2.8s
?kafka Pulled 2.3s
? mongo-db Pulled 3.0s
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
$ ./services orion After executing the above, the following error appears in the container log.
What are the possible settings? |
The
The latest stable is 1.1.1. The bleeding edge is currently 1.2.0-PRE-1222. Where possible, the tutorials usually use a slightly older tested stable image, but you could try updating |
I can't reproduce this issue. Your environment may be corrupted.
|
Orion version has not changed yet.
The container log shows the following:
|
Related: ScorpioBroker/ScorpioBroker#305 I suspect that you are unable to access a public instance of the core |
I tried using the new services script.
I also checked the proxy settings.
I have also set the environment variables on the host in the same way.
I don't know the original behavior, so please give me advice on where to investigate. |
I added "-e HTTP_PROXY -e HTTPS_PROXY" to the following three places, thinking that the environment variables were not passed to the execution of eval.
Change the above part to:
The results of running orion and scorpio are as follows.
What other possible causes are there? |
Any new information on how to avoid it? |
I'm still convinced that this is an "access a public instance of the core You could also raise issues with Orion and Scorpio teams directly to see if they could help. |
I am also working with proxy and met the same problem with orion (I did not try others). The health check command of
This command sends a request to
After fixed, Hope this help. |
?Waiting for Orion-LD to be available
and
?Waiting for Scorpio to respond
After that, it doesn't work.
Please let me know how to avoid this.
The text was updated successfully, but these errors were encountered: