October 8, 20241 yr Now seeing a new error. I have the telegraf.conf in both /mnt/user/appdata/telegraf/telegraf.conf/telegraf.conf and /etc/telegraf/telegraf.conf. When I click on start, I see the circle rotating and then nothing. When I click on logs under Telegraf, I see "/bin/sh: apt: not found." When I click on Edit, I don't see anywhere that I'm doing any command line arguments or anything else that's trying to use the apt command.
March 1, 20251 yr Hello, I was wondering if someone was able to have telegraf working with pihole v6 api? I don't get how to fetch data with the new api. Thank you!
March 30, 20251 yr Does anyone know how to fix "[inputs.diskio] Unable to gather disk ..." 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sde1": error reading /dev/sde1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sde1": error reading /dev/sde1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sdg1": error reading /dev/sdg1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sdg1": error reading /dev/sdg1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sdh1": error reading /dev/sdh1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sdh1": error reading /dev/sdh1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sdc1": error reading /dev/sdc1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sdc1": error reading /dev/sdc1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sdd1": error reading /dev/sdd1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sdd1": error reading /dev/sdd1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sdb1": error reading /dev/sdb1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sdb1": error reading /dev/sdb1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sdf1": error reading /dev/sdf1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sdf1": error reading /dev/sdf1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sdi1": error reading /dev/sdi1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sdi1": error reading /dev/sdi1: no such file or directory
March 31, 20251 yr On 3/30/2025 at 8:02 AM, spyd4r said: Does anyone know how to fix "[inputs.diskio] Unable to gather disk ..." 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sde1": error reading /dev/sde1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sde1": error reading /dev/sde1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sdg1": error reading /dev/sdg1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sdg1": error reading /dev/sdg1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sdh1": error reading /dev/sdh1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sdh1": error reading /dev/sdh1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sdc1": error reading /dev/sdc1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sdc1": error reading /dev/sdc1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sdd1": error reading /dev/sdd1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sdd1": error reading /dev/sdd1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sdb1": error reading /dev/sdb1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sdb1": error reading /dev/sdb1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sdf1": error reading /dev/sdf1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sdf1": error reading /dev/sdf1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk name for "sdi1": error reading /dev/sdi1: no such file or directory 2025-03-30T12:55:50Z W! [inputs.diskio] Unable to gather disk tags for "sdi1": error reading /dev/sdi1: no such file or directory ... for which docker... better to have asked on the general forum and linked here... AS That a path error that it either is fighting a read write or general host error on what is accessing what... Quote W! [inputs.diskio] Unable to gather disk name for "sde1": error reading /dev/sde1: no such file or directory W! [inputs.diskio] Unable to gather disk tags for "sde1": error reading /dev/sde1: no such file or directory Stop all dockers and run the docker safe permission option under unraid tool... Also edit the docker and make sure the path exist If I'm guessing, this is for docker hdd temp. Edited March 31, 20251 yr by bmartino1 typo
May 13, 20251 yr On 3/31/2025 at 10:28 AM, bmartino1 said: ... for which docker... Pretty sure @spyd4r was asking in regards to the telegraf container. I have had mine pinned on 1.20.2-alpine for a long time, but my logs were getting filled with the warning about the inputs.docker API being depreciated. Following this post by @cassiusdrow, I was able to upgrade off to something newer. I tried going to telegraf 1.34.3-alpine, but got the same inputs.diskio errors. I ultimately went back to 1.24.4-alpine and my logs are quiet. Which is what I was after in the first place. If the fix is easy, I would like to go to something newer, less prone to vulnerabilities, etc.
May 14, 20251 yr 14 hours ago, UncleStu said: Pretty sure @spyd4r was asking in regards to the telegraf container. I have had mine pinned on 1.20.2-alpine for a long time, but my logs were getting filled with the warning about the inputs.docker API being depreciated. Following this post by @cassiusdrow, I was able to upgrade off to something newer. I tried going to telegraf 1.34.3-alpine, but got the same inputs.diskio errors. I ultimately went back to 1.24.4-alpine and my logs are quiet. Which is what I was after in the first place. If the fix is easy, I would like to go to something newer, less prone to vulnerabilities, etc. I've also had mine pinned on 1.20.2-alpine as well due to newer versions having issues, I can't remember them exactly though. I'll have to give 1.24.4-alpine on my secondary test server, thanks for that information.
June 16, 20251 yr I'm running unRaid V7.1.2. When I run the InfluxDB docker container, I can't see the WebUI. I'm told that the Docker refused the connection.The only error is InfluxDB saysts=2025-06-16T19:14:21.610640Z lvl=info msg="Pruning shard groups after retention check (start)" log_id=0x6q_OIl000 service=retention op_name=retention_delete_check op_name=retention_prune_shard_groups op_event=startts=2025-06-16T19:14:21.610655Z lvl=info msg="Pruning shard groups after retention check (end)" log_id=0x6q_OIl000 service=retention op_name=retention_delete_check op_name=retention_prune_shard_groups op_event=end op_elapsed=0.017msts=2025-06-16T19:14:21.610675Z lvl=info msg="Retention policy deletion check (end)" log_id=0x6q_OIl000 service=retention op_name=retention_delete_check op_event=end op_elapsed=0.156msAlso, does someone have the generic telegraf.conf file. I have one that allows telegraf to stay started, but I'm not getting any data. (I tried to go look at the InfluxDB table, which is why I know that InfluxDB UI is refusing my connection.)I apologize if these are stupid noob questions, but I'm just trying to get my Grafana dashboard to work.
June 19, 20251 yr Please update influx-cli, Influx CLI dev (git: a79a2a1b825867421d320428538f76a4c90aa34c) build_date: 2024-04-16T14:34:32Z is outdatet.Update of Container today.. CLI Version from Stone-Age.
June 19, 20251 yr Where did you see that my Influx CLI is outdated? Also, as I'm still on the learning curve on unRaid Docker, how would I go about doing the upgrade? Do I open a terminal session in unRaid or open the console prompt for InfluxDB?
June 21, 20251 yr Looking for help on getting Grafana container reinstalled. I'm starting over from scratch and purging the old data. Directoty /mnt/user/appdata/grafana is owned by nobody:users. No matter what I do from the configuration of the container, I can't force it to use this uid:gid. It insists on using 472:0 which I don't want it to use. Why is this container so difficult to manage?
July 3, 20251 yr Can anyone please help me with Telergaf? It is running based on the Docker tab, but it doesn't work in Grafana. When I check the logs, it doesn't do anything; it just closes immediately. When I check Glances, I see this:This has been running fine for months, but today it just looks like this.
August 17, 2025Aug 17 Has anyone run into any issues with Telegraf failing to start after updating the docker image? I originally set up Telegraf (and InfluxDB, and Grafana) when following this project: https://technicalramblings.com/blog/how-to-setup-grafana-influxdb-and-telegraf-to-monitor-your-unraid-system/Since setting it up some time back, I've continued to let the Telegraf, InfluxDB, and Grafana images update and everything has remained functional. However, after updating the Telegraf image recently, it will not start. The logs show the following errors:Reading package lists...Ign:1 http://security.debian.org/debian-security buster/updates InReleaseIgn:2 http://deb.debian.org/debian buster InReleaseErr:3 http://security.debian.org/debian-security buster/updates Release 404 Not Found [IP: 151.101.194.132 80]Ign:4 http://deb.debian.org/debian buster-updates InReleaseErr:5 http://deb.debian.org/debian buster Release 404 Not Found [IP: 151.101.194.132 80]Err:6 http://deb.debian.org/debian buster-updates Release 404 Not Found [IP: 151.101.194.132 80]
September 20, 2025Sep 20 I'm having issues with telegraph as well. I followed the same guide long ago. The .conf file that that website instructs you to use is also missing. I suspect that it would be best to figure out a new way to get everything running, but I don't want to risk losing all the data. Most of this grafana stuff is all way over my head.
November 29, 2025Nov 29 Hello,in my case all of sudden InfluxDB stopped to work, and of course my "Grafana-Unraid-Stack" is now death.Strange enough command "docker logs InfluxDB" doesn't return anything.When I try to start the docker I got: Execution error Server ERROR.Has someone any advice?Thanks
March 19Mar 19 I just got InfluxDB v3 Enterprise container working on my Unraid instance with a At-Home license. Wondering if there will ever be an official install package built for Unraid. I had to add several Environment variables to get it to work. If someone can help get it added officially i can provide what i had to do to get it to work. I also have a container for InfluxDB Explorer working as well.
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.