June 9, 20215 yr SpeedTestForInfluxDB seems to no longer work. I downgraded from influx 2 back to 1.8.6 since it broke too many things. But the speed test is no longer working (was working before) and get the following in the logs: Loading Configuration File config.ini Configuration Successfully Loaded 2021-06-09 20:32:17,631 - DEBUG: Testing connection to InfluxDb using provided credentials 2021-06-09 20:32:17,634 - DEBUG: Successful connection to InfluxDb 2021-06-09 20:32:17,634 - INFO: Starting Speed Test For Server None 2021-06-09 20:32:17,664 - DEBUG: Setting up SpeedTest.net client Traceback (most recent call last): File "/src/influxspeedtest.py", line 8, in <module> collector.run() File "/src/influxspeedtest/InfluxdbSpeedtest.py", line 173, in run self.run_speed_test() File "/src/influxspeedtest/InfluxdbSpeedtest.py", line 121, in run_speed_test self.setup_speedtest(server) File "/src/influxspeedtest/InfluxdbSpeedtest.py", line 71, in setup_speedtest self.speedtest = speedtest.Speedtest() File "/usr/local/lib/python3.7/site-packages/speedtest.py", line 1091, in __init__ self.get_config() File "/usr/local/lib/python3.7/site-packages/speedtest.py", line 1174, in get_config map(int, server_config['ignoreids'].split(',')) ValueError: invalid literal for int() with base 10: '' Loading Configuration File config.ini Configuration Successfully Loaded 2021-06-09 20:50:45,047 - DEBUG: Testing connection to InfluxDb using provided credentials 2021-06-09 20:50:45,050 - DEBUG: Successful connection to InfluxDb 2021-06-09 20:50:45,050 - INFO: Starting Speed Test For Server None 2021-06-09 20:50:45,058 - DEBUG: Setting up SpeedTest.net client Traceback (most recent call last): File "/src/influxspeedtest.py", line 8, in <module> collector.run() File "/src/influxspeedtest/InfluxdbSpeedtest.py", line 173, in run self.run_speed_test() File "/src/influxspeedtest/InfluxdbSpeedtest.py", line 121, in run_speed_test self.setup_speedtest(server) File "/src/influxspeedtest/InfluxdbSpeedtest.py", line 71, in setup_speedtest self.speedtest = speedtest.Speedtest() File "/usr/local/lib/python3.7/site-packages/speedtest.py", line 1091, in __init__ self.get_config() File "/usr/local/lib/python3.7/site-packages/speedtest.py", line 1174, in get_config map(int, server_config['ignoreids'].split(',')) ValueError: invalid literal for int() with base 10: ''
June 10, 20215 yr On 4/2/2021 at 8:10 PM, B0rax said: @canadje: It works for me. all the latest updates. I needed to change the location of influxdb data storage though. it also helps to change the web path to the correct port so you can use the influxdb webui. Is it possible to share your setting? I only have my influx settings like: Or do I need to change something in my Grafana settings? I don not understand what to change to use influxdb 2.0 with Grafana? Also my webui of influxdb is not working Edited June 11, 20215 yr by canedje
June 15, 20215 yr Something weird has been going on with Grafana. A short time ago, it updated to V8.0 which broke a bunch of my value mappings. I managed to fix those under new templates. Today there was another update for Grafana Docker and now it's back at version 7.5.8 which isn't even on their release page: https://grafana.com/docs/grafana/latest/release-notes/ This change back from 8.0 broke some of my dashboard panels again. for now I've gone and put in "grafana/grafana:8.0.2" as my repository to force the version as the default seems to not be consistent with what version it grabs and v7 to v8 changes a lot of the panel configs. Edited June 15, 20215 yr by axipher
June 28, 20215 yr Updated Grafana recently and I guess it went to v8.0.3. I didn’t have problems with my items (although it did change some of the coloring and formatting) but I’m now having Chrome and Chromium crashes on a couple of display systems. The Aw, Snap variety that don’t auto-recover. Anyone else dealing with this?
July 13, 20214 yr Is it possible to update the telegraf container so it supports URL based telegraf configurations from InfluxDB2.0? Edited July 13, 20214 yr by spyd4r
July 26, 20214 yr I am running the most recent version of Glances on unraid. It actually updated the other day. Today i have noticed that the docker will not start. Receiving the below error in my docker log. Anyone else seeing this or know how to fix? /usr/local/bin/python3: No module named glances
July 27, 20214 yr On 7/26/2021 at 5:46 AM, JohnSracic said: I am running the most recent version of Glances on unraid. It actually updated the other day. Today i have noticed that the docker will not start. Receiving the below error in my docker log. Anyone else seeing this or know how to fix? /usr/local/bin/python3: No module named glances Same error on my 6.9.2 box after the latest container update. Looks like there is already a GitHub issue targeting a fix in Glances 3.2.3 release: https://github.com/nicolargo/glances/issues/1905. Workaround would be to add a version tag to the container config like this: Edited July 27, 20214 yr by baccula
August 27, 20214 yr On 6/9/2021 at 1:53 PM, dandiodati said: SpeedTestForInfluxDB seems to no longer work. I downgraded from influx 2 back to 1.8.6 since it broke too many things. But the speed test is no longer working (was working before) and get the following in the logs: I just noticed that as of 8/25 at about 5am pt SpeedTest started working again. I didn't (or don't remember) make any changes, it just started working. Maybe take another look at yours.
August 31, 20214 yr I've been using Grafana flawlessly for over a year with InfluxDB and Varken behind the Ultimate Unraid Dashboard 1.5. I'm not sure if it was a Docker container update for any of the three above, but now Plex data is not showing in the Grafana Dashboard. Attached is an example for "TV Shows added this week" All other Plex data (Streams, Clients, etc) is showing old or no data. If it helps diagnose, all other Unraid data on the dashboard is working fine EXCEPT "data added to array" info for day, month, year. Its like that counter reset, I'm guessing the same time as the Varken data went wonky. I've looked at the Varken and InfluxDB databases, rolled back their docker containers, no luck. Any help or guidance appreciated.
September 1, 20214 yr On 8/30/2021 at 9:07 PM, joshallen2k said: I've been using Grafana flawlessly for over a year with InfluxDB and Varken behind the Ultimate Unraid Dashboard 1.5. I'm not sure if it was a Docker container update for any of the three above, but now Plex data is not showing in the Grafana Dashboard. Attached is an example for "TV Shows added this week" All other Plex data (Streams, Clients, etc) is showing old or no data. If it helps diagnose, all other Unraid data on the dashboard is working fine EXCEPT "data added to array" info for day, month, year. Its like that counter reset, I'm guessing the same time as the Varken data went wonky. I've looked at the Varken and InfluxDB databases, rolled back their docker containers, no luck. Any help or guidance appreciated. Anyone with any thoughts at all on this? Thanks!
September 22, 20214 yr mounted /etc/grafana/grafana.ini changed data in grafana.ini ,its also changed inside the container /etc/grafana/grafana.ini but its not show up in grafana program ..... any help please ?
September 28, 20214 yr Can someone please explain how I fix InfluxDB Error: Bad Gateway. Its doing my head in. I have read every thread in the world about this. Everything seems to refer to docker compose, I just feel like every docker in community apps is broken some how and I would be better off with compose lol. Any hints for a moron here? I have everything else going influxdb is receiving data and I can easily access its web gui so I know its working. I have tried entering the Ip and entering the container name nothing works Edited September 28, 20214 yr by garethsnaim
October 16, 20214 yr Anybody had Telegraf not detecting all network interfaces ? I have Network card in bond and some VLANs... in Telegraf I setup inputs.net without parameters to take all (I also tried to specify which interfaces) but in the Grafana I can only see some of them. See the attached pic. But my ip a looks like this: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN group default qlen 1000 link/gre 0.0.0.0 brd 0.0.0.0 4: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1476 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1464 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 6: ip_vti0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 10: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq master bond0 state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff 11: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq master bond0 state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff permaddr 68:05:ca:3c:9d:53 12: bond0: <BROADCAST,MULTICAST,PROMISC,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff 13: bond0.1020@bond0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0.1020 state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff 14: bond0.1030@bond0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0.1030 state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff 15: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff inet 10.0.0.2/24 scope global br0 valid_lft forever preferred_lft forever 16: br0.1020: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff 17: br0.1030: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff 18: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000 link/none inet 10.253.0.1/32 scope global wg0 valid_lft forever preferred_lft forever 19: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:15:79:85:f5 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever 21: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:aa:0f:96 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 22: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:aa:0f:96 brd ff:ff:ff:ff:ff:ff I would like at least the bond0 to be monitored (so far I have it via plugin in unraid that generate graphs ok, but not in Grafana...)
October 16, 20214 yr 8 hours ago, VladoPortos said: Anybody had Telegraf not detecting all network interfaces ? I have Network card in bond and some VLANs... in Telegraf I setup inputs.net without parameters to take all (I also tried to specify which interfaces) but in the Grafana I can only see some of them. See the attached pic. But my ip a looks like this: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN group default qlen 1000 link/gre 0.0.0.0 brd 0.0.0.0 4: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1476 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1464 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 6: ip_vti0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 10: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq master bond0 state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff 11: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc fq master bond0 state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff permaddr 68:05:ca:3c:9d:53 12: bond0: <BROADCAST,MULTICAST,PROMISC,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff 13: bond0.1020@bond0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0.1020 state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff 14: bond0.1030@bond0: <BROADCAST,MULTICAST,PROMISC,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0.1030 state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff 15: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff inet 10.0.0.2/24 scope global br0 valid_lft forever preferred_lft forever 16: br0.1020: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff 17: br0.1030: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 68:05:ca:3c:9d:52 brd ff:ff:ff:ff:ff:ff 18: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000 link/none inet 10.253.0.1/32 scope global wg0 valid_lft forever preferred_lft forever 19: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:15:79:85:f5 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever 21: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:aa:0f:96 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 22: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:aa:0f:96 brd ff:ff:ff:ff:ff:ff I would like at least the bond0 to be monitored (so far I have it via plugin in unraid that generate graphs ok, but not in Grafana...) Ok I will answer my own question. The image absolutely have to be as Network Type: Host ( I had it on its own VLAN ) otherwise for some unknown reason even though we are mounting /proc into the container the file /proc/net/dev is different in container (It does not make sense... ) and you can't even mount it directly, the container will not start... so Host only to have network... :-/ https://github.com/influxdata/telegraf/issues/4505
October 20, 20214 yr Hey Folks, I've run into an issue where whenever I update my InfluxDB container (it's running v 2.x) it wipes all the existing data and seems to update it to the latest version. I therefore lose the entire config and all my data. Any idea why this might be? Here's a picture of my container config page. Any help would be most appreciated Edited October 20, 20214 yr by Lohita
October 21, 20214 yr I have the same problem as Lohita above. Updated the docker from 2.0.x (unsure which flavor it was in June) using 'influxdb:latest' during the upgrade process within unraid, then when I start the Docker image I get the Influx Onboarding process. More information: I can see my influx folders at: /appdata/influxdb/data, /appdata/influxdb/meta, /appdata/influxdb/wal. All my data lives in the /data folder and is visible to the share. On the flash drive, I see: /boot/config/plugins/dockerMan/templates-user/my-Influxdb.xml, which contains the following: <Data> <Volume> <HostDir>/mnt/user/appdata/influxdb</HostDir> <ContainerDir>/var/lib/influxdb</ContainerDir> <Mode>rw</Mode> </Volume> </Data> <Environment/> <Labels/> <Config Name="Host Port 1" Target="8083" Default="8083" Mode="tcp" Description="Container Port: 8083" Type="Port" Display="always" Required="true" Mask="false">8083</Config> <Config Name="Host Port 2" Target="8086" Default="8086" Mode="tcp" Description="Container Port: 8086" Type="Port" Display="always" Required="true" Mask="false">8086</Config> <Config Name="Host Path 1" Target="/var/lib/influxdb" Default="/mnt/user/appdata/influxdb" Mode="rw" Description="Container Path: /var/lib/influxdb" Type="Path" Display="always" Required="true" Mask="false">/mnt/user/appdata/influxdb</Config> My shares include one named appdata, set to Public, Prefer: Cache. This share seems to go to the /appdata folder. Inside of Krusader, it looks like: /media/appdata. I hope someone can help me here.
October 29, 20214 yr Some changes was few hours ago in https://hub.docker.com/_/telegraf After auto-update (i use telegraf:alpine tag) container stoped working, log: All versions below not working too. Only 1.17.3-alpine still functional well Edited October 29, 20214 yr by Nuke
October 29, 20214 yr 1 hour ago, Nuke said: Some changes was few hours ago in https://hub.docker.com/_/telegraf After auto-update (i use telegraf:alpine tag) container stoped working, log: All versions below not working too. Only 1.17.3-alpine still functional well Yeah i set mine to telegraf:1.20.2 I guess unless there is really something specific thats new that's extra you want to gather metrics on there is not really any point in upgrading.
October 29, 20214 yr Thanks for that. Yup having the same problem since updating, changing to telegraf:1.20.2-alpine worked for me too. Edited October 30, 20214 yr by 1471
October 30, 20214 yr 18 hours ago, Nuke said: Some changes was few hours ago in https://hub.docker.com/_/telegraf After auto-update (i use telegraf:alpine tag) container stoped working, log: All versions below not working too. Only 1.17.3-alpine still functional well I was having the same problem, noticed it updated over night and now doesn't work. TL;DR this happens in the new version because the docker no longer runs under root and I had some extra parameters that's running `apk` which isn't allowed by the new telegraf user. Longer explain: A google lead me to info about it being a user permission issue: https://stackoverflow.com/questions/50727783/alpine-docker-error-unable-to-lock-database-permission-denied-error-failed-to Then looked at the dockerfile in github, it seems prior to Oct 15, the telegraf docker was running as root. They changed this to use 'telegraf' user, see commit here: https://github.com/influxdata/influxdata-docker/commit/83520188be87cbee6edb3ac995c647cf99acdf51 The error in my case was happening becuase I add some apk pakages by docker settings -> advanced -> Post Arguments /bin/sh -c 'apk update && apk add lm_sensors lm-sensors-detect perl && apk add smartmontools && apk add nvme-cli && telegraf' After removing those argument, I simply get an error in the log because it can't find smart (which was removed): After commenting out inputs.smart in my config I could start telegraf again. In my case, the graphs and data I use actually wasn't affected by not having inputs.smart, so I didn't reconfigure it. But this may help others if they don't want to pin telegraf to an older/specific tag.
October 31, 20214 yr i downgraded to 1.20.2-alpine and no longer face the apt error but now i have new issue whereby it cant connect to influxdb:1.18.4-alpine When writing to [http://192.168.xx.xx:8086]: database "telegraf" creation failed: Post "http://192.168.xx.xx:8086/query": dial tcp 192.168.xx.xx:8086: connect: no route to host No changes to my network was done
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.