Remote image renderer - error context deadline exceeded

Grafana
1

Hello,
I have a problem that when using grafana image renderer as a rendering tool for my grafana dashboards. It sometimes get server error messages. Maybe would someone advise what problem is causing this and how to solve it?
Log is here:

``
> t=2021-06-19T05:08:57+0000 lvl=eror msg="Rendering failed." logger=context userId=0 orgId=1 uname= error="failed to send request to remote rendering service: Get "http://xxx.xxx.xxx:8081/render?deviceScaleFactor=1.000000&domain=xxx.xxx.xxx.xxx&encoding=&height=200&renderKey=srpRq9INm6VYPAbmBETGz56Iak8rBvnG&timeout=60&timezone=&url=http%3A%2F%2Fxxx.xxx.xxx.xxx%3A3000%2Fd-solo%2FDWn1b8EMk%2Fdashboard1%3ForgId%3D1%26panelId%3D2%26width%3D400%26height%3D200%26render%3D1&width=400\": context deadline exceeded.

Whereas at the remote image renderer - the error log is following:


{"url":"/render?deviceScaleFactor=1.000000&domain=xxx.xxx.xxx&encoding=&height=200&renderKey=tcJGEpVgHboYIw5dH2S7ZmJKbC85T6xY&timeout=60&timezone=&url=http%3A%2F%2Fxxx.xxx.xxx.xxx%3A3000%2Fd-solo%2FDWn1b8EMk%2Fdashboard1%3ForgId%3D1%26panelId%3D2%26width%3D400%26height%3D200%26render%3D1&width=400","stack":"TimeoutError: Navigation timeout of 60000 ms exceeded\n    at /usr/src/app/node_modules/puppeteer/lib/LifecycleWatcher.js:142:21\n  -- ASYNC --\n    at Frame.<anonymous> (/usr/src/app/node_modules/puppeteer/lib/helper.js:111:15)\n    at Page.goto (/usr/src/app/node_modules/puppeteer/lib/Page.js:675:49)\n    at Page.<anonymous> (/usr/src/app/node_modules/puppeteer/lib/helper.js:112:23)\n    at Browser.<anonymous> (/usr/src/app/build/browser/browser.js:170:24)\n    at Generator.next (<anonymous>)\n    at fulfilled (/usr/src/app/build/browser/browser.js:5:58)\n    at runMicrotasks (<anonymous>)\n    at processTicksAndRejections (internal/process/task_queues.js:97:5)","level":"error","message":"Request failed"}
2

While I haven’t used the renderer myself, I would guess that the key issue is this:

The renderer couldn’t load the dashboard (including having data queries complete) within 60 seconds, so gave up.

Maybe it’s possible to increase that timeout? Or ensure that queries return faster?

3

I’ll try,
The default was 30s, already increased up to a minute.
Shall give a 120s, but I feel that something else is stopping dashboards to render, since they render ~50% of the time.

4

This topic was automatically closed after 365 days. New replies are no longer allowed.