langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 03:55:25 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

when execute work flow with agent node, report error:no available node, plugin runtime not found #22224

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

Originally created by @kanjoe888 on GitHub (Feb 14, 2026).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.13.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Whether I use the workflow process from before the upgrade or a newly created one, an error always occurs as long as there is an agent node. I have tested the large model plugin being used, and it works fine in chatflow, ruling out the possibility that the issue is caused by the plugin.

the log is :

2026-02-14 10:27:48 plugin_daemon-1 | 2026-02-14T02:27:48.444349157Z WARN dify-plugin-daemon middleware.go:83 trace_id=f9a344c2f39a3f7a09524d7564321903 tenant_id=c67846c0-48f9-49a9-8d20-7ae5095fee39 HTTP request client_ip=172.18.0.10 method=POST path=/plugin/c67846c0-48f9-49a9-8d20-7ae5095fee39/dispatch/model/schema status=404 latency_ms=1
2026-02-14 10:27:48 worker-1 | 2026-02-14 02:27:48.460 ERROR [GraphWorker-0] [base.py:305] 83149779888e5ffaaf2c4bcb97e4192c - Error in stream response for plugin {'code': -500, 'message': '{"message":"no available node, plugin runtime not found","error_type":"PluginDaemonInternalServerError","args":null}', 'data': None}
2026-02-14 10:27:48 worker-1 | 2026-02-14 02:27:48.461 ERROR [GraphWorker-0] [node.py:393] 83149779888e5ffaaf2c4bcb97e4192c - Node 1771035857950 failed to run
2026-02-14 10:27:48 worker-1 | Traceback (most recent call last):
2026-02-14 10:27:48 worker-1 | File "/app/api/core/workflow/nodes/base/node.py", line 368, in run
2026-02-14 10:27:48 worker-1 | for event in result:
2026-02-14 10:27:48 worker-1 | ^^^^^^
2026-02-14 10:27:48 worker-1 | File "/app/api/core/workflow/nodes/agent/agent_node.py", line 102, in _run
2026-02-14 10:27:48 worker-1 | parameters = self._generate_agent_parameters(
2026-02-14 10:27:48 worker-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2026-02-14 10:27:48 worker-1 | File "/app/api/core/workflow/nodes/agent/agent_node.py", line 319, in _generate_agent_parameters
2026-02-14 10:27:48 worker-1 | model_instance, model_schema = self._fetch_model(value)
2026-02-14 10:27:48 worker-1 | ^^^^^^^^^^^^^^^^^^^^^^^^
2026-02-14 10:27:48 worker-1 | File "/app/api/core/workflow/nodes/agent/agent_node.py", line 448, in _fetch_model
2026-02-14 10:27:48 worker-1 | model_schema = model_type_instance.get_model_schema(model_name, model_credentials)
2026-02-14 10:27:48 worker-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2026-02-14 10:27:48 worker-1 | File "/app/api/core/model_runtime/model_providers/__base/ai_model.py", line 183, in get_model_schema
2026-02-14 10:27:48 worker-1 | schema = plugin_model_manager.get_model_schema(
2026-02-14 10:27:48 worker-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2026-02-14 10:27:48 worker-1 | File "/app/api/core/plugin/impl/model.py", line 69, in get_model_schema
2026-02-14 10:27:48 worker-1 | for resp in response:
2026-02-14 10:27:48 worker-1 | ^^^^^^^^
2026-02-14 10:27:48 worker-1 | File "/app/api/core/plugin/impl/base.py", line 306, in _request_with_plugin_daemon_response_stream
2026-02-14 10:27:48 worker-1 | self._handle_plugin_daemon_error(error.error_type, error.message)
2026-02-14 10:27:48 worker-1 | File "/app/api/core/plugin/impl/base.py", line 349, in _handle_plugin_daemon_error
2026-02-14 10:27:48 worker-1 | raise PluginDaemonInternalServerError(description=message)
2026-02-14 10:27:48 worker-1 | core.plugin.impl.exc.PluginDaemonInternalServerError: req_id: 24b0208706 PluginDaemonInternalServerError: no available node, plugin runtime not found
2026-02-14 10:27:48 worker-1 | 2026-02-14 02:27:48.541 ERROR [GraphDispatcher] [error_handler.py:101] - Node 1771035857950 failed with ABORT strategy: req_id: 24b0208706 PluginDaemonInternalServerError: no available node, plugin runtime not found
2026-02-14 10:27:48 worker-1 | 2026-02-14 02:27:48.747 INFO [Dummy-13] [trace.py:128] 83149779888e5ffaaf2c4bcb97e4192c - Task tasks.app_generate.workflow_execute_task.workflow_based_app_execution_task[4984c65b-714c-4bba-a6ee-a23b623bbefe] succeeded in 2.0975028459999976s: None
2026-02-14 10:27:48 worker-1 | 2026-02-14 02:27:48.786 ERROR [Thread-14 (_generate_worker)] [workflow_entry.py:124] 83149779888e5ffaaf2c4bcb97e4192c - Unknown Error when workflow entry running
2026-02-14 10:27:48 worker-1 | Traceback (most recent call last):
2026-02-14 10:27:48 worker-1 | File "/app/api/core/workflow/workflow_entry.py", line 120, in run
2026-02-14 10:27:48 worker-1 | yield from generator
2026-02-14 10:27:48 worker-1 | File "/app/api/core/workflow/graph_engine/graph_engine.py", line 276, in run
2026-02-14 10:27:48 worker-1 | raise self._graph_execution.error
2026-02-14 10:27:48 worker-1 | RuntimeError: req_id: 24b0208706 PluginDaemonInternalServerError: no available node, plugin runtime not found
2026-02-14 10:27:48 nginx-1 | 172.18.0.1 - - [14/Feb/2026:02:27:48 +0000] "GET /console/api/apps/74c6494f-b51d-40d0-a440-8584312f597d/workflows/draft/system-variables HTTP/1.1" 200 1547 "http://localhost/app/74c6494f-b51d-40d0-a440-8584312f597d/workflow" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36" "-"
2026-02-14 10:27:49 nginx-1 | 172.18.0.1 - - [14/Feb/2026:02:27:49 +0000] "GET /console/api/apps/74c6494f-b51d-40d0-a440-8584312f597d/workflows/draft/variables?page=1&limit=100 HTTP/1.1" 200 1415 "http://localhost/app/74c6494f-b51d-40d0-a440-8584312f597d/workflow" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36" "-"
2026-02-14 10:27:49 nginx-1 | 172.18.0.1 - - [14/Feb/2026:02:27:49 +0000] "GET /console/api/apps/74c6494f-b51d-40d0-a440-8584312f597d/workflows/draft/conversation-variables HTTP/1.1" 200 13 "http://localhost/app/74c6494f-b51d-40d0-a440-8584312f597d/workflow" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36" "-"
2026-02-14 10:27:49 nginx-1 | 172.18.0.1 - - [14/Feb/2026:02:27:49 +0000] "POST /console/api/apps/74c6494f-b51d-40d0-a440-8584312f597d/workflows/draft/run HTTP/1.1" 200 4106 "http://localhost/app/74c6494f-b51d-40d0-a440-8584312f597d/workflow" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36" "-"
2026-02-14 10:27:50 plugin_daemon-1 | 2026-02-14T02:27:50.305234594Z ERROR dify-plugin-daemon installed_bucket.go:81 failed to create PluginUniqueIdentifier from path path=abesticode/knowledge_pro_0.0.1@c36329a7a0ec70b0920a27fcae1692e180907b20b344b0c9302257ca7108dfc8 error="plugin_unique_identifier is not valid: abesticode/knowledge_pro_0.0.1@c36329a7a0ec70b0920a27fcae1692e180907b20b344b0c9302257ca7108dfc8"
2026-

Image

✔️ Expected Behavior

execute work flow normally

❌ Actual Behavior

report error

Originally created by @kanjoe888 on GitHub (Feb 14, 2026). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.13.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Whether I use the workflow process from before the upgrade or a newly created one, an error always occurs as long as there is an agent node. I have tested the large model plugin being used, and it works fine in chatflow, ruling out the possibility that the issue is caused by the plugin. the log is : 2026-02-14 10:27:48 plugin_daemon-1 | 2026-02-14T02:27:48.444349157Z WARN dify-plugin-daemon middleware.go:83 trace_id=f9a344c2f39a3f7a09524d7564321903 tenant_id=c67846c0-48f9-49a9-8d20-7ae5095fee39 HTTP request client_ip=172.18.0.10 method=POST path=/plugin/c67846c0-48f9-49a9-8d20-7ae5095fee39/dispatch/model/schema status=404 latency_ms=1 2026-02-14 10:27:48 worker-1 | 2026-02-14 02:27:48.460 ERROR [GraphWorker-0] [base.py:305] 83149779888e5ffaaf2c4bcb97e4192c - Error in stream response for plugin {'code': -500, 'message': '{"message":"no available node, plugin runtime not found","error_type":"PluginDaemonInternalServerError","args":null}', 'data': None} 2026-02-14 10:27:48 worker-1 | 2026-02-14 02:27:48.461 ERROR [GraphWorker-0] [node.py:393] 83149779888e5ffaaf2c4bcb97e4192c - Node 1771035857950 failed to run 2026-02-14 10:27:48 worker-1 | Traceback (most recent call last): 2026-02-14 10:27:48 worker-1 | File "/app/api/core/workflow/nodes/base/node.py", line 368, in run 2026-02-14 10:27:48 worker-1 | for event in result: 2026-02-14 10:27:48 worker-1 | ^^^^^^ 2026-02-14 10:27:48 worker-1 | File "/app/api/core/workflow/nodes/agent/agent_node.py", line 102, in _run 2026-02-14 10:27:48 worker-1 | parameters = self._generate_agent_parameters( 2026-02-14 10:27:48 worker-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2026-02-14 10:27:48 worker-1 | File "/app/api/core/workflow/nodes/agent/agent_node.py", line 319, in _generate_agent_parameters 2026-02-14 10:27:48 worker-1 | model_instance, model_schema = self._fetch_model(value) 2026-02-14 10:27:48 worker-1 | ^^^^^^^^^^^^^^^^^^^^^^^^ 2026-02-14 10:27:48 worker-1 | File "/app/api/core/workflow/nodes/agent/agent_node.py", line 448, in _fetch_model 2026-02-14 10:27:48 worker-1 | model_schema = model_type_instance.get_model_schema(model_name, model_credentials) 2026-02-14 10:27:48 worker-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2026-02-14 10:27:48 worker-1 | File "/app/api/core/model_runtime/model_providers/__base/ai_model.py", line 183, in get_model_schema 2026-02-14 10:27:48 worker-1 | schema = plugin_model_manager.get_model_schema( 2026-02-14 10:27:48 worker-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2026-02-14 10:27:48 worker-1 | File "/app/api/core/plugin/impl/model.py", line 69, in get_model_schema 2026-02-14 10:27:48 worker-1 | for resp in response: 2026-02-14 10:27:48 worker-1 | ^^^^^^^^ 2026-02-14 10:27:48 worker-1 | File "/app/api/core/plugin/impl/base.py", line 306, in _request_with_plugin_daemon_response_stream 2026-02-14 10:27:48 worker-1 | self._handle_plugin_daemon_error(error.error_type, error.message) 2026-02-14 10:27:48 worker-1 | File "/app/api/core/plugin/impl/base.py", line 349, in _handle_plugin_daemon_error 2026-02-14 10:27:48 worker-1 | raise PluginDaemonInternalServerError(description=message) 2026-02-14 10:27:48 worker-1 | core.plugin.impl.exc.PluginDaemonInternalServerError: req_id: 24b0208706 PluginDaemonInternalServerError: no available node, plugin runtime not found 2026-02-14 10:27:48 worker-1 | 2026-02-14 02:27:48.541 ERROR [GraphDispatcher] [error_handler.py:101] - Node 1771035857950 failed with ABORT strategy: req_id: 24b0208706 PluginDaemonInternalServerError: no available node, plugin runtime not found 2026-02-14 10:27:48 worker-1 | 2026-02-14 02:27:48.747 INFO [Dummy-13] [trace.py:128] 83149779888e5ffaaf2c4bcb97e4192c - Task tasks.app_generate.workflow_execute_task.workflow_based_app_execution_task[4984c65b-714c-4bba-a6ee-a23b623bbefe] succeeded in 2.0975028459999976s: None 2026-02-14 10:27:48 worker-1 | 2026-02-14 02:27:48.786 ERROR [Thread-14 (_generate_worker)] [workflow_entry.py:124] 83149779888e5ffaaf2c4bcb97e4192c - Unknown Error when workflow entry running 2026-02-14 10:27:48 worker-1 | Traceback (most recent call last): 2026-02-14 10:27:48 worker-1 | File "/app/api/core/workflow/workflow_entry.py", line 120, in run 2026-02-14 10:27:48 worker-1 | yield from generator 2026-02-14 10:27:48 worker-1 | File "/app/api/core/workflow/graph_engine/graph_engine.py", line 276, in run 2026-02-14 10:27:48 worker-1 | raise self._graph_execution.error 2026-02-14 10:27:48 worker-1 | RuntimeError: req_id: 24b0208706 PluginDaemonInternalServerError: no available node, plugin runtime not found 2026-02-14 10:27:48 nginx-1 | 172.18.0.1 - - [14/Feb/2026:02:27:48 +0000] "GET /console/api/apps/74c6494f-b51d-40d0-a440-8584312f597d/workflows/draft/system-variables HTTP/1.1" 200 1547 "http://localhost/app/74c6494f-b51d-40d0-a440-8584312f597d/workflow" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36" "-" 2026-02-14 10:27:49 nginx-1 | 172.18.0.1 - - [14/Feb/2026:02:27:49 +0000] "GET /console/api/apps/74c6494f-b51d-40d0-a440-8584312f597d/workflows/draft/variables?page=1&limit=100 HTTP/1.1" 200 1415 "http://localhost/app/74c6494f-b51d-40d0-a440-8584312f597d/workflow" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36" "-" 2026-02-14 10:27:49 nginx-1 | 172.18.0.1 - - [14/Feb/2026:02:27:49 +0000] "GET /console/api/apps/74c6494f-b51d-40d0-a440-8584312f597d/workflows/draft/conversation-variables HTTP/1.1" 200 13 "http://localhost/app/74c6494f-b51d-40d0-a440-8584312f597d/workflow" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36" "-" 2026-02-14 10:27:49 nginx-1 | 172.18.0.1 - - [14/Feb/2026:02:27:49 +0000] "POST /console/api/apps/74c6494f-b51d-40d0-a440-8584312f597d/workflows/draft/run HTTP/1.1" 200 4106 "http://localhost/app/74c6494f-b51d-40d0-a440-8584312f597d/workflow" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/144.0.0.0 Safari/537.36" "-" 2026-02-14 10:27:50 plugin_daemon-1 | 2026-02-14T02:27:50.305234594Z ERROR dify-plugin-daemon installed_bucket.go:81 failed to create PluginUniqueIdentifier from path path=abesticode/knowledge_pro_0.0.1@c36329a7a0ec70b0920a27fcae1692e180907b20b344b0c9302257ca7108dfc8 error="plugin_unique_identifier is not valid: abesticode/knowledge_pro_0.0.1@c36329a7a0ec70b0920a27fcae1692e180907b20b344b0c9302257ca7108dfc8" 2026- <img width="1908" height="553" alt="Image" src="https://github.com/user-attachments/assets/2ea3979d-db41-4be1-83b1-cd7019701692" /> ### ✔️ Expected Behavior execute work flow normally ### ❌ Actual Behavior report error
yindo added the 🐞 bug label 2026-02-21 20:16:13 -05:00
yindo commented 2026-02-21 20:16:13 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 14, 2026):

This error typically occurs when the plugin daemon cannot locate or initialize the plugin runtime. Based on similar issues, here are the solutions:

Most Reliable Fix: Uninstall and Reinstall the Plugin

  1. Uninstall the model provider plugin (e.g., deepseek) through the Dify UI
  2. Restart the plugin daemon container: 
    docker restart docker-plugin_daemon-1
  3. Reinstall the plugin from the marketplace

Alternative: Remove Broken Virtual Environment

  1. Enter the plugin daemon container: 
    docker exec -it docker-plugin_daemon-1 bash
  2. Find and remove broken .venv directories: 
    VENV=$(find /app/storage -maxdepth 5 -type d -name '.venv' | head -n1)
rm -rf "$VENV"
  3. Restart the plugin daemon

For Agent Nodes Specifically (v1.13.0)
There's a known issue where workflows with agent nodes may fail after upgrading. Try removing and re-adding the agent node in your workflow to refresh plugin references.

The "failed to create PluginUniqueIdentifier" error in your logs suggests database inconsistency between plugin records and actual files - reinstalling the plugins should resolve this.

To reply, just mention @dosu.

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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 14, 2026): <!-- Answer --> This error typically occurs when the plugin daemon cannot locate or initialize the plugin runtime. Based on similar issues, here are the solutions: **Most Reliable Fix: Uninstall and Reinstall the Plugin** 1. Uninstall the model provider plugin (e.g., deepseek) through the Dify UI 2. Restart the plugin daemon container: ```bash docker restart docker-plugin_daemon-1 ``` 3. Reinstall the plugin from the marketplace **Alternative: Remove Broken Virtual Environment** 1. Enter the plugin daemon container: ```bash docker exec -it docker-plugin_daemon-1 bash ``` 2. Find and remove broken `.venv` directories: ```bash VENV=$(find /app/storage -maxdepth 5 -type d -name '.venv' | head -n1) rm -rf "$VENV" ``` 3. Restart the plugin daemon **For Agent Nodes Specifically (v1.13.0)** There's a [known issue](https://github.com/langgenius/dify/issues/32253) where workflows with agent nodes may fail after upgrading. Try removing and re-adding the agent node in your workflow to refresh plugin references. The "failed to create PluginUniqueIdentifier" error in your logs suggests [database inconsistency between plugin records and actual files](https://github.com/langgenius/dify/issues/31303) - reinstalling the plugins should resolve this. <!-- 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/012350a9-c2b2-4900-adda-cada6232b60c?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/012350a9-c2b2-4900-adda-cada6232b60c?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/012350a9-c2b2-4900-adda-cada6232b60c?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/012350a9-c2b2-4900-adda-cada6232b60c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/012350a9-c2b2-4900-adda-cada6232b60c?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/012350a9-c2b2-4900-adda-cada6232b60c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/012350a9-c2b2-4900-adda-cada6232b60c?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20error%20typically%20occurs%20when%20the%20plugin%20daemon%20cannot%20locate%20or%20initialize%20the%20plugin%20runtime.%20Based%20on%20similar%20issues%2C%20here%20are%20the%20solutions%3A%0A%0A%2A%2AMost%20Reliable%20Fix%3A%20Uninstall%20and%20Reinstall%20the%20Plugin%2A%2A%0A1.%20Uninstall%20the%20model%20provider%20plugin%20%28e.g.%2C%20deepseek%29%20through%20the%20Dify%20UI%0A2.%20Restart%20the%20plugin%20daemon%20container%3A%0A%20%20%20%60%60%60bash%0A%20%20%20docker%20restart%20docker-plugin_daemon-1%0A%20%20%20%60%60%60%0A3.%20Reinstall%20the%20plugin%20from%20the%20marketplace%0A%0A%2A%2AAlternative%3A%20Remove%20Broken%20Virtual%20Environment%2A%2A%0A1.%20Enter%20the%20plugin%20daemon%20container%3A%0A%20%20%20%60%60%60bash%0A%20%20%20docker%20exec%20-it%20docker-plugin_daemon-1%20bash%0A%20%20%20%60%60%60%0A2.%20Find%20and%20remove%20broken%20%60.venv%60%20directories%3A%0A%20%20%20%60%60%60bash%0A%20%20%20VENV%3D%24%28find%20/app/storage%20-maxdepth%205%20-type%20d%20-name%20%27.venv%27%20%7C%20head%20-n1%29%0A%20%20%20rm%20-rf%20%22%24VENV%22%0A%20%20%20%60%60%60%0A3.%20Restart%20the%20plugin%20daemon%0A%0A%2A%2AFor%20Agent%20Nodes%20Specifically%20%28v1.13.0%29%2A%2A%0AThere%27s%20a%20%5Bknown%20issue%5D%28https%3A//github.com/langgenius/dify/issues/32253%29%20where%20workflows%20with%20agent%20nodes%20may%20fail%20after%20upgrading.%20Try%20removing%20and%20re-adding%20the%20agent%20node%20in%20your%20workflow%20to%20refresh%20plugin%20references.%0A%0AThe%20%22failed%20to%20create%20PluginUniqueIdentifier%22%20error%20in%20your%20logs%20suggests%20%5Bdatabase%20inconsistency%20between%20plugin%20records%20and%20actual%20files%5D%28https%3A//github.com/langgenius/dify/issues/31303%29%20-%20reinstalling%20the%20plugins%20should%20resolve%20this.)&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/32321)
yindo commented 2026-02-21 20:16:13 -05:00
Author
Owner
Copy Link
Copy Source

@kanjoe888 commented on GitHub (Feb 14, 2026):

when i reinstall ollama plug , it report error : failed to launch plugin: fork/exec /app/storage/cwd/langgenius/ollama-0.1.2@fcf107badccaf57948634ad2c557d393c3894138d83f4eb3f959e9a1d3a86512/.venv/bin/python: exec format error

how to resolver it ?

@kanjoe888 commented on GitHub (Feb 14, 2026): when i reinstall ollama plug , it report error : failed to launch plugin: fork/exec /app/storage/cwd/langgenius/ollama-0.1.2@fcf107badccaf57948634ad2c557d393c3894138d83f4eb3f959e9a1d3a86512/.venv/bin/python: exec format error how to resolver it ?
yindo commented 2026-02-21 20:16:13 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 14, 2026):

The "exec format error" is typically caused by Docker resource constraints or an architecture mismatch in the plugin's virtual environment. Try these solutions:

1. Clear the old virtual environment and reinstall:

docker exec -it docker-plugin_daemon-1 bash
rm -rf /app/storage/cwd/langgenius/ollama-*/.venv
exit
docker restart docker-plugin_daemon-1

Then reinstall the ollama plugin from the UI.

2. Add resource limits to your docker-compose.yaml (if resource-related):

plugin_daemon:
  deploy:
    resources:
      limits:
        cpus: '2'
        memory: 4G
  ulimits:
    nproc: 65535
    nofile:
      soft: 65535
      hard: 65535
  security_opt:
    - seccomp:unconfined

3. Add timeout settings in the plugin_daemon environment:

environment:
  PYTHON_ENV_INIT_TIMEOUT: 320

After making changes, run docker compose up -d to apply them.

The error suggests the Python binary in the .venv was built for a different CPU architecture than your container is running. Deleting the .venv directory should force a fresh virtual environment rebuild with the correct architecture.

To reply, just mention @dosu.

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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 14, 2026): <!-- Answer --> The "exec format error" is typically caused by **Docker resource constraints** or an **architecture mismatch** in the plugin's virtual environment. Try these solutions: **1. Clear the old virtual environment and reinstall:** ```bash docker exec -it docker-plugin_daemon-1 bash rm -rf /app/storage/cwd/langgenius/ollama-*/.venv exit docker restart docker-plugin_daemon-1 ``` Then reinstall the ollama plugin from the UI. **2. Add resource limits to your `docker-compose.yaml`** (if resource-related): ```yaml plugin_daemon: deploy: resources: limits: cpus: '2' memory: 4G ulimits: nproc: 65535 nofile: soft: 65535 hard: 65535 security_opt: - seccomp:unconfined ``` **3. Add timeout settings** in the plugin_daemon environment: ```yaml environment: PYTHON_ENV_INIT_TIMEOUT: 320 ``` After making changes, run `docker compose up -d` to apply them. The error suggests the Python binary in the `.venv` was built for a different CPU architecture than your container is running. Deleting the `.venv` directory should force a fresh virtual environment rebuild with the correct architecture. <!-- 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/bb05c5f7-e274-44d1-adbd-f7095c3e97cb?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/bb05c5f7-e274-44d1-adbd-f7095c3e97cb?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/bb05c5f7-e274-44d1-adbd-f7095c3e97cb?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/bb05c5f7-e274-44d1-adbd-f7095c3e97cb?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/bb05c5f7-e274-44d1-adbd-f7095c3e97cb?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/bb05c5f7-e274-44d1-adbd-f7095c3e97cb?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/bb05c5f7-e274-44d1-adbd-f7095c3e97cb?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20%22exec%20format%20error%22%20is%20typically%20caused%20by%20%2A%2ADocker%20resource%20constraints%2A%2A%20or%20an%20%2A%2Aarchitecture%20mismatch%2A%2A%20in%20the%20plugin%27s%20virtual%20environment.%20Try%20these%20solutions%3A%0A%0A%2A%2A1.%20Clear%20the%20old%20virtual%20environment%20and%20reinstall%3A%2A%2A%0A%60%60%60bash%0Adocker%20exec%20-it%20docker-plugin_daemon-1%20bash%0Arm%20-rf%20/app/storage/cwd/langgenius/ollama-%2A/.venv%0Aexit%0Adocker%20restart%20docker-plugin_daemon-1%0A%60%60%60%0AThen%20reinstall%20the%20ollama%20plugin%20from%20the%20UI.%0A%0A%2A%2A2.%20Add%20resource%20limits%20to%20your%20%60docker-compose.yaml%60%2A%2A%20%28if%20resource-related%29%3A%0A%60%60%60yaml%0Aplugin_daemon%3A%0A%20%20deploy%3A%0A%20%20%20%20resources%3A%0A%20%20%20%20%20%20limits%3A%0A%20%20%20%20%20%20%20%20cpus%3A%20%272%27%0A%20%20%20%20%20%20%20%20memory%3A%204G%0A%20%20ulimits%3A%0A%20%20%20%20nproc%3A%2065535%0A%20%20%20%20nofile%3A%0A%20%20%20%20%20%20soft%3A%2065535%0A%20%20%20%20%20%20hard%3A%2065535%0A%20%20security_opt%3A%0A%20%20%20%20-%20seccomp%3Aunconfined%0A%60%60%60%0A%0A%2A%2A3.%20Add%20timeout%20settings%2A%2A%20in%20the%20plugin_daemon%20environment%3A%0A%60%60%60yaml%0Aenvironment%3A%0A%20%20PYTHON_ENV_INIT_TIMEOUT%3A%20320%0A%60%60%60%0A%0AAfter%20making%20changes%2C%20run%20%60docker%20compose%20up%20-d%60%20to%20apply%20them.%0A%0AThe%20error%20suggests%20the%20Python%20binary%20in%20the%20%60.venv%60%20was%20built%20for%20a%20different%20CPU%20architecture%20than%20your%20container%20is%20running.%20Deleting%20the%20%60.venv%60%20directory%20should%20force%20a%20fresh%20virtual%20environment%20rebuild%20with%20the%20correct%20architecture.)&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/32321)
yindo commented 2026-02-21 20:16:13 -05:00
Author
Owner
Copy Link
Copy Source

@kanjoe888 commented on GitHub (Feb 14, 2026):

when i execute last steps, now i had reinstalled ollama plugin surcessfully.

now i reinstall xinference plugin, it report error:
failed to launch plugin: fork/exec /app/storage/cwd/langgenius/xinference-0.0.9@70724a48be26657dfb7b3f18a378e78ef7784e97e3824da4cf1d76c79c6b547d/.venv/bin/python: exec format error

@kanjoe888 commented on GitHub (Feb 14, 2026): when i execute last steps, now i had reinstalled ollama plugin surcessfully. now i reinstall xinference plugin, it report error: failed to launch plugin: fork/exec /app/storage/cwd/langgenius/xinference-0.0.9@70724a48be26657dfb7b3f18a378e78ef7784e97e3824da4cf1d76c79c6b547d/.venv/bin/python: exec format error
yindo commented 2026-02-21 20:16:13 -05:00
Author
Owner
Copy Link
Copy Source

@kanjoe888 commented on GitHub (Feb 14, 2026):

Most Reliable Fix: Uninstall and Reinstall the Plugin

Uninstall the model provider plugin (e.g., deepseek) through the Dify UI
Restart the plugin daemon container:
docker restart docker-plugin_daemon-1
Reinstall the plugin from the marketplace
Alternative: Remove Broken Virtual Environment

Enter the plugin daemon container:
docker exec -it docker-plugin_daemon-1 bash
Find and remove broken .venv directories:
VENV=$(find /app/storage -maxdepth 5 -type d -name '.venv' | head -n1)
rm -rf "$VENV"
Restart the plugin daemon
=================》
I have reinstalled all plugins according to the instructions, but the problem still persists

@kanjoe888 commented on GitHub (Feb 14, 2026): Most Reliable Fix: Uninstall and Reinstall the Plugin Uninstall the model provider plugin (e.g., deepseek) through the Dify UI Restart the plugin daemon container: docker restart docker-plugin_daemon-1 Reinstall the plugin from the marketplace Alternative: Remove Broken Virtual Environment Enter the plugin daemon container: docker exec -it docker-plugin_daemon-1 bash Find and remove broken .venv directories: VENV=$(find /app/storage -maxdepth 5 -type d -name '.venv' | head -n1) rm -rf "$VENV" Restart the plugin daemon =================》 I have reinstalled all plugins according to the instructions, but the problem still persists
yindo commented 2026-02-21 20:16:13 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 14, 2026):

The persistent "exec format error" strongly indicates a Docker architecture mismatch - the Python binary is compiled for a different CPU architecture than what your plugin daemon is running.

First, check if this is an architecture issue:

# Check your host architecture
uname -m

# Check plugin daemon architecture
docker exec docker-plugin_daemon-1 uname -m

If these don't match (e.g., one shows aarch64/ARM and other shows x86_64), that's the root cause.

Complete reset (when .venv cleanup alone doesn't work):

  1. Clear ALL plugin storage:
docker exec -it docker-plugin_daemon-1 bash -c "rm -rf /app/storage/cwd/langgenius/* /app/storage/cwd/plugins/*"
  1. Also clean database records (connect to your PostgreSQL):
DELETE FROM plugin_installations;
DELETE FROM ai_model_installations;
  1. Restart the daemon:
docker restart docker-plugin_daemon-1
  1. Then reinstall plugins from the UI.

Note: Dify does not officially support ARM architecture for self-hosted Docker. If you're running on ARM (like Apple Silicon or Raspberry Pi), this may be a known limitation causing these errors.

To reply, just mention @dosu.

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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 14, 2026): <!-- Answer --> The persistent "exec format error" strongly indicates a **Docker architecture mismatch** - the Python binary is compiled for a different CPU architecture than what your plugin daemon is running. **First, check if this is an architecture issue:** ```bash # Check your host architecture uname -m # Check plugin daemon architecture docker exec docker-plugin_daemon-1 uname -m ``` If these don't match (e.g., one shows `aarch64`/ARM and other shows `x86_64`), that's the root cause. **Complete reset (when .venv cleanup alone doesn't work):** 1. Clear ALL plugin storage: ```bash docker exec -it docker-plugin_daemon-1 bash -c "rm -rf /app/storage/cwd/langgenius/* /app/storage/cwd/plugins/*" ``` 2. Also clean database records (connect to your PostgreSQL): ```sql DELETE FROM plugin_installations; DELETE FROM ai_model_installations; ``` 3. Restart the daemon: ```bash docker restart docker-plugin_daemon-1 ``` 4. Then reinstall plugins from the UI. **Note:** [Dify does not officially support ARM architecture](https://github.com/langgenius/dify/issues/30662) for self-hosted Docker. If you're running on ARM (like Apple Silicon or Raspberry Pi), this may be a known limitation causing these errors. <!-- 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/f3bccf8b-b8c7-4299-9834-7edc6e2ee847?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f3bccf8b-b8c7-4299-9834-7edc6e2ee847?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f3bccf8b-b8c7-4299-9834-7edc6e2ee847?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f3bccf8b-b8c7-4299-9834-7edc6e2ee847?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f3bccf8b-b8c7-4299-9834-7edc6e2ee847?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f3bccf8b-b8c7-4299-9834-7edc6e2ee847?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f3bccf8b-b8c7-4299-9834-7edc6e2ee847?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20persistent%20%22exec%20format%20error%22%20strongly%20indicates%20a%20%2A%2ADocker%20architecture%20mismatch%2A%2A%20-%20the%20Python%20binary%20is%20compiled%20for%20a%20different%20CPU%20architecture%20than%20what%20your%20plugin%20daemon%20is%20running.%0A%0A%2A%2AFirst%2C%20check%20if%20this%20is%20an%20architecture%20issue%3A%2A%2A%0A%60%60%60bash%0A%23%20Check%20your%20host%20architecture%0Auname%20-m%0A%0A%23%20Check%20plugin%20daemon%20architecture%0Adocker%20exec%20docker-plugin_daemon-1%20uname%20-m%0A%60%60%60%0A%0AIf%20these%20don%27t%20match%20%28e.g.%2C%20one%20shows%20%60aarch64%60/ARM%20and%20other%20shows%20%60x86_64%60%29%2C%20that%27s%20the%20root%20cause.%0A%0A%2A%2AComplete%20reset%20%28when%20.venv%20cleanup%20alone%20doesn%27t%20work%29%3A%2A%2A%0A%0A1.%20Clear%20ALL%20plugin%20storage%3A%0A%60%60%60bash%0Adocker%20exec%20-it%20docker-plugin_daemon-1%20bash%20-c%20%22rm%20-rf%20/app/storage/cwd/langgenius/%2A%20/app/storage/cwd/plugins/%2A%22%0A%60%60%60%0A%0A2.%20Also%20clean%20database%20records%20%28connect%20to%20your%20PostgreSQL%29%3A%0A%60%60%60sql%0ADELETE%20FROM%20plugin_installations%3B%0ADELETE%20FROM%20ai_model_installations%3B%0A%60%60%60%0A%0A3.%20Restart%20the%20daemon%3A%0A%60%60%60bash%0Adocker%20restart%20docker-plugin_daemon-1%0A%60%60%60%0A%0A4.%20Then%20reinstall%20plugins%20from%20the%20UI.%0A%0A%2A%2ANote%3A%2A%2A%20%5BDify%20does%20not%20officially%20support%20ARM%20architecture%5D%28https%3A//github.com/langgenius/dify/issues/30662%29%20for%20self-hosted%20Docker.%20If%20you%27re%20running%20on%20ARM%20%28like%20Apple%20Silicon%20or%20Raspberry%20Pi%29%2C%20this%20may%20be%20a%20known%20limitation%20causing%20these%20errors.)&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/32321)
yindo commented 2026-02-21 20:16:13 -05:00
Author
Owner
Copy Link
Copy Source

@kanjoe888 commented on GitHub (Feb 14, 2026):

I had check the architecture is same.

I have reinstalled all plugins according to the instructions, but the problem still persists

help 。。。。。
=================》
Most Reliable Fix: Uninstall and Reinstall the Plugin

Uninstall the model provider plugin (e.g., deepseek) through the Dify UI
Restart the plugin daemon container:
docker restart docker-plugin_daemon-1
Reinstall the plugin from the marketplace
Alternative: Remove Broken Virtual Environment

Enter the plugin daemon container:
docker exec -it docker-plugin_daemon-1 bash
Find and remove broken .venv directories:
VENV=$(find /app/storage -maxdepth 5 -type d -name '.venv' | head -n1)
rm -rf "$VENV"
Restart the plugin daemon

@kanjoe888 commented on GitHub (Feb 14, 2026): I had check the architecture is same. I have reinstalled all plugins according to the instructions, but the problem still persists help 。。。。。 =================》 Most Reliable Fix: Uninstall and Reinstall the Plugin Uninstall the model provider plugin (e.g., deepseek) through the Dify UI Restart the plugin daemon container: docker restart docker-plugin_daemon-1 Reinstall the plugin from the marketplace Alternative: Remove Broken Virtual Environment Enter the plugin daemon container: docker exec -it docker-plugin_daemon-1 bash Find and remove broken .venv directories: VENV=$(find /app/storage -maxdepth 5 -type d -name '.venv' | head -n1) rm -rf "$VENV" Restart the plugin daemon
yindo commented 2026-02-21 20:16:13 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 14, 2026):

Since architecture matches and reinstalling didn't help, try these additional fixes:

1. Check for noexec mount flag (common cause):

mount | grep storage

If you see noexec, that's the problem. Remount without it.

2. Add Docker security options to docker-compose.yaml:

plugin_daemon:
  security_opt:
    - seccomp:unconfined

3. Fix directory permissions:

sudo chown -R 1000:1000 ./volumes/plugin_daemon
sudo chmod -R 775 ./volumes/plugin_daemon

4. Pull a fresh plugin daemon image (resolves hidden corruption):

docker compose down
docker rmi langgenius/dify-plugin-daemon:0.5.3-local
docker compose up -d

5. Clear ALL .venv directories (not just one):

docker exec -it docker-plugin_daemon-1 sh -c "find /app/storage -type d -name '.venv' -exec rm -rf {} + 2>/dev/null || true"
docker restart docker-plugin_daemon-1

Also, if you ever migrated your Docker volumes using zip, that breaks symlinks. Always use tar for Docker volume backups.

After applying these, try reinstalling the plugins again from the UI.

To reply, just mention @dosu.

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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Feb 14, 2026): <!-- Answer --> Since architecture matches and reinstalling didn't help, try these additional fixes: **1. Check for `noexec` mount flag** (common cause): ```bash mount | grep storage ``` If you see `noexec`, that's the problem. [Remount without it](https://github.com/langgenius/dify/issues/17456). **2. Add Docker security options** to `docker-compose.yaml`: ```yaml plugin_daemon: security_opt: - seccomp:unconfined ``` **3. Fix directory permissions:** ```bash sudo chown -R 1000:1000 ./volumes/plugin_daemon sudo chmod -R 775 ./volumes/plugin_daemon ``` **4. Pull a fresh plugin daemon image** (resolves hidden corruption): ```bash docker compose down docker rmi langgenius/dify-plugin-daemon:0.5.3-local docker compose up -d ``` **5. Clear ALL .venv directories** (not just one): ```bash docker exec -it docker-plugin_daemon-1 sh -c "find /app/storage -type d -name '.venv' -exec rm -rf {} + 2>/dev/null || true" docker restart docker-plugin_daemon-1 ``` Also, if you ever migrated your Docker volumes using **zip**, that breaks symlinks. [Always use `tar` for Docker volume backups](https://github.com/langgenius/dify/discussions/30561#discussioncomment-15411670). After applying these, try reinstalling the plugins again from the UI. <!-- 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/a46b0511-571b-4326-8775-f742a9af6d88?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/a46b0511-571b-4326-8775-f742a9af6d88?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/a46b0511-571b-4326-8775-f742a9af6d88?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/a46b0511-571b-4326-8775-f742a9af6d88?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a46b0511-571b-4326-8775-f742a9af6d88?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/a46b0511-571b-4326-8775-f742a9af6d88?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a46b0511-571b-4326-8775-f742a9af6d88?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Since%20architecture%20matches%20and%20reinstalling%20didn%27t%20help%2C%20try%20these%20additional%20fixes%3A%0A%0A%2A%2A1.%20Check%20for%20%60noexec%60%20mount%20flag%2A%2A%20%28common%20cause%29%3A%0A%60%60%60bash%0Amount%20%7C%20grep%20storage%0A%60%60%60%0AIf%20you%20see%20%60noexec%60%2C%20that%27s%20the%20problem.%20%5BRemount%20without%20it%5D%28https%3A//github.com/langgenius/dify/issues/17456%29.%0A%0A%2A%2A2.%20Add%20Docker%20security%20options%2A%2A%20to%20%60docker-compose.yaml%60%3A%0A%60%60%60yaml%0Aplugin_daemon%3A%0A%20%20security_opt%3A%0A%20%20%20%20-%20seccomp%3Aunconfined%0A%60%60%60%0A%0A%2A%2A3.%20Fix%20directory%20permissions%3A%2A%2A%0A%60%60%60bash%0Asudo%20chown%20-R%201000%3A1000%20./volumes/plugin_daemon%0Asudo%20chmod%20-R%20775%20./volumes/plugin_daemon%0A%60%60%60%0A%0A%2A%2A4.%20Pull%20a%20fresh%20plugin%20daemon%20image%2A%2A%20%28resolves%20hidden%20corruption%29%3A%0A%60%60%60bash%0Adocker%20compose%20down%0Adocker%20rmi%20langgenius/dify-plugin-daemon%3A0.5.3-local%0Adocker%20compose%20up%20-d%0A%60%60%60%0A%0A%2A%2A5.%20Clear%20ALL%20.venv%20directories%2A%2A%20%28not%20just%20one%29%3A%0A%60%60%60bash%0Adocker%20exec%20-it%20docker-plugin_daemon-1%20sh%20-c%20%22find%20/app/storage%20-type%20d%20-name%20%27.venv%27%20-exec%20rm%20-rf%20%7B%7D%20%2B%202%3E/dev/null%20%7C%7C%20true%22%0Adocker%20restart%20docker-plugin_daemon-1%0A%60%60%60%0A%0AAlso%2C%20if%20you%20ever%20migrated%20your%20Docker%20volumes%20using%20%2A%2Azip%2A%2A%2C%20that%20breaks%20symlinks.%20%5BAlways%20use%20%60tar%60%20for%20Docker%20volume%20backups%5D%28https%3A//github.com/langgenius/dify/discussions/30561%23discussioncomment-15411670%29.%0A%0AAfter%20applying%20these%2C%20try%20reinstalling%20the%20plugins%20again%20from%20the%20UI.)&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/32321)
yindo commented 2026-02-21 20:16:14 -05:00
Author
Owner
Copy Link
Copy Source

@kanjoe888 commented on GitHub (Feb 14, 2026):

After following the above steps, my issue still persists.

I believe the focus should be on why the agent node in the workflow is problematic. If the LLM node in chatflow works normally, it should rule out the possibility that the issue is caused by the plugin. Can we identify the problem from the logs?

@kanjoe888 commented on GitHub (Feb 14, 2026): After following the above steps, my issue still persists. I believe the focus should be on why the agent node in the workflow is problematic. If the LLM node in chatflow works normally, it should rule out the possibility that the issue is caused by the plugin. Can we identify the problem from the logs?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
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#22224
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?