mirror of
https://github.com/RD17/ambar.git
synced 2026-04-25 23:45:50 +03:00
[GH-ISSUE #189] Error when starting up ambar (serviceapi Container is unhealthy) #186
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#186
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 @ratio91 on GitHub (Sep 27, 2018).
Original GitHub issue: https://github.com/RD17/ambar/issues/189
Creating docker-ambar_redis_1 ... done
Creating docker-ambar_es_1 ... done
Creating docker-ambar_rabbit_1 ... done
Creating docker-ambar_db_1 ... done
ERROR: for serviceapi Container "16d637ef76b6" is unhealthy.
ERROR: Encountered errors while bringing up the project.
anyone else ever encountered this error?
it worked like a charm over the summer, only when I recenctly updated the images this happens.
Please help, thank you!
@isido993 commented on GitHub (Oct 8, 2018):
Hello,
Run 'docker ps -a', find a container with 'exited' state, and then run 'docker logs ' and post the results here.
Also, could you share the business issue you're solving/trying to solve with Ambar with me? It'll help us develop it into a better product. Thanks.
@ratio91 commented on GitHub (Oct 9, 2018):
I solved it by setting ES memory to:
sudo sysctl -w vm.max_map_count=262144I use ambar for searching PDF and MS Word Documents (CVs) and improving full-text search for users.