Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

We have upgraded to version v1.0.1, but in the plugin marketplace, issues such as "get custom model schema failed," "PluginDaemonInternalServerError: no available node," and "plugin not found" still occur. #15843

Open
5 tasks done
lanqy123 opened this issue Mar 14, 2025 · 1 comment
Labels
🐞 bug Something isn't working

Comments

@lanqy123
Copy link

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

v1.0.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

@dosubot dosubot bot added the 🐞 bug Something isn't working label Mar 14, 2025
Copy link

dosubot bot commented Mar 14, 2025

To address the issues you're encountering after upgrading to version v1.0.1, such as "get custom model schema failed," "PluginDaemonInternalServerError: no available node," and "plugin not found," you can try the following steps:

  1. Clear Plugin Data: Execute these SQL commands in the dify_plugin database to clear existing plugin data:

    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;
  2. Clear Plugin Directories: Remove the contents of the following directories:

    • /app/storage/cwd/plugins/plugin
    • /app/storage/cwd/plugins/plugin-working
    • /app/storage/cwd/plugins/persistence
    • /app/storage/cwd/plugins/plugin-root
  3. Restart the Plugin Daemon Service: This can help reinitialize the plugin system.

  4. Reinstall the Plugins: After clearing the data and directories, reinstall the necessary plugins.

If these steps do not resolve the issues, consider downgrading the dify-api and dify-web services to version 0.15.3 as a temporary workaround, as this has been confirmed to resolve similar issues related to the plugin daemon's database connectivity [1][2].

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant