[Bug]: Generates huge log files

[darkSuperman]

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

baf3b9b

RAGFlow image version

v0.17.2

Other environment information

Ubuntu24

Actual behavior

I don't know why such a huge log file is generated, causing the disk space to fill up.

Expected behavior

Logs should be cleared regularly

Steps to reproduce

none

Additional information

[dosubot]

Hey @darkSuperman! I'm here to help you with any bugs, questions, or contributions you have for RAGFlow. Let's work together to solve this issue!

To address the issue of large log files in RAGFlow, you can consider the following steps:

1. Adjust Log Levels: The default log level in RAGFlow is set to INFO, but you can reduce verbosity by adjusting the log levels. You can set the LOG_LEVELS environment variable to change the log level for specific components. For example, to set the log level of ragflow.es_conn to ERROR, use:

   LOG_LEVELS=ragflow.es_conn=ERROR
   

   This will help in reducing the amount of log data generated ^[1].

2. Log Rotation and Cleanup: Currently, there is no built-in log rotation or cleanup mechanism documented in RAGFlow. You might need to implement a custom solution using tools like logrotate to manage log file sizes and perform regular cleanup.

3. Check for Excessive Logging: The logs indicate repeated errors and warnings. Investigate the root cause of these errors, such as socket connection failures, and address them to prevent excessive logging.

4. Customize Log File Paths: If needed, you can customize the log file paths by modifying the nginx.conf file and the docker-compose.yml file to redirect logs to a different location or volume ^[2][3].

Implementing these steps should help manage the log file sizes and prevent disk space issues.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[Staz1994]

Looks like docker's logging policy, Configure logging drivers https://docs.docker.com/engine/logging/configure/

[yourbikun]

I encountered the same problem on Ubuntu 24.02. May I ask how it was finally resolved?

[tp7309]

limit log size is worked.
https://docs.docker.com/engine/logging/configure/