grafana-image-renderer: [3.11.1+] rendering failed: Error: Failed to launch the browser process

What happened: I just updated the plugin from 3.11.0 to 3.11.1, now the rendering doesn’t work anymore. Browser shows this image instead: grafik

In the grafana.log I have this:

logger=grafana.update.checker t=2024-07-16T15:47:04.283135203+02:00 level=info msg="Update check succeeded" duration=234.799768ms
logger=plugin.grafana-image-renderer t=2024-07-16T15:47:05.887656459+02:00 level=error msg="Failed to get browser version" err=map[]
logger=plugins.update.checker t=2024-07-16T15:47:06.028639677+02:00 level=info msg="Update check succeeded" duration=1.97984127s
logger=rendering renderer=plugin t=2024-07-16T15:47:06.083086254+02:00 level=info msg=Rendering path="d-solo/qDwRNfbik/icinga2-with-influxdb?var-hostname=jh.vms.idial.fh&var-service=hostalive4&var-command=hostalive4&panelId=1&orgId=&width=640&height=320&theme=light&from=now-6h&to=now" userID=4
logger=grafana-apiserver t=2024-07-16T15:47:06.15364003+02:00 level=info msg="Adding GroupVersion playlist.grafana.app v0alpha1 to ResourceManager"
logger=grafana-apiserver t=2024-07-16T15:47:06.154718455+02:00 level=info msg="Adding GroupVersion featuretoggle.grafana.app v0alpha1 to ResourceManager"
logger=plugin.grafana-image-renderer t=2024-07-16T15:47:06.309327865+02:00 level=error msg="Render request failed" url="http://localhost:3000/d-solo/qDwRNfbik/icinga2-with-influxdb?var-hostname=jh.vms.idial.fh&var-service=hostalive4&var-command=hostalive4&panelId=1&orgId=&width=640&height=320&theme=light&from=now-6h&to=now&render=1" error="Error: Failed to launch the browser process!\nchrome_crashpad_handler: --database is required\nTry 'chrome_crashpad_handler --help' for more information.\n[3002066:3002066:0716/154706.161379:ERROR:socket.cc(120)] recvmsg: Connection reset by peer (104)\n\n\nTROUBLESHOOTING: https://pptr.dev/troubleshooting\n"
logger=context userId=4 orgId=1 uname=sa-1-autogen-1-icinga2 t=2024-07-16T15:47:06.312963968+02:00 level=error msg="Rendering failed." error="rendering failed: Error: Failed to launch the browser process!\nchrome_crashpad_handler: --database is required\nTry 'chrome_crashpad_handler --help' for more information.\n[3002066:3002066:0716/154706.161379:ERROR:socket.cc(120)] recvmsg: Connection reset by peer (104)\n\n\nTROUBLESHOOTING: https://pptr.dev/troubleshooting\n"
logger=context userId=4 orgId=1 uname=sa-1-autogen-1-icinga2 t=2024-07-16T15:47:06.314198587+02:00 level=error msg="Request error" error="Context.HTML - Error rendering template: error. You may need to build frontend assets \n template: error:16:42: executing \"error\" at <.Assets.Dark>: can't evaluate field Assets in type struct { Title string; AppTitle string; AppSubUrl string; ThemeType string; ErrorMsg error }" stack="github.com/grafana/grafana/pkg/web/context.go:112 (0x74e8064)\ngithub.com/grafana/grafana/pkg/services/contexthandler/model/model.go:54 (0x74f3328)\ngithub.com/grafana/grafana/pkg/api/render.go:106 (0xa44612a)\ngithub.com/grafana/grafana/pkg/api/response/web_hack.go:40 (0x74f94af)\nnet/http/server.go:2166 (0x74e90f8)\ngithub.com/grafana/grafana/pkg/web/macaron.go:131 (0x74e90b5)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/macaron.go:137 (0x74e9194)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/macaron.go:137 (0x74e9194)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/macaron.go:137 (0x74e9194)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/macaron.go:137 (0x74e9194)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/macaron.go:137 (0x74e9194)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/services/contexthandler/contexthandler.go:141 (0xa4505f4)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/macaron.go:137 (0x74e9194)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/macaron.go:137 (0x74e9194)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/macaron.go:137 (0x74e9194)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/macaron.go:137 (0x74e9194)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/macaron.go:137 (0x74e9194)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/render.go:44 (0x74e9c0b)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/macaron.go:137 (0x74e9194)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/macaron.go:137 (0x74e9194)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/macaron.go:137 (0x74e9194)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/macaron.go:137 (0x74e9194)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/middleware/csrf/csrf.go:66 (0x98f45af)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/middleware/recovery.go:180 (0xa428ffd)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/middleware/loggermw/logger.go:72 (0x98f553e)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/middleware/request_metrics.go:75 (0x82b19ed)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/middleware/request_tracing.go:88 (0xa429d75)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/middleware/requestmeta/request_metadata.go:66 (0xa44f6e1)\nnet/http/server.go:2166 (0x623f028)\ngithub.com/grafana/grafana/pkg/web/context.go:52 (0x74e79fa)\ngithub.com/grafana/grafana/pkg/web/router.go:155 (0x74eb3ed)\ngithub.com/grafana/grafana/pkg/web/router.go:221 (0x74ebf14)\ngithub.com/grafana/grafana/pkg/web/macaron.go:163 (0x74e95dc)\nnet/http/server.go:3137 (0x624272d)\nnet/http/server.go:2039 (0x623da07)\nruntime/asm_amd64.s:1695 (0x5ee74c0)\n"
logger=context userId=4 orgId=1 uname=sa-1-autogen-1-icinga2 t=2024-07-16T15:47:06.314452972+02:00 level=error msg="Request Completed" method=GET path=/render/d-solo/qDwRNfbik/icinga2-with-influxdb status=500 remote_addr=127.0.0.1 time_ms=244 duration=244.168582ms size=351 referer= handler=/render/* status_source=server

After a downgrade to 3.11.0 everything is working again.

What you expected to happen: Rendering still works as before.

How to reproduce it (as minimally and precisely as possible):

kevin@icinga:~$ sudo systemctl stop grafana-server.service
kevin@icinga:~$ sudo -u grafana -H bash
grafana@icinga:/home/kevin$ cd /storage/grafana/plugins/
grafana@icinga:/storage/grafana/plugins$ rm -rf grafana-image-renderer/
grafana@icinga:/storage/grafana/plugins$ wget https://github.com/grafana/grafana-image-renderer/releases/download/v3.11.1/plugin-linux-x64-glibc.zip
grafana@icinga:/storage/grafana/plugins$ unzip plugin-linux-x64-glibc.zip
grafana@icinga:/storage/grafana/plugins$ rm plugin-linux-x64-glibc.zip
grafana@icinga:/storage/grafana/plugins$ mv plugin-linux-x64-glibc/ grafana-image-renderer/
grafana@icinga:/storage/grafana/plugins$ exit
kevin@icinga:~$ sudo systemctl start grafana-server.service

Anything else we need to know?:

Environment:

  • Grafana Image Renderer version: 3.11.0 -> 3.11.1
  • Grafana version: 11.1.0
  • Installed plugin or remote renderer service: Installed (custom plugin directory defined in /etc/grafana/grafana.ini: plugins = /storage/grafana/plugins)
  • OS Grafana Image Renderer is installed on: Ubuntu 20.04
  • User OS & Browser: Windows 11 23H2, Firefox 115.13.0esr
  • Others:

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 3
  • Comments: 32 (3 by maintainers)

Most upvoted comments

Yeah, I can confirm that fixed it for me. Thanks.

  • 3.11.0 contains Chrome 128.0.6534.0 -> works
  • 3.11.1 contains Chrome 128.0.6597.0 -> does NOT work
  • 3.11.2 contains Chrome 129.0.6644.0 -> does NOT work

Confirming that downgrading to 3.11.0 works. Here is a command line method to install a particular version of the plugin:

grafana-cli plugins uninstall grafana-image-renderer
grafana-cli plugins install grafana-image-renderer 3.11.0
service grafana-server restart

Hi Agnes,

thanks for the tip. I commented out the env variables in /etc/default/grafana, then used this setting in /etc/grafana/grafana.ini:

[plugin.grafana-image-renderer]
rendering_chrome_bin = /storage/grafana/grafana-image-renderer_3.11.0/chrome/linux-128.0.6534.0/chrome-linux64/chrome

That also works.

I also tried it with the newest release 3.11.2 - but this one also does not work out of the box, only if using the env variables or old Chrome. So the newly bundled Chrome unfortunately does not fix the problem.

  • 3.11.0 contains Chrome 128.0.6534.0 -> works
  • 3.11.1 contains Chrome 128.0.6597.0 -> does NOT work
  • 3.11.2 contains Chrome 129.0.6644.0 -> does NOT work

I also found out that the packaged Chrome in 3.11.1 and 3.11.2 had extra files: deb.deps and rpm.deps. I checked my installed packages against the list in deb.deps and installed the missing packages (in my case fonts-liberation, libvulkan1 and xdg-utils). Then restarted the grafana-server.service, but it still didn’t work.

Hi Agnes! Thanks for responding. Unfortunately the following did not change anything:

[plugin.grafana-image-renderer]
rendering_args = --no-sandbox,--disable-gpu,--database

But I wonder if this is a valid setting, as the docs don’t mention it.

The trick from https://github.com/puppeteer/puppeteer/issues/11023#issuecomment-1776247197 actually worked. I set the variables in my /etc/default/grafana-server, then restarted grafana. Rendering started worked again.

My /etc/default/grafana-server
GRAFANA_USER=grafana

GRAFANA_GROUP=grafana

GRAFANA_HOME=/usr/share/grafana

LOG_DIR=/var/log/grafana

DATA_DIR=/var/lib/grafana

MAX_OPEN_FILES=10000

CONF_DIR=/etc/grafana

CONF_FILE=/etc/grafana/grafana.ini

RESTART_ON_UPGRADE=true

PLUGINS_DIR=/var/lib/grafana/plugins

PROVISIONING_CFG_DIR=/etc/grafana/provisioning

# Only used on systemd systems
PID_FILE_DIR=/run/grafana

# TEST Workaround for grafana-image-renderer-3.11.1
XDG_CONFIG_HOME=/tmp/.chromium
XDG_CACHE_HOME=/tmp/.chromium

I then also tried using a different directory, i.e. inside the home directory of the grafana user (/usr/share/grafana/):

XDG_CONFIG_HOME=/usr/share/grafana/.config/chromium
XDG_CACHE_HOME=/usr/share/grafana/.cache/chromium

But then the rendering stopped working again. Even after pre-creating the directories, doing a chown grafana:grafana and even chmod 777 on them these did not work.

Dou you have any idead what has changed between 3.11.0 and 3.11.1 that could cause this behaviour?

Same issue. Downgraded from 3.11.1 to 3.11.0 then it worked…

I’m seeing the same thing with the latest helm chart, just setting imageRenderer.enabled: true.

@alphabet5 I had the same issue yesterday. You can downgrade to 3.11.0 and it resolves the issue; just add the following:

imageRenderer:
  enabled: true
  image:
    registry: docker.io
    repository: grafana/grafana-image-renderer
    tag: 3.11.0
    pullPolicy: Always

Same problem with release 3.11.3, containing Chrome 129.0.6654.0. Still one of the workarounds (using XDG_* env variables or older Chrome 128.0.6534) is needed.

Still an issue in 3.11.4 (containing Chrome 130.0.6693.0).