[Question]: after installation，can't open file sync_data_source.py

[yangliupu]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (Language Policy).
• Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
• Please do not modify this template :) and fill in all the required fields.

Describe your problem

Hi，After installation，there is one error in log, python3: can't open file '/ragflow/rag/svr/sync_data_source.py': [Errno 2] No such file or directory .meanwhile , I can't open the ragflow login html page in the web.

[dosubot]

The error about the missing /ragflow/rag/svr/sync_data_source.py file happens because this file is expected to be present in your installation, but it's missing. Recent updates show that sync_data_source.py is an active part of the backend and is required for RAGFlow to start and function correctly, including the web login page. This issue usually points to an incomplete or incorrect installation—either the package or Docker image you used did not include all the necessary files, or the installation process failed to copy everything needed.

To resolve this, make sure you are using the latest official release or Docker image, as recent pull requests confirm the file is present and maintained in the current codebase (example, example). If you built from source, pull the latest code and rebuild. If you used a prebuilt package or image, try re-downloading and reinstalling to ensure all files are included.

This missing file is a known issue reported by other users, and fixing the installation should also resolve the problem with accessing the login page (reference). If you continue to see this error after reinstalling, double-check that your installation directory contains rag/svr/sync_data_source.py.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[Magicbook1108]

@yangliupu Please provide more details on your installation process. What commands did you execute, and in what order?

[yangliupu]

I just executed the fllowing steps:

1. sudo sysctl -w vm.max_map_count=262144
2. git clone https://github.com/infiniflow/ragflow.git
3. cd ragflow/docker
4. vim .env . just modified
   SVR_WEB_HTTP_PORT=8080
   SVR_WEB_HTTPS_PORT=8443
   SVR_HTTP_PORT=8081
   use RAGFLOW_IMAGE=infiniflow/ragflow:v0.21.1
5. sudo docker compose -f docker-compose.yml up -d

my Docker version 28.5.2, build ecc6942 . Docker Compose version v2.40.3

[yangliupu]

@Magicbook1108 The above is my installation steps

[Magicbook1108]

@yangliupu Just put it in the correct postion and continue to see if any other error exists
sync_data_source.py

[yangliupu]

peewee.ProgrammingError: (1146, "Table 'rag_flow.sync_logs' doesn't exist"

[Magicbook1108]

use RAGFLOW_IMAGE=infiniflow/ragflow:latest

Use the latest image, I have never encountered such sync_logs issue

[Magicbook1108]

@yangliupu Try using the latest image (RAGFLOW_IMAGE=infiniflow/ragflow:latest) if there's no specific reason to stick with v0.21.1. I haven't encountered any issues with sync_logs on the latest version.

[HandSonic]

infiniflow/ragflow:v0.21.1-slim also has this issue.

[Magicbook1108]

@HandSonic
We are currently on v0.21.1, so you can find sync_data_source.py directly in our GitHub repo. It should be there, so please check your git clone process to ensure everything was cloned correctly.

[HandSonic]

@HandSonic We are currently on v0.21.1, so you can find sync_data_source.py directly in our GitHub repo. It should be there, so please check your git clone process to ensure everything was cloned correctly.

I noticed that this file is missing in the v0.21.1 release, causing all Docker images running this version to report the error: https://github.com/infiniflow/ragflow/tree/v0.21.1/rag/svr

[Magicbook1108]

@HandSonic
I double-checked with my colleague, and this file should not be required in v0.21; it’s intended for v0.22. I will try deploying v0.21.1 on my local machine to reproduce the issue you're facing.