[Support] for atribe's repo Docker images


Recommended Posts

Hello, im new to unraid and this docker thing. I added influxdb docker container to my unraid server and restored some test data from one of my cloud servers. now i have one problem. to show this data in grafana i was using flux on my productive servers. flux is disabled in this docker container and there is no full influxdb.conf in /etc/influxdb to enable flux. how can i enable it the docker way?

Link to comment
  • 2 weeks later...

Heyo, I just setup Glances and I can access the webui but the RX & TX for the Containers is showing NaNb, anyone know how to get this to properly display the RX/TX? I've noticed it for Plex which is currently set to Host networking, the Glances docker is set to a Proxynet I've setup for my swag container. 

Link to comment
  • 2 weeks later...
On 3/20/2020 at 8:49 PM, tknx said:

For telegraf - is there a clean way to get it to use the telegraf.d for additional plugins?

 

I passed 


--config-directory /etc/telegraf/telegraf.d

as a post argument, but then in logs I get:

 


2020-03-20T19:42:08Z I! Starting Telegraf 1.13.4
2020-03-20T19:42:08Z I! Using config file: /etc/telegraf/telegraf.conf
2020-03-20T19:42:08Z W! Telegraf is not permitted to read /etc/telegraf/telegraf.d
...

all of the following are owned by nobody:users and have 777 permissions right now

  • /mnt/user/appdata/telegraf
  • /mnt/user/appdata/telegraf/telegraf.conf
  • /mnt/user/appdata/telegraf/telegraf.d
  • /mnt/user/appdata/telegraf/telegraf.d/etcetera.conf

 

So I am unsure as to why it is not permitted to read the telegraf.d directory

Did you get it to work in the end? I am facing a similar issue, but for me the docker does not mention yet reading the telegraf.d folder. My Post Argument looks like this

/bin/sh -c 'apt update && apt install -y smartmontools && apt install -y lm-sensors && apt install -y nvme-cli && apt install -y ipmitool && telegraf --config /etc/telegraf/telegraf.conf --config-directory /etc/telegraf/telegraf.d'

 

Any guidance is welcome!

Link to comment

Hi, I hope you can help me.
I used Grafana a while ago and everything was fine.
I had to reinstall Grafana now (hard disk dead, no parrity, I know...😑)
Anyway, no stats work now?! (the configuration is the same).
I searched several forums for the same problems, and tried everything, without success.😡
Is this a bug, can someone help me?

Grafana.png

Grafana1.png

Time zone in Grafana.png

Time zone in UNRAID.png

Link to comment

As mentioned above, the latest tag now installs influx 2.0 and a docker update automatically installed this for me.

 

It was causing Grafana to return Authorization errors for me so clearly not backward compatible.

 

Changing the tag within the Repository to 1.8 solved it for me.

 

Anyone migrated from 1.x to 2.0 yet? Any issues?

 

influx.png

  • Like 1
  • Thanks 3
Link to comment

Thanks so much for this info guys, I went to check my graphs before and wondered what the hell was going on - I'd lost connection to everything!  After reading your posts and changing the repo to be influxdb:1.8 I was back up and running in about 30 seconds.

 

Much appreciated!

  • Like 1
Link to comment

I just realized that my DB is getting error " influxdb lvl=info msg=Unauthorized log_id=0S_B9NMW000 error="token required" "

thought what is messed up again, seems like it was in this state for few weeks and not updating DB at all...

 

I found the suggestion to change the docker to 1.X instead of "latest"

Here are also all versions listed seems like https://hub.docker.com/_/influxdb/?tab=tags&page=1&ordering=last_updated

So currently im on "influxdb:1.8.4-alpine" version and it works! Thanks!

 

1. What the alpine means? (some Beta/Alpha release? )

2. If i want to move to "latest" again "2.X" what should i go? I see this post the telegraf part iI should be able to do, but i dont understand the "Grafana" part what is "InfluxDB OSS 2.0" do i want "Flux" or "InfluxQL" ?

3. Does the "old" data 1.X from telegraf will be kept also in 2.x+ version?

 

Thanks

On 2/25/2021 at 3:23 AM, JaseNZ said:

You would need to change telegraf.

https://docs.influxdata.com/influxdb/v2.0/write-data/no-code/use-telegraf/manual-config/

 

then this

 

https://docs.influxdata.com/influxdb/v2.0/tools/grafana/

 

For myself I don't see the need as I am only graphing all the metrics so would make no difference to me.

 

Link to comment

Hello! I'm currently trying to set up anon access in Grafana, in order to make the dashboard visible to others, but I cannot find grafana.ini, because it is located in another folder, not mapped in unRAID: every time I try to map it, the docker spits out errors, saying it cant locate the file grafana.ini or grafana-server is not available, and it doesn't start. I tried mapping it using paths from the docker setup and also using ENV variables, nothing worked. Sadly, there is no ENV variable solely for enabling anon log-in :(

 

I tried to bash into the container but for some reason the user is not root, so there is not much I can do, vim cant save the modified grafana.ini because of that. What shall I do?

Link to comment
On 3/2/2021 at 12:33 AM, Michel Amberg said:

So I just started getting this error a couple of days back any ideas?
image.png.8686ed5052c2b3b2ebcc512b07064764.png
 

I do have exactly the same

I did an upgrade of Unraid to 6.9.0

I think it has to do something with that

I'm not able to create and write to InfluxDB anymore from telegraf

I did change nothing in the setup

It did work for 6months without problems

image.png.0b19dad0744655e0c890a1627ad7ff0b.png

 

Edited by canedje
Link to comment
1 hour ago, canedje said:

I do have exactly the same

I did an upgrade of Unraid to 6.9.0

I think it has to do something with that

I'm not able to create and write to InfluxDB anymore from telegraf

I did change nothing in the setup

It did work for 6months without problems

image.png.0b19dad0744655e0c890a1627ad7ff0b.png

 

I fixed this downgrade to influx version 1.8 and problems go away

Link to comment
10 hours ago, Michel Amberg said:

I fixed this downgrade to influx version 1.8 and problems go away

I did downgrade.

It is working again

Thanks

 

 

Grafana is working again and I do see the graphs so I'm happy.

Telegraf log still showing a lot of errors:

image.png.4ab299e9d527cc7b248392b47513d3ad.png

Edited by canedje
Link to comment

Just to lend my voice to the list...InfluxDB 2.0 also broke everything for me. Grafana was throwing the access error, but it also turns out I was not capturing any data from multiple sources, including Telegraf. It's possible the return to 1.8 blew out what was captured during that time, but that would be surprising to me. Changing to 1.8 brought it back, with the data gap.

Link to comment

hi, first time using influxdb. seems the influx has changes since a lot of the guides was written. Im getting influxdb.exceptions.InfluxDBClientError: 401: {"code":"unauthorized","message":"Unauthorized"} When trying to use userid and password that i selected in influxdb. But with software that support token im getting a connection to the database. Is there a way to enable legacy use of userid/password?

Link to comment

Influx 2.0 update needs some work since it breaks the chronogragh and graphana connectors. From the official site there are various docker commands to run to get it to upgrade properly, not a simple image pull.

 

I rolled back to 1.8 for now, until its fixed or I rebuild it from the source. Influx2.0 seems to have a built in UI on port 9999, which this docker config doesn't natively map

 

A note in general, dont blindly upgrade docker containers without reading the repo notes.

Edited by sec787
Link to comment

Is there a workaround for the disk spin down issue after the 6.9 update caused by, among other factors, the telegraf hddtemp plugin? 

 

 

Also I noticed since a few days that I can't edit the influxdb container anymore. I could imagine that this came with the 2.0 change of the latest image.
In the GUI the name is just white and no longer clickable. The entry in the conext menu is also missing. Before the 6.9 update I could not update the container. The container name was blue and when I tried to update, I got the message that the configuration could not be found.
But the XML file on the flash exists and is exactly the same size as on a flash backup when everything was normal. Also a reinstallation of the 1.8 image, including deleting the previous image and deleting and recreating the config did not bring any improvement.

Link to comment

The solution for the non-editable container was to re-download Influxdb from the Apps tab and reconfigure everything like before except the extra parameter --name influxdb wich has caused the problem. As soon as you set it, the container gets in this status. I don't know why because I have other containers also configured with this parameter and their own name and no problems at all.

Edited by kennymc.c
  • Thanks 1
Link to comment

Hi,

 

I have the installed InfluxDB docker and I can log in and see and display data.

But I wonder why my appdata/influxdb directory remains empty. It seems as if tha data goes somewhere else. Perhaps in the image file?

I removed the docker and reinstalled form the apps tab making sure that the default configuration for Host Path 1 points to /mnt/user/appdata/influxdb/ . The success message after installation includes the desired path but also /var/lib/influxdb .243704998_Screenshot_2021-03-14FizUpdateContainer(1).thumb.png.615d683cf7f661752e06ec24697c94a5.png

 

I add the log after restart below. What puzzles me is the line

ts=2021-03-14T22:29:48.418174Z lvl=info msg="Using data dir" log_id=0StiaunG000 service=storage-engine service=store path=/var/lib/influxdb2/engine/data

 

What can I do to get the data written to a proper location?

 

Thanks in advance

Michael

 

2021-03-14T22:29:42.498767181Z warn boltdb not found at configured path, but DOCKER_INFLUXDB_INIT_MODE not specified, skipping setup wrapper {"system": "docker", "bolt_path": ""}
ts=2021-03-14T22:29:47.593475Z lvl=info msg="Welcome to InfluxDB" log_id=0StiaunG000 version=2.0.4 commit=4e7a59bb9a build_date=2021-02-08T17:47:02Z
ts=2021-03-14T22:29:47.614938Z lvl=info msg="Resources opened" log_id=0StiaunG000 service=bolt path=/var/lib/influxdb2/influxd.bolt
ts=2021-03-14T22:29:47.623203Z lvl=info msg="Bringing up metadata migrations" log_id=0StiaunG000 service=migrations migration_count=14
ts=2021-03-14T22:29:48.418174Z lvl=info msg="Using data dir" log_id=0StiaunG000 service=storage-engine service=store path=/var/lib/influxdb2/engine/data
ts=2021-03-14T22:29:48.418315Z lvl=info msg="Compaction settings" log_id=0StiaunG000 service=storage-engine service=store max_concurrent_compactions=2 throughput_bytes_per_second=50331648 throughput_bytes_per_second_burst=50331648
ts=2021-03-14T22:29:48.418333Z lvl=info msg="Open store (start)" log_id=0StiaunG000 service=storage-engine service=store op_name=tsdb_open op_event=start
ts=2021-03-14T22:29:48.418419Z lvl=info msg="Open store (end)" log_id=0StiaunG000 service=storage-engine service=store op_name=tsdb_open op_event=end op_elapsed=0.088ms
ts=2021-03-14T22:29:48.418489Z lvl=info msg="Starting retention policy enforcement service" log_id=0StiaunG000 service=retention check_interval=30m
ts=2021-03-14T22:29:48.418523Z lvl=info msg="Starting precreation service" log_id=0StiaunG000 service=shard-precreation check_interval=10m advance_period=30m
ts=2021-03-14T22:29:48.418756Z lvl=info msg="Starting query controller" log_id=0StiaunG000 service=storage-reads concurrency_quota=10 initial_memory_bytes_quota_per_query=9223372036854775807 memory_bytes_quota_per_query=9223372036854775807 max_memory_bytes=0 queue_size=10
ts=2021-03-14T22:29:48.419963Z lvl=info msg="Configuring InfluxQL statement executor (zeros indicate unlimited)." log_id=0StiaunG000 max_select_point=0 max_select_series=0 max_select_buckets=0
ts=2021-03-14T22:29:48.735702Z lvl=info msg=Starting log_id=0StiaunG000 service=telemetry interval=8h
ts=2021-03-14T22:29:48.735688Z lvl=info msg=Listening log_id=0StiaunG000 transport=http addr=:8086 port=8086
ts=2021-03-14T22:29:58.362115Z lvl=info msg=Unauthorized log_id=0StiaunG000 error="authorization not found"
ts=2021-03-14T22:29:59.014941Z lvl=info msg=Unauthorized log_id=0StiaunG000 error="session not found"
[...]
ts=2021-03-14T22:32:29.836588Z lvl=info msg="index opened with 8 partitions" log_id=0StiaunG000 service=storage-engine index=tsi
ts=2021-03-14T22:32:29.837291Z lvl=info msg="Reindexing TSM data" log_id=0StiaunG000 service=storage-engine engine=tsm1 db_shard_id=1
ts=2021-03-14T22:32:29.837311Z lvl=info msg="Reindexing WAL data" log_id=0StiaunG000 service=storage-engine engine=tsm1 db_shard_id=1

 

Link to comment

@kannznichkaufen If you're starting a new database with the influxdb/lastest image, it will use influxdb 2.0 which stores its data in /var/lib/influxdb2 according to the Docker hub page. This path is also mentioned in you log. Unfortunately the Unraid Influxdb App Template hasn't been updated, so you have to manually adjust HostPath 1. 

Maybe @atribe could change the default Host Path to /var/lib/influxdb2.

  • Thanks 1
Link to comment

Thank You for looking into it @kennymc.c

Changing Host Path 1 didn't change much. A new directory /appdata/influxdb2 is created but remains empty.

The log says

2021-03-14T23:23:42.532348802Z warn boltdb not found at configured path, but DOCKER_INFLUXDB_INIT_MODE not specified, skipping setup wrapper {"system": "docker", "bolt_path": ""}
ts=2021-03-14T23:23:47.947998Z lvl=info msg="Welcome to InfluxDB" log_id=0StlggQl000 version=2.0.4 commit=4e7a59bb9a build_date=2021-02-08T17:47:02Z
ts=2021-03-14T23:23:47.963094Z lvl=info msg="Resources opened" log_id=0StlggQl000 service=bolt path=/var/lib/influxdb2/influxd.bolt
ts=2021-03-14T23:23:47.970154Z lvl=info msg="Bringing up metadata migrations" log_id=0StlggQl000 service=migrations migration_count=14
ts=2021-03-14T23:23:48.918810Z lvl=info msg="Using data dir" log_id=0StlggQl000 service=storage-engine service=store path=/var/lib/influxdb2/engine/data
ts=2021-03-14T23:23:48.918919Z lvl=info msg="Compaction settings" log_id=0StlggQl000 service=storage-engine service=store max_concurrent_compactions=2 throughput_bytes_per_second=50331648 throughput_bytes_per_second_burst=50331648

 

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.