Stopped by user. - Githubissues

langgenius / dify

Dify is an open-source LLM app development platform. Dify's intuitive interface combines AI workflow, RAG pipeline, agent capabilities, model management, observability features and more, letting you quickly go from prototype to production.

Other

46.76k stars 6.61k forks source link

Self Checks

[X] This is only for bug report, if you would like to ask a question, please head to Discussions.
[X] I have searched for existing issues search for existing issues, including closed ones.
[X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
[X] Please do not modify this template :) and fill in all the required fields.

Dify version

0.8.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I created a long text generation workflow application and then ran it, and the application stopped automatically. log display: Stopped by user.

timeout set: docker-compose.xml GUNICORN_TIMEOUT: ${GUNICORN_TIMEOUT:-3600} API_TOOL_DEFAULT_CONNECT_TIMEOUT: ${API_TOOL_DEFAULT_CONNECT_TIMEOUT:-6000} API_TOOL_DEFAULT_READ_TIMEOUT: ${API_TOOL_DEFAULT_READ_TIMEOUT:-3600} environment HTTP_REQUEST_MAX_CONNECT_TIMEOUT: 6000

✔️ Expected Behavior

run complete

❌ Actual Behavior

Start 43.843 ms Generate Subtitles and Outlines 1.517K tokens · 31.743 s Extract Subtitles and Outlines 139.945 ms Iteration 19 m 28.879 s

3个迭代 Stopped by user. LLM 3 41.141 s Stopped by user. 2024-09-29 08-02-06屏幕截图

@18600709862 你好！我是Dosu，我是一个可以帮助您解决错误，回答问题并成为贡献者的机器人。我会在等待人类维护者的过程中帮助您。

I found a similar issue that might be relevant to your problem. The issue titled "The workflow has ended, but there is no output on the front end of the page, and the workflow keeps spinning" was closed and referenced by another issue titled "Detailed logs break down with graph_engine and iteration node" ^[1].

The log message "Stopped by user" indicates that the application is being stopped manually or by some external trigger. This message is not related to timeout settings in your docker-compose.yaml or environment variables. Given the provided docker-compose.yaml, the restart: always policy is set for all services, which means the services should automatically restart unless explicitly stopped.

Here are a few potential reasons for this issue:

Manual Intervention: Someone might be manually stopping the containers using commands like docker stop.
External Scripts or Tools: There might be external scripts or tools that are stopping the containers.
Resource Constraints: If the host machine is running out of resources (CPU, memory), Docker might stop the containers.

To further diagnose the issue, you can:

Check the Docker logs for more details using docker logs <container_id>.
Ensure no external scripts or tools are stopping the containers.
Monitor the resource usage on the host machine.

If none of these apply, you might need to look into Docker's event logs to see what is triggering the stop event ^[2].

To continue talking to Dosu, mention @dosu.