infiniflow / ragflow

RAGFlow is an open-source RAG (Retrieval-Augmented Generation) engine based on deep document understanding.
https://ragflow.io
Apache License 2.0
16.4k stars 1.67k forks source link

[Question]: Can't connect to ES cluster #1468

Open 1148330040 opened 1 month ago

1148330040 commented 1 month ago

Describe your problem

错误图片 d1780d4d965959f87d0e85add8d0ab8 docker ps图片,均已启动成功: 1720690078982 从其他 issue中看到的,关于镜像版本全都是dev: 1720690143697 请问老哥,还有可能是 哪里的问题?

KevinHuSh commented 1 month ago

Please refer to this And mind the password consistency between docker/.env and conf/service_conf.yml

zhangxiaotian1996 commented 1 month ago

朋友问题解决了吗?我也遇到了这个问题 尝试可很多办法都不行

luchenwei9266 commented 1 month ago

Please refer to this And mind the password consistency between docker/.env and conf/service_conf.yml请参考此内容 请注意 docker/.env 和 conf/service_conf.yml 之间的密码一致性

This method is useless. I followed this document several times, but I still reported this error. The passwords for the two files are the same.

hellowJuly commented 1 month ago

Please refer to this And mind the password consistency between docker/.env and conf/service_conf.yml

image

i checked, status is healthy. but still have this err that 'Can't connect to ES cluster '

RyanRaw commented 3 weeks ago

我的解决方法发这里了https://github.com/infiniflow/ragflow/issues/1135#issuecomment-2291638601

Randname666 commented 1 week ago

Currently two issues found that could result in the problem:

  1. The port on the host is mapped at 1200 (used to be 9200 but changed at some point) by ragflow-es-01 but ragflow-server still listens at 9200;
  2. ragflow-server isn't having a correct domain resolution set for http://es01. Cannot confirm if this also happens on docker; I tried to deploy it from source code which had no luck.

Solutions:

  1. edit docker-compose.yml and/or .env to map the port on the host back to 9200.
  2. If it's confortable to do so (doesn't cause other resolution issues or security risks), edit /etc/hosts , alternatively configure the DNS to resolve domain es01 to 127.0.0.1; if the ElasticSearch is running on other machines, configure /etc/hosts to where the IP that ElasticSearch is at, alternatively you may have to tweak networking gears.

Alternatively, check the comment mentioned by @RyanRaw .