writinwaters commited on
Commit
9487109
·
1 Parent(s): ba51460

Added FAQ why document parsing gets stuck (#385)

Browse files

### What problem does this PR solve?


### Type of change


- [x] Documentation Update

Files changed (1) hide show
  1. docs/faq.md +11 -0
docs/faq.md CHANGED
@@ -90,6 +90,17 @@ Ignore this warning and continue. All system warnings can be ignored.
90
 
91
  Parsing requests have to wait in queue due to limited server resources. We are currently enhancing our algorithms and increasing computing power.
92
 
 
 
 
 
 
 
 
 
 
 
 
93
  ### How to handle `Index failure`?
94
 
95
  An index failure usually indicates an unavailable Elasticsearch service.
 
90
 
91
  Parsing requests have to wait in queue due to limited server resources. We are currently enhancing our algorithms and increasing computing power.
92
 
93
+ ### Why does my document parsing stall at under one percent?
94
+
95
+ If your RAGFlow is deployed *locally*, try the following:
96
+
97
+ 1. Check the log of your RAGFlow server to see if it is running properly:
98
+ ```bash
99
+ docker logs -f ragflow-server
100
+ ```
101
+ 2. Check if the **tast_executor.py** process exist.
102
+ 3. Check if your RAGFlow server can access hf-mirror.com or huggingface.com.
103
+
104
  ### How to handle `Index failure`?
105
 
106
  An index failure usually indicates an unavailable Elasticsearch service.