dify upload file to knowledge database, cannot segment

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

1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

上传文件到知识库，无法分段，日志显示：

[ERROR]PluginDaemonInternalServerError: no available node, plugin not found
2025-03-05T03:41:37.836645277Z goroutine 614 [running]:
runtime/debug.Stack()
2025-03-05T03:41:37.836656101Z 	/usr/local/go/src/runtime/debug/stack.go:24 +0x5e
github.com/langgenius/dify-plugin-daemon/internal/types/exception.InternalServerError({0x180b640, 0xc0016ba320})
2025-03-05T03:41:37.836675030Z 	/app/internal/types/exception/factory.go:27 +0x27
2025-03-05T03:41:37.836680255Z github.com/langgenius/dify-plugin-daemon/internal/server.(*App).redirectPluginInvokeByPluginIdentifier(0xc0001160d8, 0xc000e5a700, {0xc0005265a0?, 0xe98ebf?}, {0x180b640, 0xc0016ba2d0})
2025-03-05T03:41:37.836685310Z 	/app/internal/server/middleware.go:120 +0xef
2025-03-05T03:41:37.836690140Z github.com/langgenius/dify-plugin-daemon/internal/server.(*App).pluginDispatchGroup.(*App).RedirectPluginInvoke.func2(0xc000e5a700)
	/app/internal/server/middleware.go:94 +0x95
2025-03-05T03:41:37.836704123Z github.com/gin-gonic/gin.(*Context).Next(0xc000e5a700)
2025-03-05T03:41:37.836709057Z 	/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:185 +0x2b
2025-03-05T03:41:37.836714299Z github.com/langgenius/dify-plugin-daemon/internal/server.(*App).pluginDispatchGroup.(*App).FetchPluginInstallation.func1(0xc000e5a700)
	/app/internal/server/middleware.go:66 +0x2f2
github.com/gin-gonic/gin.(*Context).Next(0xc000e5a700)
2025-03-05T03:41:37.836825922Z 	/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:185 +0x2b
2025-03-05T03:41:37.836838806Z github.com/langgenius/dify-plugin-daemon/internal/server.(*App).pluginGroup.CheckingKey.func1(0xc000e5a700)
2025-03-05T03:41:37.836851310Z 	/app/internal/server/middleware.go:24 +0x95
github.com/gin-gonic/gin.(*Context).Next(...)
	/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:185
2025-03-05T03:41:37.836888152Z github.com/gin-gonic/gin.CustomRecoveryWithWriter.func1(0xc000e5a700)
	/go/pkg/mod/github.com/gin-gonic/[email protected]/recovery.go:102 +0x7a
2025-03-05T03:41:37.836912964Z github.com/gin-gonic/gin.(*Context).Next(...)
2025-03-05T03:41:37.836925222Z 	/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:185
github.com/gin-gonic/gin.LoggerWithConfig.func1(0xc000e5a700)
2025-03-05T03:41:37.836950097Z 	/go/pkg/mod/github.com/gin-gonic/[email protected]/logger.go:249 +0xe5
2025-03-05T03:41:37.836963147Z github.com/gin-gonic/gin.(*Context).Next(...)
2025-03-05T03:41:37.836975570Z 	/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:185
github.com/gin-gonic/gin.(*Engine).handleHTTPRequest(0xc0001ae680, 0xc000e5a700)
	/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:633 +0x892
2025-03-05T03:41:37.837018099Z github.com/gin-gonic/gin.(*Engine).ServeHTTP(0xc0001ae680, {0x181dac0, 0xc0001de2a0}, 0xc001f10120)
	/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:589 +0x1b2
2025-03-05T03:41:37.837043848Z net/http.serverHandler.ServeHTTP({0x1813868?}, {0x181dac0?, 0xc0001de2a0?}, 0x6?)
	/usr/local/go/src/net/http/server.go:3142 +0x8e
net/http.(*conn).serve(0xc000626000, {0x1820270, 0xc0008821b0})
	/usr/local/go/src/net/http/server.go:2044 +0x5e8
2025-03-05T03:41:37.837110232Z created by net/http.(*Server).Serve in goroutine 88
2025-03-05T03:41:37.837122793Z 	/usr/local/go/src/net/http/server.go:3290 +0x4b4
2025-03-05T03:41:37.837135365Z 
[GIN] 2025/03/05 - 03:41:37 | 404 |    4.093288ms |     10.42.0.112 | POST     "/plugin/dd1a2b70-036d-49a6-ae01-7dbbe6c7604d/dispatch/text_embedding/num_tokens"

✔️ Expected Behavior

No response

❌ Actual Behavior

Mar 05 '25 03:03 jenven

I found a similar unsolved discussion regarding a "Knowledge base file upload text segmentation and cleaning error" ^[1].

To resolve the "PluginDaemonInternalServerError: no available node, plugin not found" error in Dify version 1.0.0 when uploading a file to the knowledge database in a self-hosted Docker environment, you can try the following solutions:

Add the following line to your docker-compose.yaml file to increase the timeout for Python environment initialization:
```
PYTHON_ENV_INIT_TIMEOUT: 320
```
If the first solution doesn't work, follow these steps to clear and reinstall the plugins:
- Clear plugin data from the database by executing these SQL commands in the dify_plugin database:
```
delete from plugin_installations where plugin_unique_identifier is not null;
delete from plugin_declarations where plugin_unique_identifier is not null;
delete from ai_model_installations where plugin_unique_identifier is not null;
delete from plugins where plugin_unique_identifier is not null;
```
- Clear the plugin directories in these locations:
  - /app/storage/cwd/plugins/plugin
  - /app/storage/cwd/plugins/plugin-working
  - /app/storage/cwd/plugins/persistence
  - /app/storage/cwd/plugins/plugin-root
- Restart the plugin daemon service.
- Reinstall the plugins from the marketplace.

These steps should help resolve the error by ensuring that the plugin installation process completes successfully ^[2]^[3].

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}

Mar 05 '25 03:03 dosubot[bot]

Please try to remove the installed plugin and install it again.

Mar 05 '25 04:03 crazywoola

Hi, @jenven. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

You reported a bug in Dify version 1.0.0 related to file upload segmentation in a self-hosted Docker setup.
Error logs indicated a "PluginDaemonInternalServerError" due to a missing plugin node.
I suggested increasing the Python environment initialization timeout and provided steps to clear and reinstall plugins.
Crazywoola also recommended removing and reinstalling the plugin.
The issue appears to be resolved by following these suggestions.

Next Steps:

Please confirm if this issue is still relevant to the latest version of the Dify repository. If so, you can keep the discussion open by commenting here.
If there are no further updates, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

Apr 05 '25 16:04 dosubot[bot]