-
Notifications
You must be signed in to change notification settings - Fork 462
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
Zabbix Plugin does not load on windows #1785
Comments
hi @patokav , some ideas: another idea: in the beginning you wrote:
the grafana-version should have no effect on the plugin's compatibility with Zabbix. so, if you take the Grafana version where the plugin was still working, and upgrade the plugin there to the newest plugin version, it should work. (of course, we'd like to find out why it does not work on the newest grafana-version, but we have to start somewhere). what was the last working grafana-version? could you try what i described? (upgrade the zabbix-plugin on that grafana-vserion to newest) |
Hi @gabor thanks for responding, I don't see an option to create a plugin configuration but I tried creating a new data source with the same error. I also tried disabling the direct DB connection but still the same. |
hi, i tried the combination of Grafana10.3.1, the grafana-zabbix-plugin version 4.4.5, and zabbix6.4, and was able to connect to zabbix (on a linux server.. well, using docker). the error message you are getting ( i see this is running on windows, may i ask, is the grafana-server running on windows, and also the zabbix-server running on windows? |
thanks for the info @patokav . i was able to reproduce this. i think the plugin does not currently work on windows. |
after more investigation, this seems to be a problem in grafana itself, and not specific to the zabbix plugin. i created a bugreport in grafana at grafana/grafana#83416, i recommend following that issue. i will close this isuse, because the fix will probably happen in core grafana. if that's not the case, we can always reopen this issue later. thanks for your help in investigating this 👍 |
hi, this is fixed now in the current zabbix plugin version ( |
Describe the bug
When trying to create a Zabbix data source I get the prompt "plugin unavailable". The plugin was working on older versions of Grafana but I was unable to connect to the zabbix database due to the "user" to "username" change on login with the php file. Would modifying the php file work for this or would it break things in zabbix?
I have also tried different versions of the plugin recommended by other issues on the GitHub with no luck, I installed the plugin using Grafana-cli each time
I have also tried executing gpx_zabbix-plugin_windows_amd64.exe as recommended in other posts
I have tried setting the following in defaults.ini
allow_loading_unsigned_plugins = alexanderzobnin-zabbix-app,alexanderzobnin-zabbix-datasource
enable_alpha = true
app_tls_skip_verify_insecure = true
And I restarted the server after making any changes/plugin installs
Expected behaviour
The database should test connection, so far that is not happening, it is just saving - to note the MySQL data source being used is tested and working
Screenshots
Logs
logger=context userId=1 orgId=1 uname=admin t=2024-01-24T16:05:00.2121184Z level=info msg="Request Completed" method=GET path=/api/live/ws status=-1 remote_addr=[::1] time_ms=1 duration=1.4059ms size=0 referer= handler=/api/live/ws
logger=context userId=1 orgId=1 uname=admin t=2024-01-24T16:05:05.0657805Z level=warn msg="Plugin unavailable" error="plugin unavailable" traceID=
logger=context userId=1 orgId=1 uname=admin t=2024-01-24T16:05:05.0657805Z level=error msg="Request Completed" method=POST path=/api/datasources/3/resources/zabbix-api status=503 remote_addr=[::1] time_ms=3 duration=3.2825ms size=46 referer=http://localhost:3000/datasources/edit/da3277fb-2c73-4738-a147-5fe955e9a7c8 handler=/api/datasources/:id/resources/*
Software versions
Windows 11 23H2
I have also tried Grafana V 10.3.1, every other version the same, and getting the same issue
The text was updated successfully, but these errors were encountered: