RD17/ambar

Error when starting up ambar (serviceapi Container is unhealthy)

Closed this issue · 2 comments

ratio91 commented

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

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

I solved it by setting ES memory to:
sudo sysctl -w vm.max_map_count=262144

I use ambar for searching PDF and MS Word Documents (CVs) and improving full-text search for users.

  • 👍1