Direct link rendered image - "failed to render an image"

Grafana
1

Hi all,

I just started using Grafana and InfluxDB to visualize some sensor output in my home automation project. To be able to show the charts in my application, I would like them to be images.

When I use the ‘Direct link rendered image’ link, I get a 404.
In the logs I only see this:

t=2018-02-08T22:51:01+0000 lvl=info msg=Rendering logger=png-renderer path="dashboard-solo/db/overzicht?orgId=1&from=1518126571027&to=1518130171028&panelId=4&width=1000&height=500&tz=UTC%2B01%3A00"                                                                                                                                     
t=2018-02-08T22:51:01+0000 lvl=eror msg="failed to render an image" logger=png-renderer error="exit status 255"                                                      
t=2018-02-08T22:51:01+0000 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=GET path=/render/dashboard-solo/db/overzicht status=404 remote_addr=172.18.0.1 time_ms=132 size=19 referer="http://xxxxxxxxxxxx:3000/dashboard/db/overzicht?orgId=1&from=now-1h&to=now"

I’m running it inside a docker container, using the official image.

Any ideas what I can try?

Thanks!

2

Does it work if you use a small time range (5 minutes for example)?

There doesn’t seem to be any error message from PhantomJS which makes it hard to troubleshoot.

Also, which version of Grafana are you using?

3

Hello,
I have a same problem with rendering image:

 t=2018-02-14T17:12:48+0100 lvl=info msg="New state change" logger=alerting.resultHandler alertId=56 newState=alerting prev state=ok
 t=2018-02-14T17:12:48+0100 lvl=info msg=Rendering logger=png-renderer path="d-solo/1LKY__jkz/services-overview?panelId=2"
 t=2018-02-14T17:12:48+0100 lvl=eror msg="failed to render an image" logger=png-renderer error="exit status 127"

Version: 5.0.0-11779beta1
Notification channel: email

4

It’s probably this issue: https://github.com/grafana/grafana/issues/10526

This is a high priority issue which we will fix before the release of 5.0 stable.

5

Hello,
we got the same problem, look here:

t=2018-03-02T16:27:34+0100 lvl=eror msg=“Request Completed” logger=context userId=0 orgId=1 uname= method=GET path=/render/dashboard-solo/db/node-byid status=500 remote_addr=195.226.122.180 time_ms=60001 size=1769 referer=https://karte.neanderfunk.de/
t=2018-03-02T16:27:34+0100 lvl=eror msg=“failed to render an image” logger=png-renderer error=“signal: killed”

We are on Grafana 5.0
Thanks for any advice or bugfix

6

Looks like a totally different error message: signal: killed

To get more details, can you turn on debug logging in your Grafana ini file:

[log]
level = debug
7

I’m also getting this same error:

t=2018-03-19T08:26:41-0600 lvl=info msg=Rendering logger=png-renderer path="d-solo/c9fqwRkmk/energy?orgId=1&panelId=2&from=1521447685706&to=1521469285706&width=1000&height=500&tz=UTC-06%3A00"
t=2018-03-19T08:26:42-0600 lvl=eror msg="failed to render an image" logger=png-renderer error="exit status 255"
t=2018-03-19T08:26:42-0600 lvl=info msg="Request Completed" logger=context userId=1 orgId=1 uname=admin method=GET path=/render/d-solo/c9fqwRkmk/energy status=404 remote_addr=192.168.1.141 time_ms=1137 size=19 referer="http://192.168.1.108:3000/d/c9fqwRkmk/energy?orgId=1"
8

@cby016 Can you turn on debugging, please. It is nearly impossible to say what your error is from just “exit status 255”.

Also, if you are using Grafana 5.0 (you don’t say which version of Grafana you are using) then please upgrade to the latest version.

9

@daniellee I actually started another topic with the details here Direct link rendered image not working on mac os x

10

Hi, just updated to latest stable Grafana v5.1.4 (commit: a5fe24fcc) and issue is still there.
OS: Centos 7
Data source: influxDB
Request: curl -H “Authorization: Bearer hidden==” ‘http://127.0.0.1:3000/render/d-solo/382/icinga2-with-influxdb?var-hostname=host1&var-service=disk&var-command=disk&panelId=2&orgId=1&width=640&height=280&theme=light&from=now-6h&to=now’
Response: page with ‘Timeout error. You can set timeout in seconds with &timeout url parameter’

Logs:

t=2018-06-22T12:42:58+0000 lvl=info msg=Rendering logger=png-renderer path=“d-solo/382/icinga2-with-influxdb?var-hostname=eye.mobizon.gmbh&var-service=disk&var-command=
disk&panelId=2&orgId=1&width=640&height=280&theme=light&from=now-6h&to=now&timeout=10”
t=2018-06-22T12:42:59+0000 lvl=eror msg=“Dashboard not found” logger=context userId=0 orgId=1 uname= error=“Dashboard not found”
t=2018-06-22T12:42:59+0000 lvl=info msg=“Request Completed” logger=context userId=0 orgId=1 uname= method=GET path=/api/dashboards/uid/382 status=404 remote_addr=[::1]
time_ms=0 size=33 referer=“localhost:3000/d-solo/382/icinga2-with-influxdb?var-hostname=eye.mobizon.gmbh&var-service=disk&var-command=disk&panelId=2&orgId=1&widt
h=640&height=280&theme=light&from=now-6h&to=now&timeout=10&render=1”
t=2018-06-22T12:42:59+0000 lvl=dbug msg="[phantom] Loading a web page: localhost:3000/d-solo/382/icinga2-with-influxdb?var-hostname=eye.mobizon.gmbh&var-service=
disk&var-command=disk&panelId=2&orgId=1&width=640&height=280&theme=light&from=now-6h&to=now&timeout=10&render=1 status: success 10000" logger=png-renderer
t=2018-06-22T12:42:59+0000 lvl=dbug msg="[phantom] ERROR: null is not an object (evaluating ‘e.panel’)\n localhost:3000/public/build/0.5c89ac3fc7a3e78b3629.js:15
nTRACE:\n -> : 0 (in function “apply”)" logger=png-renderer
t=2018-06-22T12:42:59+0000 lvl=dbug msg="[phantom] phantomjs://code/render.js:48 in onError" logger=png-renderer
t=2018-06-22T12:42:59+0000 lvl=dbug msg="[phantom] ERROR: [object Object]\nTRACE:\n -> : 0 (in function “apply”)\n\n phantomjs://code/render.js:48 in onError" logger
=png-renderer
t=2018-06-22T12:42:59+0000 lvl=dbug msg="[phantom] ERROR: Possibly unhandled rejection: {“message”:“Dashboard not found”,“severity”:“warning”,“line”:11,“sour
ceURL”:“localhost:3000/public/build/app.5372b9bbcb8c6d1c027e.js”,“stack”:“requestErrorHandler@ localhost:3000/public/build/app.5372b9bbcb8c6d1c027e.j
s:11:76460\n[native code]\n localhost:3000/public/build/vendor.0cea50118711e7e6c839.js:87:84380\ni@ localhost:3000/public/build/vendor.0cea50118711e7e6c8
39.js:87:21995\n localhost:3000/public/build/vendor.0cea50118711e7e6c839.js:87:23453”}\nTRACE:\n -> : 0 (in function “apply”)\n\n phantomjs://code/render.js:
48 in onError" logger=png-renderer
t=2018-06-22T12:43:08+0000 lvl=eror msg=“Timeout error. You can set timeout in seconds with &timeout url parameter” logger=context userId=0 orgId=1 uname= error=“Timeou
t error. You can set timeout in seconds with &timeout url parameter”
t=2018-06-22T12:43:08+0000 lvl=eror msg=“Request Completed” logger=context userId=0 orgId=1 uname= method=GET path=/render/d-solo/382/icinga2-with-influxdb status=500 r
emote_addr=127.0.0.1 time_ms=10028 size=1763 referer=
t=2018-06-22T12:43:08+0000 lvl=eror msg=“failed to render an image” logger=png-renderer error=“signal: killed”

Any solutions or workarounds will be good as nobody tells anything about workarounds. Thanks.