mirror of
https://github.com/RD17/ambar.git
synced 2026-04-25 07:25:55 +03:00
[GH-ISSUE #6] "Oops.... Something went wrong" during loading #5
Labels
No labels
$$ Paid Support
bug
bug
enhancement
help wanted
invalid
pull-request
question
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ambar#5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @agreenfield1 on GitHub (Apr 7, 2017).
Original GitHub issue: https://github.com/RD17/ambar/issues/6
It seems like the api is not accessible, even though installation went without any apparent issue. During loading of the page, I get the error "Oops.... Something went wrong" at the bottom. It looks like the ambar-webapi container is restarting every 5 minutes due to not connecting to the ambar-es container?
ambar-webapi container log output:
ambar-es container logs:
@sochix commented on GitHub (Apr 7, 2017):
Hello @agreenfield1 ! Can you please show your
config.jsonanddocker-compose.yml?@agreenfield1 commented on GitHub (Apr 8, 2017):
config.json:
docker-compose.yml:
@isido993 commented on GitHub (Apr 11, 2017):
Here is the issue:
2017/04/07 05:18:52 Timeout after 5m0s waiting on dependencies to become available: [unix:///var/run/docker.sock http://es:9200]Since it connected to Docker socket (
2017/04/07 05:18:52 Connected to unix:///var/run/docker.sock), the problem is that WebApi can't reach ES on es:9200 (internal Docker network). And it's quite strange...Please check if ES is accessible at http://10.20.30.13:9200/_cat/indices and post the result here.
Thnx
@agreenfield1 commented on GitHub (Apr 11, 2017):
http://10.20.30.13:9200/_cat/indices gives me this:
@isido993 commented on GitHub (Apr 13, 2017):
So, ES is up and WebApi has access to it (since it successfully created two indexes).
To be honest, I'm quite out of guesses now... Did you try updating Docker and docker-compose?
@agreenfield1 commented on GitHub (Apr 14, 2017):
Well, I got it working:
Updating to the following didn't help:
I deleted the /opt/ambar directory and reinstalled, but it still didn't work. But I noticed that after doing this http://10.20.30.13:9200/_cat/indices just showed an empty page (no indices), again pointing to a communication problem between webapi and es containers. In the docker-compose.template.yml file I replaced the following line in the webapi>environment section:
- es=http://es:9200with
- es=http://10.20.30.13:9200After stopping and starting, it worked.
@isido993 commented on GitHub (Apr 14, 2017):
You're quite an enthusiast :)
Referring ES by IP is not the best option, in this case all the interaction with ES will be done through physical network adapter, and that's not the most efficient way. That's why we force WebApi to access ES via internal Docker network (by referring it as http://es:9200).
In your case due to some unknown reason WebApi can not access ES via internal net, I honestly have no clue why this could happen. Looks like a bug in Docker or docker-compose. If you eventually figure out why this happened - please let us know.
Thanks!
@agreenfield1 commented on GitHub (Apr 14, 2017):
Stubborn more like it! One last update:
I changed docker-compose.template.yml and back to
- es=http://es:9200The problem returned as expected after stopping/starting. I went into the ambar_webapi_1 container:
sudo docker exec -it ambar_webapi_1 bashand installed httpie. I was able to connect to http://es:9200 with no issue from within the webapi container, even though the main problem was still occurring. Not sure what to make of that.
@robert-mcdermott commented on GitHub (Apr 17, 2017):
I'm experiencing the same thing, here is how I got it working:
@Panos512 commented on GitHub (Apr 24, 2017):
Hello,
I am having the same issue.
I tried replacing
esanddbwith my localhost ip (127.0.0.1) ondocker-compose.template.ymland I also added the same ip onconfig,jsonas local and external host for the api and fe.http://127.0.0.1:9200/_cat/indices is giving me:
and the logs seem fine:
Any ideas what could be wrong?
Thank you in advance.
@sochix commented on GitHub (Apr 25, 2017):
Hello @Panos512 ! Can you please post your machine configuration? What OS is it running?
@Panos512 commented on GitHub (May 4, 2017):
@sochix I was trying to run it on
Ubuntu 17.04. When I tried on another machine usingUbuntu 16.04everything worked perfectly.Dockeranddocker-composeversions were the latest on both installations and I cannot figure anything being different apart from the os version. Anyways I managed to get it working perfectly :)@sochix commented on GitHub (May 4, 2017):
Ok, nice! Ubuntu > 16.04 have some issues with docker that's the problem.
@davemanster commented on GitHub (Jun 25, 2017):
I am on Ubuntu 16.04 and am having the same issue. I have tried replacing http://es:9200 with http://IP:9200 with no success.
@davemanster commented on GitHub (Jun 25, 2017):
Please close. After three minutes of not working it is now working with http://IP:9200.
Thanks
@sochix commented on GitHub (Jun 25, 2017):
@davemanster nice!
@andychoi commented on GitHub (Sep 23, 2017):
same error. followed https://blog.ambar.cloud/ambar-installation-step-by-step-guide-2/
@sochix commented on GitHub (Sep 28, 2017):
@andychoi please, try again. Seem like it's solved problem for @davemanster