-
Notifications
You must be signed in to change notification settings - Fork 28
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
msg="Failed to start plugin" after update to 0.5.0 #72
Comments
Thanks for reporting this! 🙏 Can I ask what Grafana version you're running? |
of course you can. 😊
my version is Grafana v7.5.7 (91de51771c).
…________________________________
Von: Marcus Olsson ***@***.***>
Gesendet: Freitag, 28. Mai 2021 11:52
An: marcusolsson/grafana-csv-datasource
Cc: Boehm, Andreas; Author
Betreff: Re: [marcusolsson/grafana-csv-datasource] msg="Failed to start plugin" after update to 0.5.0 (#72)
Thanks for reporting this! 🙏 Can I ask what Grafana version you're running?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#72 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AT7SF4F2X2SHCAZ5KBH27XTTP5RWNANCNFSM45V3JQRQ>.
|
I did get the plugin run again. I removed all other non default plugins, including csv plugin, and added csv plugin afterwards. |
thanks a lot for supporting my case. |
Sorry for the late response here, but I'm happy to hear you got it working! |
I updated the marcusolsson-csv-datasource plugin to try to use the new regex support in the field names.
After the update, the plugin does not start anymore. The error message is the following.
May 28 08:10:19 linux-7x33.suse grafana-server[32040]: t=2021-05-28T08:10:19+0200 lvl=eror msg="Failed to start plugin" logger=plugins.backend pluginId=grafana-csv-plugin error="Unrecognized remote plugin message: \n\nThis usually means that the plugin is either invalid or simply\nneeds to be recompiled to support the latest protocol."
What did I wrong, or what can I do to resolve this?
I tried to remove and re-add the plugin, but I got no change. :-(
Thank you very much for supporting.
The text was updated successfully, but these errors were encountered: