The startup log keeps reporting errors and the document cannot be parsed

[chaijl]

RedisDB.queue_info rag_flow_svr_queue got exception: no such key
2025-06-14 07:33:06,914 INFO 28 task_executor_b898275dc858_0 reported heartbeat: {"name": "task_executor_b898275dc858_0", "now": "2025-06-14T07:33:06.912+08:00", "boot_at": "2025-06-14T07:32:36.875+08:00", "pending": 0, "lag": 0, "done": 0, "failed": 0, "current": {}}

The error above seems to indicate that Redis does not have a key value, but even if I manually added it, it still doesn't work. How should I handle this error

[ZhenhangTung]

@KevinHuSh

[KevinHuSh]

RedisDB.queue_info rag_flow_svr_queue got exception: no such key

This message could be ignored.
Just keep the redis healthy and accessible.

[xqin-ls]

If this message can be ignored, why we can't access the ragflow-server if the default port is changed from 80 to 3080.