langgenius/dify-plugin-daemon
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugin-daemon.git synced 2026-07-21 17:25:23 -04:00
Code Issues 111 Packages Projects Releases 10 Wiki Activity

Run failed: PluginDaemonInternalServerError: killed by timeout #147

New Issue
Open
opened 2026-02-16 00:20:07 -05:00 by yindo · 2 comments
yindo commented 2026-02-16 00:20:07 -05:00
Owner
Copy Link
Copy Source

Originally created by @lrange2001 on GitHub (Jun 27, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.5.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

✔️ Expected Behavior

Image

❌ Actual Behavior

Image

Originally created by @lrange2001 on GitHub (Jun 27, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.5.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/365feeb1-7838-492b-af99-b6c32bbec382) ### ✔️ Expected Behavior ![Image](https://github.com/user-attachments/assets/f6912784-c4d4-469a-b821-e3128e0c1747) ### ❌ Actual Behavior ![Image](https://github.com/user-attachments/assets/803d2df7-eb46-4203-8556-90c39ba3db91)
yindo commented 2026-02-16 00:20:08 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jun 27, 2025):

The "PluginDaemonInternalServerError: killed by timeout" error is triggered when the plugin daemon process exceeds its allowed execution time. In Dify (self-hosted, Docker), this timeout is controlled by environment variables: PLUGIN_MAX_EXECUTION_TIMEOUT (default 600 seconds) and GUNICORN_TIMEOUT (default 200 seconds). These values can be increased in your Docker environment if your plugin operations need more time to complete. Timeout enforcement happens at the infrastructure level (Gunicorn, Docker), not within the plugin code itself, so if your plugins are long-running or your server is resource-constrained, you may see this error "docker/.env.example" "api/docker/entrypoint.sh".

Check your Docker Compose or deployment config for these environment variables and try increasing them. Also, review your container's CPU and memory limits to ensure the plugin daemon isn't being killed due to resource exhaustion. Examining the plugin daemon logs around the time of the error may provide more details.

If you can share which plugin or operation was running when this happened, I can help look for more specific causes or solutions.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Jun 27, 2025): <!-- Answer --> The "PluginDaemonInternalServerError: killed by timeout" error is triggered when the plugin daemon process exceeds its allowed execution time. In Dify (self-hosted, Docker), this timeout is controlled by environment variables: PLUGIN_MAX_EXECUTION_TIMEOUT (default 600 seconds) and GUNICORN_TIMEOUT (default 200 seconds). These values can be increased in your Docker environment if your plugin operations need more time to complete. Timeout enforcement happens at the infrastructure level (Gunicorn, Docker), not within the plugin code itself, so if your plugins are long-running or your server is resource-constrained, you may see this error ["docker/.env.example"](https://github.com/langgenius/dify/blob/0cb00d5fd2ab4f04a9d28660cb71bc50b0566833/docker/.env.example) ["api/docker/entrypoint.sh"](https://github.com/langgenius/dify/blob/0cb00d5fd2ab4f04a9d28660cb71bc50b0566833/api/docker/entrypoint.sh). Check your Docker Compose or deployment config for these environment variables and try increasing them. Also, review your container's CPU and memory limits to ensure the plugin daemon isn't being killed due to resource exhaustion. Examining the plugin daemon logs around the time of the error may provide more details. If you can share which plugin or operation was running when this happened, I can help look for more specific causes or solutions. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/6dc3b5dd-f14d-4e47-814c-ad926cfa2cc4?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/6dc3b5dd-f14d-4e47-814c-ad926cfa2cc4?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/6dc3b5dd-f14d-4e47-814c-ad926cfa2cc4?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/6dc3b5dd-f14d-4e47-814c-ad926cfa2cc4?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6dc3b5dd-f14d-4e47-814c-ad926cfa2cc4?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/6dc3b5dd-f14d-4e47-814c-ad926cfa2cc4?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6dc3b5dd-f14d-4e47-814c-ad926cfa2cc4?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/21618)
yindo commented 2026-02-16 00:20:08 -05:00
Author
Owner
Copy Link
Copy Source

@Blackoutta commented on GitHub (Jun 27, 2025):

A few days ago, after I upgraded the plugin daemon to version 0.1.2, I encountered the issue of multiple plugins being killed by timeout. Rolling back to version 0.1.1 restored everything to normal. Then, I tried manually updating the Python dependencies of the stuck plugin, dify_plugin, which also resolved the freezing issue. However, doing this for each plugin would be too labor-intensive. In the end, I decided to stick with version 0.1.1.

@Blackoutta commented on GitHub (Jun 27, 2025): A few days ago, after I upgraded the plugin daemon to version 0.1.2, I encountered the issue of multiple plugins being killed by timeout. Rolling back to version 0.1.1 restored everything to normal. Then, I tried manually updating the Python dependencies of the stuck plugin, dify_plugin, which also resolved the freezing issue. However, doing this for each plugin would be too labor-intensive. In the end, I decided to stick with version 0.1.1.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Windows
bug
cmd
documentation
enhancement
go
good first issue
plugin-daemon
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugin-daemon#147
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?