-
Notifications
You must be signed in to change notification settings - Fork 155
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
grafana-image-renderer stops working after 2nd restart of Grafana service (Windows) #260
Comments
After reproducing this to gather logs and screen grabs, I found this in the grafana.log (filtered to "render")
So the plugin is getting disabled (though grafana-cli doesn't show it's disabled) because of the presence of Which contains
Looking at microsoft/playwright#2901 suggest that this is because this build of Chromium is trying to load video renderer DLLs which don't exist on this OS (Windows Server 2012 R2). Those DLLs probably can't be added to some OS, particularly Server OS. As this is an expected condition, and doesn't affect the plugin rendering for Grafana (on first run) it seems the cause of the problem is Chromium being called with settings that cause the debug.log to be generated which then breaks the signature for the plugin making it get ignored on all future Grafana service starts. While it doesn't appear to be related to the "missing" video decoder DLLs, I've also seen this
logged to the The most logical thing to do here would be to call Chromium with settings that prevent the I did have custom.ini including
Which it looks like I added to try and debug this issue. Removing it still causes the debug.log to get generated - so the log level isn't being passed to Chromium. An alternative approach, if it's possible, might be to set the signing to ignore |
As per https://peter.sh/experiments/chromium-command-line-switches/ other options might be to pass one or more of
It's worth noting that https://www.chromium.org/for-testers/enable-logging says the file will be called |
Hi, @AlexHeylin I'm experiencing the same problem with the debug file in the chromium folder, so I would like to know if you did what you say in the last comment as a possible workaround and if it was solved. have you solved this issue? these are the errors that I get from debug.file (It works correctly for 1 or 2 days, then the debug.file is created, Grafana service is restarted and finally image render is broken) ERROR:command_buffer_proxy_impl.cc(122)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer. As a possible workaround, I modified the custom init file of Grafana adding "rendering_args" = --disable-gpu or -disable-gpu without any successful This is because I have read that it is an issue with the GPU but my VM does not have it Thanks! |
After upgrade to 8.0.6
Note that the codec warnings are gone. This may also be because I installed the "Media Foundation" feature in Windows Server 2012 R2. The issue persists though. Given there are multiple reasons Chromium may generate this file, I suggest the best way to resolve this is to have this file ignored for signing purposes, or tell Chromium to create it in a temp folder such as I will try passing switches to Chromium, and report back. |
HI @AlexHeylin, I followed this thread and it works... but the plugin will be unsigned BR |
This issue isn't resolved, simply worked around. If the plugin doesn't shutdown cleanly for some reason the debug.log file remains in place and the plugin can't start until the debug.log file is removed manually and Grafana restarted. Restarting the Grafana service won't solve the problem because once the plugin can't load due to the debug.log , the plugin isn't running so can't remove the debug.log file to resolve the problem. |
What happened:
Restart Grafana service, or computer. Grafana front end says grafana-image-renderer not installed. grafana-cli might agree, or might show it installed. grafana-image-renderer folder and files exist on disk without any apparent changes since before service was restarted.
What you expected to happen:
Once installed, grafana-image-renderer continues to show as installed and work after service / computer restarts.
How to reproduce it (as minimally and precisely as possible):
Install v8.x and grafana-image-renderer on Windows (I'm using MySQL, and Grafana was upgraded from at least v7, v6 before that - no idea if relevant).
loop to here
Restart Grafana service once to activate grafana-image-renderer.
Check front end and confirm grafana-image-renderer installed and working.
Restart Grafana service.
Check front end and observe that it says grafana-image-renderer is not installed.
Run
grafana-cli.exe plugins ls
and observe it may / may not show grafana-image-renderer as installed. Even if it's shown as installed, it doesn't work.Run
grafana-cli.exe remove grafana-image-renderer
and observe from result that it was removed, even ifgrafana-cli.exe plugins ls
said it wasn't installed.Run
grafana-cli.exe remove grafana-image-renderer
and observe the file not found error because it tried to remove a file that wasn't there - observe how this is different to the run above.Run
grafana-cli.exe install grafana-image-renderer
and observe success reported, and prompt to restart Grafana service to activate plugin.Loop back to
loop to here
in this list. Repeat until you're convinced I'm not making this up.Anything else we need to know?:
As I recall, following the upgrade of 7.x to 8.0.2 the plugins refused to run and I think I had to delete the plugins.json from the plugins root folder and let it rebuild before they would work. All other plugins work fine now - only grafana-image-renderer gives problems.
Environment:
grafana-clock-panel ←[33m@←[0m 1.1.3
grafana-image-renderer ←[33m@←[0m 3.0.1
grafana-piechart-panel ←[33m@←[0m 1.6.2
grafana-polystat-panel ←[33m@←[0m 1.2.5
grafana-worldmap-panel ←[33m@←[0m 0.3.3
briangann-datatable-panel ←[33m@←[0m 1.0.3
briangann-gauge-panel ←[33m@←[0m 0.0.9
farski-blendstat-panel ←[33m@←[0m 1.0.3
jasonlashua-prtg-datasource ←[33m@←[0m 4.0.4
michaeldmoore-annunciator-panel ←[33m@←[0m 1.1.0
michaeldmoore-multistat-panel ←[33m@←[0m 1.7.2
mtanda-heatmap-epoch-panel ←[33m@←[0m 0.1.8
mxswat-separator-panel ←[33m@←[0m 1.0.1
neocat-cal-heatmap-panel ←[33m@←[0m 0.0.4
petrslavotinek-carpetplot-panel ←[33m@←[0m 0.1.2
satellogic-3d-globe-panel ←[33m@←[0m 0.1.1
savantly-heatmap-panel ←[33m@←[0m 0.2.1
vonage-status-panel ←[33m@←[0m 1.0.11
The text was updated successfully, but these errors were encountered: