March 24, 20251 yr Hello all, new to Unraid and New to this Dashboard, I have the dashboard installed and I can see that I see everything except my plex type, readarr, sonarr blah blah, it looks like I need to get Varken installed, but can't seem to get it working. I went through and created a varken.ini file but when I got to start it, I get Critical: dbmanager : You have not configured you varken.ini. Please read the wiki page for configuration, except it doesn't seem the wiki page exists any longer? Does someone have a walk through out there somewhere I can use? I have my Telegraf set to 1.20.2 and my influxdb to 1.8.4 so I think that's correct? I've also installed Python 3 for Unraid as I saw when googling around that it had to have python and pip.
March 30, 20251 yr Dasbhoards report "No Data". I just installed Grafana-Unraid-Stack from Community Apps, and the dashboards are reporting "No Data". I followed the instructions from: https://hub.docker.com/r/testdasi/grafana-unraid-stack/ How do I fix/configure? SOLUTION: Docker container log was showing errors: [error] influxdb crashed! [error] loki crashed! Fix: testdasi/grafana-unraid-stack:stable-amd64 Edited April 5, 20251 yr by Jaybau Solution
April 3, 20251 yr Same here. Log says: [info] Initialisation started... [info] influxdb fixed. [info] loki fixed. [info] telegraf fixed. [info] promtail fixed. [info] grafana fixed. [info] Initialisation complete [info] Runing apps... [info] Run influxdb as service on port 8086 Executable /usr/bin/influxd does not exist! [info] Run loki as daemon on port 3100 [info] Run telegraf as service [info] Run promtail as daemon on port 9086 [info] Run grafana as service on port 3006 * Starting Grafana Server ...fail! [info] All done [error] influxdb crashed! [error] loki crashed! [info] Skip hddtemp due to USE_HDDTEMP set to no [error] telegraf crashed! [info] promtail PID: 77 [error] grafana crashed!
April 5, 20251 yr @Chlorgas I found that using this repository tag worked for me: testdasi/grafana-unraid-stack:stable-amd64
April 6, 20251 yr On 4/5/2025 at 4:03 AM, Jaybau said: @Chlorgas I found that using this repository tag worked for me: testdasi/grafana-unraid-stack:stable-amd64 Thanks for that!! Worked for me as well!
April 8, 20251 yr Well this was some work, but I was able to get V1.7 of this dashboard on 7.0.1 of Unraid working going through the thread and hacking my way through it with all the containers and configuring grafana with the various data sources. For those that try this, here are some tips for you in the order that I deployed my implementation of this dashboard: Grafana docker install: I used the official latest version, didn't make any changes except I'm using port 3003 as I'm running Homepage on 3000. Bridge mode from the instructions. InfluxDB (V1.8) docker: Used the official V1.8 version from the app store. Made no changes to the docker install. Bridge mode also, kept it at port 8086, didn't use the "alpine" version that I saw in a few places. I tried 2.x version and didn't have any luck and 1.8 works fine. Telegraf docker (this was challenging): I selected the official version also from the app store. I created a directory prior called "telegraf" first in my /mnt/user/appdata directory and I used this abbreviated version for the telegraf.conf file: https://github.com/skaterpunk/UUD/blob/main/telegraf.conf. The 10,000 line conf file that has been referenced (and is archived on the wayback machine) a few times in this thread was just too overwhelming for my skills and patience. The only thing I changed was the influxDB location and enabling the UPS for my power supply (which is working in Unraid). After uploading the .conf file into the appdata/telegraf directory, I made the following changes to the docker container before deploying it: Changed the repository to: telegraf:alpine Host mode (already enabled but important to point this out) Host path 7 points to the conf file: /mnt/user/appdata/telegraf/telegraf.conf Turn on advanced mode on upper right hand corner, then add: Extra Parameters: --entrypoint=/bin/sh Post Arguments: -c "apk add --no-cache sed && sed -i 's/su-exec telegraf/su-exec root/' /entrypoint.sh && apk update && apk upgrade && apk add smartmontools curl python3 py3-pip docker && python3 -m venv /venv && source /venv/bin/activate && pip install requests && exec /entrypoint.sh telegraf" It should begin to populate your InfluxDB. You can install a docker container called Chronograf to connect your InfluxDB and see if there's data inside that DB as V1.8 doesn't have a web UI (versus 2.x). Varken docker for Media Library/Plex Stats Varken hasn't been updated in a few years but it's still able to interface and collect stats from Tautulli and the Arrr stack of apps. For deploying it, do the following: Create a directory called varken in your appdata (e.g., /mnt/user/appdata/varken Download the sample varken.ini file and edit it for your environment. I used this example here: https://github.com/HStep20/Ultimate-Unraid-Dashboard-Guide/blob/master/appdata/GUS-varken/varken.ini I only have one instance of Sonarr so changed that to 1 and not 1,2 (same with radarr). I set ombi to false as I don't use it. For the Maxmind License, I registered at https://maxmind.com and got a free license. I copied and pasted that license into the config and uncommented that line. I finally configured InfluxDB, Tautulli, Sonarr, Radarr with their various IP addresses and API keys. I have a Ubiquiti instance, but it won't work since it requires authentication to complete the login. Copy this varken.ini into your varken directory. Deploy varken with bridge mode (preset already), correct the timezone, and make sure the config directory is correct. It will then interface with your InfluxDB. Unraid API Go to app store, search for "unraid API" and select unraid-simple-monitoring-api docker image. The port 24940 should work for you. Deploy it as-is, no changes needed. Configuring Grafana Log into grafana instance. You need to add three data sources: First, select InfluxDB - connect it to your influxDB IP address. To configure it, called it "telegrafDB" or whatever you want. HTTP URL=Your influxDB url: http://10.0.1.5:8086 (example for me) Database=telegraf HTTP method=post Save/Test Repeat these steps for Varken, name it "varkenDB" or whatever you want. Change the database to varken and HTTP method=post. Save and Test and you should be connected. For the third data source, the Unraid API, it took me some time and persistence. Here's what worked: Install new data source, which is Infinity (it supports JSON connections). Configure infinity to connect to your unraid api instance: Name=UNRAID API (I used what the author used for this dashboard, so not sure if it really matters). No Auth Base URL=http://10.0.1.5:24940/api/getServers (in my case), yours will vary (you can test it also) Enable Health Check. Set health check url to: http://10.0.1.5:24940/api/getServers (in my case) Save and Test and you should be set. All three data sources are now connected to Grafana. Download the V1.7 JSON for this dashboard and Create New Dashboard, Import JSON, select the V1.7 JSON. It will install and load. Finally, select your Host (unraid server), Telegraf Datasource: telegrafdb, Varken Datasource: varkendb, and then Unraid API Datasource: UNRAID API. Select your proper parity drive(s), Array Drive(s), Cache Drive (I don't use one), SSD Drive, and Flash Boot Drive. Stats should populate and you can then add/remove tiles for the dashboard. My only issue so far is that I'm missing the following in my dashboard: Stream Origination Tile Map - No data is showing up from Varken and the Mapping License that I have. Not sure if that will take time or I'm doing something wrong. Some Temperature and Fan Speeed Tiles aren't working. Not so worried that much about this. Hope this helps any newbs like me who are wishing to deploy this one on V7.0.1. Thanks. Edited April 8, 20251 yr by huntrm
June 23, 20251 yr Just a heads up, if you're running the latest version of Telegraf (1.34.5-alpine), it seems to cause issues with the 'Ultimate Dashboard'.Until someone clever that me can work out what changes caused the issue, pinning to an older version works:Change from: telegraf:alpineTo version: telegraf:1.34.4-alpine Edited June 23, 20251 yr by 1471
July 16, 2025Jul 16 @ciro73 @blackert @M10UnraidUserAfter a reboot, I found my telegraf instances telegraf:1.20.2 was not working (This was because I have the following post arguments on my instance to ensure smartmontools is installed)./bin/bash -c 'apt-get update && apt-get install -y smartmontools && telegraf'It appears that smartmontools has been removed from the apt-get source repository, so to fix it I updated the post arguments to below. This updates the target repository to an archived version. This has resolved the issue for me./bin/bash -c 'sed -i s/security.debian.org/archive.debian.org/g /etc/apt/sources.list && sed -i s/deb.debian.org/archive.debian.org/g /etc/apt/sources.list && apt-get update && apt-get install -y smartmontools && telegraf' Edited July 16, 2025Jul 16 by Jufy111
August 26, 2025Aug 26 If someone is running into issues with telegraf, docker etc., some notes on how I finally got it working (also as a future reference for me).Root cause:after telegraf version 1.20.2, telegraf does no longer run as root. It is therefore no longer able to access the docker status, and it is no longer possible to install packages via "post arguments" or by using the telegraf console as-is.Workaround would be staying on telegraf 1.20.2, which has some issues itself:a) possible security issue due to its root privilegesb) will not receive any updates (new functionality and patches)c) docker monitoring seems not to be possible anymore due to it using an old version of the docker API (error message in log "[inputs.docker] Error in plugin: Error response from daemon: {"message":"client version 1.21 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version"}"Solution (working for me as of august 2025):install latest telegraf versiontelegraf:alpine give the telegraf user the rights to access the docker.sock by adding an extra parameter--user telegraf:$(stat -c '%g' /var/run/docker.sock)make sure your telegraf-conf does not use any additional packages (since those are not installed yet, the container will most likely not start).open the Unraid-CLI, and enter the telegraf container as root via docker exec -it --user root <telegraf-docker-name> shnow you can install any addtional packages via the CLI, e.g.apk add smartmontoolsapk add lm-sensorsapk add lm-sensors-detectapk add nvme-cliapk add ipmitoolnow re-enable all inputs using additional packages (if needed).you should now have the latest version of telegraf running with additional packages and a telegraf user able to access the docker status.
August 26, 2025Aug 26 side note: according to their website, it should be able to add packages even as non-root, but I have found not way of doing so... https://www.influxdata.com/blog/docker-run-telegraf-as-non-root/
October 19, 2025Oct 19 On 8/26/2025 at 2:56 PM, lambi said:If someone is running into issues with telegraf, docker etc., some notes on how I finally got it working (also as a future reference for me).Root cause:after telegraf version 1.20.2, telegraf does no longer run as root. It is therefore no longer able to access the docker status, and it is no longer possible to install packages via "post arguments" or by using the telegraf console as-is.Workaround would be staying on telegraf 1.20.2, which has some issues itself:a) possible security issue due to its root privilegesb) will not receive any updates (new functionality and patches)c) docker monitoring seems not to be possible anymore due to it using an old version of the docker API (error message in log"[inputs.docker] Error in plugin: Error response from daemon: {"message":"client version 1.21 is too old. Minimum supported API version is 1.24, please upgrade your client to a newer version"}"Solution (working for me as of august 2025):install latest telegraf versiontelegraf:alpinegive the telegraf user the rights to access the docker.sock by adding an extra parameter--user telegraf:$(stat -c '%g' /var/run/docker.sock)make sure your telegraf-conf does not use any additional packages (since those are not installed yet, the container will most likely not start).open the Unraid-CLI, and enter the telegraf container as root viadocker exec -it --user root <telegraf-docker-name> shnow you can install any addtional packages via the CLI, e.g.apk add smartmontoolsapk add lm-sensorsapk add lm-sensors-detectapk add nvme-cliapk add ipmitoolnow re-enable all inputs using additional packages (if needed).you should now have the latest version of telegraf running with additional packages and a telegraf user able to access the docker status.I followed this tutorial and telegraph starts. Unfortunately I get this message.2025-10-19T07:35:00Z W! [outputs.influxdb_v2] Metric buffer overflow; 8695 metrics have been dropped2025-10-19T07:35:00Z W! [outputs.influxdb_v2] Metric buffer overflow; 8439 metrics have been dropped Can you share your influxdb and telegraph settings? I am using the latest versions of influxdb and telegraph.
May 7May 7 Using Extra Parameters: --user telegraf:$(stat -c '%g' /var/run/docker.sock) and the golift/telegraf image worked for me for the latest versions of telegraf and influxdb.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.