search

grafana / grafana-image-renderer

A Grafana backend plugin that handles rendering of panels & dashboards to PNGs using headless browser (Chromium/Chrome)
Apache License 2.0
385 stars 156 forks source link

plugin-linux-x64-glibc-no-chromium fails #475

Open athaga opened 1 year ago

athaga commented 1 year ago

I just uppdated to v.3.8.4 

Error: ✗ *rendering.RenderingService run error: Unrecognized remote plugin message: 
This usually means
  the plugin was not compiled for this architecture,
  the plugin is missing dynamic-link libraries necessary to run,
  the plugin is not executable by this process due to file permissions, or
  the plugin failed to negotiate the initial go-plugin protocol handshake

Additional notes about plugin:
  Path: /var/lib/grafana/plugins/grafana-image-renderer/plugin_start_linux_amd64
  Mode: -rwxr-xr-x
  Owner: 472 [grafana] (current: 472 [grafana])
  Group: 0 [root] (current: 0 [root])
  ELF architecture: EM_X86_64 (current architecture: amd64)
athaga commented 1 year ago

note the plugin-linux-x64-glibc is also installed grafana is 10.0.2 it runs on docker alpine is 3.17.4

AgnesToulet commented 1 year ago

Hi! Did you update from 3.8.3 or from an older version? Do you have any logs prior to that that could explain the error?

Also, please note that from the documentation:

This plugin is not compatible with the current Grafana Docker image and requires additional system-level dependencies. We recommend setting up another Docker container for rendering and using remote rendering instead. For instruction, refer to Run in Docker.

If you still want to install the plugin with the Grafana Docker image, refer to the instructions on building a custom Grafana image in Grafana Docker documentation.

Have you followed the documentation to build a custom Grafana image?

You should have only one plugin installed, else we won't be able to know which one is failing exactly.

Lucareful commented 2 months ago

i have the same problem, this is some about logs.


  ELF architecture: EM_X86_64 (current architecture: amd64)
  Group: 0 [root] (current: 0 [root])
  Owner: 0 [root] (current: 0 [root])
  Mode: -rwxr-xr-x
  Path: /var/lib/grafana/plugins/grafana-image-renderer/plugin_start_linux_amd64
Additional notes about plugin:

  the plugin failed to negotiate the initial go-plugin protocol handshake
  the plugin is not executable by this process due to file permissions, or
  the plugin is missing dynamic-link libraries necessary to run,
  the plugin was not compiled for this architecture,
This usually means
Failed to read any lines from plugin's stdout
Seokyun-Ha commented 1 month ago

I have experienced same thing with grafana v10.2.3 and plugin 3.11.6.

redm123 commented 1 week ago

Came here as I just upgraded Grafana from an older version to 11 and just wanted to enable images in Alerts again... and ran into this problem. Honestly, I don't know if I should laugh or cry ... 16GB RAM or more for getting an image of a graph?? Insane. And then it doesn't even work, in the official Docker image! Running a separate docker service for getting an image of a graph?? Build an own docker image for getting an image of a graph?? Sorry to say, that's so ridiculous... (well, actually it matches what I've seen from current Grafana so far, compared to earlier versions, which I really liked... horrible UI, over engineered, overly complex for simple things...). Guess time to look for something else..