[Bug]: 2026-02-05 14:25:18,298 WARNING 35 DB is not ready yet: (1146, "Table 'rag_flow.sync_logs' doesn't exist")

[lhxxrds]

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.

RAGFlow workspace code commit ID

456789

RAGFlow image version

v0.22.1

Other environment information

2026-02-05 14:25:18,298 WARNING  35 DB is not ready yet: (1146, "Table 'rag_flow.sync_logs' doesn't exist")

Actual behavior

2026-02-05 14:25:18,298 WARNING 35 DB is not ready yet: (1146, "Table 'rag_flow.sync_logs' doesn't exist")

Expected behavior

2026-02-05 14:25:18,298 WARNING 35 DB is not ready yet: (1146, "Table 'rag_flow.sync_logs' doesn't exist")

Steps to reproduce

2026-02-05 14:25:18,298 WARNING  35 DB is not ready yet: (1146, "Table 'rag_flow.sync_logs' doesn't exist")

Additional information

2026-02-05 14:25:18,298 WARNING 35 DB is not ready yet: (1146, "Table 'rag_flow.sync_logs' doesn't exist")

[dosubot]

This warning means RAGFlow can't find the sync_logs table in your database. The table should be auto-created at startup by the ORM, but this can fail if the MySQL user lacks permissions, if the migration/init logic didn't run, or if there's a mismatch between your code, Docker image, and entrypoint script versions. Sometimes, this warning is normal during initial startup or migrations and resolves itself after a few minutes, but if it persists or causes 502 errors, it's usually a sign of a deeper issue with database initialization or permissions (details).

Here’s what to check:

1. Make sure your MySQL user has full privileges (CREATE, ALTER, SELECT, UPDATE, DELETE) on the rag_flow database.
2. Confirm your code, Docker image, and entrypoint script are all from the same release.
3. Inspect backend and MySQL logs for permission errors or migration failures.
4. If you’re using Docker, ensure your data volumes are not stale or missing. Avoid running docker compose down -v unless you want to reset all data.
5. If you don’t need to preserve data, stop all containers, remove the MySQL data volume, and restart—RAGFlow will auto-create all tables.
6. If you need to keep your data, you can manually trigger the migration logic (see the migrate_db() function in the codebase) or run python rag/svr/sync_data_source.py to help initialize sync_logs (example).

If the warning only appears briefly at startup and the service becomes available after a few minutes, it’s expected behavior (discussion). If it persists, double-check the above points.

To reply, just mention @dosu.

---

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

   

[Magicbook1108]

You can ignore this. I don't think any error will be triggered.

This is a table related to datasource functionality.

[lhxxrds]

but it will lead ragflow not workon @dosu.@Magicbook1108

[Magicbook1108]

I have a few questions and suggestions below:

1. Are your running ragflow service from docker or source code?
2. If you are running from docker， please docker ps -a and take a screen shot. We are looking for which container is unhealthy.
3. If you temporately not plan to use data source functionalities, you can go to entrypoint.sh, set ENABLE_DATASYNC=0. Then docker compose down, up.

[Magicbook1108]

Hello, I have just started a ragflow service from docker compose. You can find I have the same issue with you, but everything is fine.