northys
northys
I also can't confirm this issue. Using latest grafana, prometheus and node-exporter and there are no issues on my dashboard. Thera re only some blank graphs (with advanced metrics I...
> which node_exporter Version do you use? I have still the same issue using Prometheus 2.35 (also Docker?) and node_exporter 1.3.1, Grafana 8.4.7 docker: ``` Starting Grafana logger=settings version=8.4.2 commit=dea7d4996a...
this is all i can provide to you... docker-compose.yml ```yaml version: '3.8' services: grafana: image: grafana/grafana ports: - "127.0.0.1:3000:3000/tcp" environment: GF_RENDERING_SERVER_URL: http://grafana-renderer:8081/render GF_RENDERING_CALLBACK_URL: http://grafana:3000/ GF_INSTALL_PLUGINS: grafana-image-renderer,grafana-piechart-panel restart: unless-stopped links: -...
also I have imported the dashboard using ID copied from grafana dashboard catalog... it's possible that newer version or something imported directly as json from this repository may be broken......
``` root@nuc ~ # journalctl --since "12 hours ago" | grep -i maloja Apr 24 01:48:16 nuc.northys.cz kernel: [ 740653] 0 740653 2182572 2172736 18059264 0 0 Maloja Apr 24...
Yup it's with cache enabled. I'll make coffee and dig more into syslog, graphs I have in prometheus and into logs produced by maloja.
Interesting it looks like kill log doesn't match time when maloja started. ``` root@nuc ~ # docker logs -t maloja | grep v3.0.5 2022-04-23T23:46:58.972536930Z Maloja v3.0.5 2022-04-24T02:50:15.541884298Z Maloja v3.0.5 2022-04-24T12:39:03.150876609Z...
Looks like it took only 2 hours to consume about 8GB of RAM. I think it should be easy to reproduce the leak. 
I wonder whether the cache is used later? Because I haven't scrobbled a single song during the night and my sqlite database is only 30MB big. I understand that it...
> It still doesn't really explain why the cache expulsion didn't trigger Has that happened also for you? I could explain that to myself as my homepab has only 12GB...