asimniazi63
commented
5 months ago +1
Closed lk1983823 closed 5 months ago
asimniazi63
commented
5 months ago +1
chinmay1819
commented
5 months ago 1+ Not getting it in the logs but getting the same outcome in the browser when I hit the url
chinmay1819
commented
5 months ago [HUQIE]:Build trie /ragflow/rag/res/huqie.txt [HUQIE]:Build trie /ragflow/rag/res/huqie.txt [HUQIE]:Build trie /ragflow/rag/res/huqie.txt WARNING:root:Realtime synonym is disabled, since no redis connection. WARNING:root:Realtime synonym is disabled, since no redis connection. WARNING:root:Realtime synonym is disabled, since no redis connection. [WARNING] Load term.freq FAIL! pytorch_model.bin: 34%|███▍ | 440M/1.30G [00:22<00:36, 23.9MB/s]WARNING:root:Realtime synonym is disabled, since no redis connection. pytorch_model.bin: 100%|██████████| 1.30G/1.30G [01:06<00:00, 19.7MB/s] [WARNING] Load term.freq FAIL! [WARNING] Load term.freq FAIL!
KevinHuSh
commented
5 months ago Is there an existing issue for the same bug?
- [x] I have checked the existing issues.
Branch name
main
Commit ID
newest
Other environment information
No response
Actual behavior
I have pulled the images successfully and do docker compose -f docker-compose-CN.yml up -d.
Expected behavior
No response
Steps to reproduce
[+] Running 6/8 ⠿ Network docker_ragflow Created 0.1s ⠿ Container ragflow-es-01 Healthy 21.2s ⠿ Container ragflow-mysql Healthy 11.2s ⠿ Container ragflow-minio Started 1.7s ⠇ es01 Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. 0.0s ⠿ Container ragflow-kibana Started 21.6s ⠿ Container ragflow-server Started 21.8s ⠇ kibana Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. 0.0s (base) lk@lk:/media/lk/disk1/lk_git/6_NLPandCNN/LLM/ragflow/docker$ docker logs -f ragflow-server [HUQIE]:Build default trie [HUQIE]:Build default trie [HUQIE]:Build default trie [HUQIE]:Build trie /ragflow/rag/res/huqie.txt [HUQIE]:Build trie /ragflow/rag/res/huqie.txt [HUQIE]:Build trie /ragflow/rag/res/huqie.txt WARNING:root:Realtime synonym is disabled, since no redis connection. WARNING:root:Realtime synonym is disabled, since no redis connection. WARNING:root:Realtime synonym is disabled, since no redis connection. [WARNING] Load term.freq FAIL! pytorch_model.bin: 7%|▋ | 94.4M/1.30G [00:29<06:09, 3.27MB/s]WARNING:root:Realtime synonym is disabled, since no redis connection. [WARNING] Load term.freq FAIL! Traceback (most recent call last): File "/root/miniconda3/envs/py11/lib/python3.11/site-packages/peewee.py", line 3291, in execute_sql cursor.execute(sql, params or ()) File "/root/miniconda3/envs/py11/lib/python3.11/site-packages/pymysql/cursors.py", line 153, in execute result = self._query(query) ^^^^^^^^^^^^^^^^^^ File "/root/miniconda3/envs/py11/lib/python3.11/site-packages/pymysql/cursors.py", line 322, in _queryAnyone can helps ? Thanks!
### Additional information  It shows {"data":null,"retcode":100,"retmsg":"<NotFound '404: Not Found'>"} in the website.
Try the solution this issue used. https://github.com/infiniflow/ragflow/issues/226
KevinHuSh
commented
5 months ago 1+ Not getting it in the logs but getting the same outcome in the browser when I hit the url
Figure out the true IP your machine use.
For windows: ipconfig
For linux: ifconfig
chinmay1819
commented
5 months ago I guess there is something else
HD1732
commented
5 months ago +1
zhongmiyu99
commented
5 months ago me too
shaoyie
commented
5 months ago Same error here, and I noticed no tables are created in mysql. And from the log: raise Exception("Can't connect to ES cluster") Exception: Can't connect to ES cluster
looks like connection to ES is not setup too.
shaoyie
commented
5 months ago Btw, what is the docker / docker-compose version is expected? In my environment, cannot understand the
include:
- path: ./docker-compose-base.yml
env_file: ./.envinside docker-compose.yml I have to merge the yml files manually. I'm on Mac.
nevesaynever1
commented
5 months ago When I run the command "docker logs -f ragflow-server ", the next exception occurred, how to solve it?
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/ragflow/rag/svr/task_broker.py", line 180, in
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/ragflow/rag/svr/task_broker.py", line 180, in
oldunclez
commented
5 months ago Same error here, and I noticed no tables are created in mysql. And from the log: raise Exception("Can't connect to ES cluster") Exception: Can't connect to ES cluster
looks like connection to ES is not setup too.
Did you set sysctl -w vm.max_map_count=262144 in the docker host ?
oldunclez
commented
5 months ago in my case ,it keeps complaint :
[WARNING] Load term.freq FAIL!
from rag.app import laws, paper, presentation, manual, qa, table, book, resume, picture, naive, one
File "/ragflow/rag/app/laws.py", line 20, in <module>
from deepdoc.parser import PdfParser, DocxParser, PlainParser
File "/ragflow/deepdoc/parser/__init__.py", line 3, in <module>
from .pdf_parser import HuParser as PdfParser, PlainParser
File "/ragflow/deepdoc/parser/pdf_parser.py", line 15, in <module>
from PyPDF2 import PdfReader as pdf2_read
ModuleNotFoundError: No module named 'PyPDF2'even thought I have install it manally :
docker exec -it ragflow-server /bin/bash
pip install PyPDF2
docker restart ragflow-server and fail to sign up
nevesaynever1
commented
5 months ago Same error here, and I noticed no tables are created in mysql. And from the log: raise Exception("Can't connect to ES cluster") Exception: Can't connect to ES cluster looks like connection to ES is not setup too.
Did you set sysctl -w vm.max_map_count=262144 in the docker host ?
Thanks, the platform is Winfows and it does not support the command set sysctl -w vm.max_map_count=262144, what should I do to solve it
KevinHuSh
commented
5 months ago Btw, what is the docker / docker-compose version is expected? In my environment, cannot understand the
include: - path: ./docker-compose-base.yml env_file: ./.envinside docker-compose.yml I have to merge the yml files manually. I'm on Mac.
Version: 25.0.3
KevinHuSh
commented
5 months ago in my case ,it keeps complaint :
[WARNING] Load term.freq FAIL! from rag.app import laws, paper, presentation, manual, qa, table, book, resume, picture, naive, one File "/ragflow/rag/app/laws.py", line 20, in <module> from deepdoc.parser import PdfParser, DocxParser, PlainParser File "/ragflow/deepdoc/parser/__init__.py", line 3, in <module> from .pdf_parser import HuParser as PdfParser, PlainParser File "/ragflow/deepdoc/parser/pdf_parser.py", line 15, in <module> from PyPDF2 import PdfReader as pdf2_read ModuleNotFoundError: No module named 'PyPDF2'even thought I have install it manally :
docker exec -it ragflow-server /bin/bash pip install PyPDF2 docker restart ragflow-serverand fail to sign up
pull the latest images
wzw773828204
commented
5 months ago Same error here, and I noticed no tables are created in mysql. And from the log: raise Exception("Can't connect to ES cluster") Exception: Can't connect to ES cluster
looks like connection to ES is not setup too.
chang ES_PORT=1200 to ES_PORT=9200 can solve this problem
you can see it curl the url in docker-compose-base.yml healthcheck: test: ["CMD-SHELL", "curl http://localhost:9200"] so 9200 is the right port rather than 1200
jacky68147527
commented
5 months ago This problem still exists.
MacOS 13.5.2 (22G91) Apple M2 Pro
nevesaynever1
commented
5 months ago
I have changed ES_PORT=1200 to ES_PORT=9200, but it still occurs the above exception. The configuration of ES_PORT is as follows:
shuaiFLYINTHESKY
commented
5 months ago [HUQIE]:Build trie /ragflow/rag/res/huqie.txt [HUQIE]:Build trie /ragflow/rag/res/huqie.txt [HUQIE]:Build trie /ragflow/rag/res/huqie.txt WARNING:root:Realtime synonym is disabled, since no redis connection. WARNING:root:Realtime synonym is disabled, since no redis connection. WARNING:root:Realtime synonym is disabled, since no redis connection. [WARNING] Load term.freq FAIL! pytorch_model.bin: 34%|███▍ | 440M/1.30G [00:22<00:36, 23.9MB/s]WARNING:root:Realtime synonym is disabled, since no redis connection. pytorch_model.bin: 100%|██████████| 1.30G/1.30G [01:06<00:00, 19.7MB/s] [WARNING] Load term.freq FAIL! [WARNING] Load term.freq FAIL!
Hello, bro, has this problem been solved? I have the same problem as you. I hope you can give me some helpful advice. Thank you！
ChinaYiqun
commented
5 months ago 同样的问题，
ChinaYiqun
commented
5 months ago 为什么作者将这个bug关闭了，这显然是不负责任的开源项目
coderBuffalo
commented
5 months ago 
[1191261511eb:00023] [[INVALID],INVALID] ORTE_ERROR_LOG: The system limit on number of children a process can have was reached in file ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 633
[1191261511eb:00023] [[INVALID],INVALID] ORTE_ERROR_LOG: The system limit on number of children a process can have was reached in file ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 172
[1191261511eb:00022] [[INVALID],INVALID] ORTE_ERROR_LOG: The system limit on number of children a process can have was reached in file ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 633
[1191261511eb:00022] [[INVALID],INVALID] ORTE_ERROR_LOG: The system limit on number of children a process can have was reached in file ../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 172
--------------------------------------------------------------------------
It looks like orte_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):
orte_ess_init failed
--> Returned value The system limit on number of children a process can have was reached (-119) instead of ORTE_SUCCESS
--------------------------------------------------------------------------
--------------------------------------------------------------------------
It looks like orte_init failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems. This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):
orte_ess_init failed
--> Returned value The system limit on number of children a process can have was reached (-119) instead of ORTE_SUCCESS
--------------------------------------------------------------------------
--------------------------------------------------------------------------
It looks like MPI_INIT failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during MPI_INIT; some of which are due to configuration or environment
problems. This failure appears to be an internal failure; here's some
additional information (which may only be relevant to an Open MPI
developer):
ompi_mpi_init: ompi_rte_init failed
--> Returned "The system limit on number of children a process can have was reached" (-119) instead of "Success" (0)
--------------------------------------------------------------------------
--------------------------------------------------------------------------
It looks like MPI_INIT failed for some reason; your parallel process is
likely to abort. There are many reasons that a parallel process can
fail during MPI_INIT; some of which are due to configuration or environment
problems. This failure appears to be an internal failure; here's some
additional information (which may only be relevant to an Open MPI
developer):
ompi_mpi_init: ompi_rte_init failed
--> Returned "The system limit on number of children a process can have was reached" (-119) instead of "Success" (0)
--------------------------------------------------------------------------
*** An error occurred in MPI_Init_thread
*** on a NULL communicator
*** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
*** and potentially your MPI job)
*** An error occurred in MPI_Init_thread
*** on a NULL communicator
*** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
*** and potentially your MPI job)
andymeadows
commented
3 months ago Curious why this was closed. Don't see anything associated with the fix and we're experiencing the same issue on Debian bookworm:
Traceback (most recent call last):
File "/ragflow/rag/svr/task_executor.py", line 28, in <module>
from api.db.services.file2document_service import File2DocumentService
File "/ragflow/api/db/services/__init__.py", line 18, in <module>
from .user_service import UserService
File "/ragflow/api/db/services/user_service.py", line 22, in <module>
from api.db.db_models import DB, UserTenant
File "/ragflow/api/db/db_models.py", line 32, in <module>
from api.settings import DATABASE, stat_logger, SECRET_KEY
File "/ragflow/api/settings.py", line 35, in <module>
from rag.utils.es_conn import ELASTICSEARCH
File "/ragflow/rag/utils/es_conn.py", line 460, in <module>
ELASTICSEARCH = ESConnection()
File "/ragflow/rag/utils/__init__.py", line 12, in _singleton
instances[key] = cls(*args, **kw)
File "/ragflow/rag/utils/es_conn.py", line 24, in __init__
raise Exception("Can't connect to ES cluster")
Exception: Can't connect to ES clusterFollowed the instructions from the Quickstart at https://ragflow.io/docs/dev/.
/sbin/sysctl vm.max_map_count
vm.max_map_count = 262144
docker --version
Docker version 26.1.4, build 5650f9bSo anyone got a fix for this?
yangboz
commented
2 months ago 为什么作者将这个bug关闭了，这显然是不负责任的开源项目
Issue 好几百，估计忙不过来 :-）
MOSSV2
commented
2 weeks ago 应该是还启动了一个redis占用了，关了另外的redis，重启
dexteon
commented
1 week ago Is there a solution for this? Or anyone know how i can run an older version in docker?
Is there an existing issue for the same bug?
Branch name
main
Commit ID
newest
Other environment information
No response
Actual behavior
I have pulled the images successfully and do docker compose -f docker-compose-CN.yml up -d.
Expected behavior
No response
Steps to reproduce
Anyone can helps ? Thanks!