Jump to content
atribe

[Support] for atribe's repo Docker images

436 posts in this topic Last Reply

Recommended Posts

On 4/25/2018 at 1:22 PM, GilbN said:

 

Have you figured this out yet?

 

No not yet.  It's easy to see the UPS power info I want at the command line with `apcaccess` but I don't know how to get the info into telegraf -> InfluxDB -> Grafana.

 

 

 

On 2/12/2018 at 9:47 PM, sureguy said:

Just a small note that if there is a docker update you will have to perform the above steps again.  At least I did after the last docker update.

 

Yeah, I have auto-update for Docker containers, and every so often I lose all of my (non-HDD) temp sensors.  When I notice a blank spot in my temperature chart I have to do this:

docker exec -ti telegraf /bin/sh
apk update 
apk add lm_sensors

Which is annoying.  Anybody know how to either make lm_sensors stay added permanently, or auto-run these commands on any update?

Share this post


Link to post

You'd have to find a different docker image or make your own

Sent from my Pixel XL using Tapatalk

Share this post


Link to post
13 hours ago, cowboytronic said:

 

No not yet.  It's easy to see the UPS power info I want at the command line with `apcaccess` but I don't know how to get the info into telegraf -> InfluxDB -> Grafana.

 

 

 

 

Yeah, I have auto-update for Docker containers, and every so often I lose all of my (non-HDD) temp sensors.  When I notice a blank spot in my temperature chart I have to do this:


docker exec -ti telegraf /bin/sh
apk update 
apk add lm_sensors

Which is annoying.  Anybody know how to either make lm_sensors stay added permanently, or auto-run these commands on any update?

I requested it on their git page - but aside from one other person asking for the same thing there's been no other traction.

 

You could just make a script that you can run after it's updated - you'd have to run it manually, but it's easier than having to remember the commands (apt vs apk etc).

 

 

Share this post


Link to post
On 28.4.2018 at 11:24 PM, cowboytronic said:

No not yet.  It's easy to see the UPS power info I want at the command line with `apcaccess` but I don't know how to get the info into telegraf -> InfluxDB -> Grafana.

 

I made this guide using Viaduct's script. 

https://technicalramblings.com/blog/setting-grafana-influxdb-telegraf-ups-monitoring-unraid/

It's not perfect as I would really like it to update influxdb more often than every minute. 

Edited by GilbN

Share this post


Link to post

Hi,

 

I have InfluxDB/Grafana/Telegraf setup for system monitoring.

 

My docker img has become very full due to InfluxDB logs (1.8GB/1.6GB json files). Is there any way to have this setup write to a different directory instead of /var/lib/docker/containers/xxxx?

 

Thanks!

Share this post


Link to post
On 4/29/2018 at 8:08 AM, GilbN said:

 

I made this guide using Viaduct's script. 

https://technicalramblings.com/blog/setting-grafana-influxdb-telegraf-ups-monitoring-unraid/

It's not perfect as I would really like it to update influxdb more often than every minute. 

 

Thanks!  This works, and it was really easy to replicate your script to my setup.  

 

I agree it would be nice to log more often than 1 minute intervals, but for long term power consumption trends this is good enough for me.  Certainly better than the zero logging I had before.

Share this post


Link to post

Had this docker working great until the last update on either the Grafana docker, or the InfluxDB docker. Not sure which one broke it. But I get a "cannot write to readonly database" error when I try to start Grafana.

 

Anyone have a clue?

 

Log:

 

t=2018-05-07T00:22:38-0400 lvl=info msg="Starting Grafana" logger=server version=5.1.0 commit=844bdc53a compiled=2018-04-26T11:09:23-0400

t=2018-05-07T00:22:38-0400 lvl=info msg="Config loaded from" logger=settings file=/usr/share/grafana/conf/defaults.ini
t=2018-05-07T00:22:38-0400 lvl=info msg="Config loaded from" logger=settings file=/etc/grafana/grafana.ini
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.data=/var/lib/grafana"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.logs=/var/log/grafana"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.plugins=/var/lib/grafana/plugins"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.provisioning=/etc/grafana/provisioning"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from command line" logger=settings arg="default.log.mode=console"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_DATA=/var/lib/grafana"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_LOGS=/var/log/grafana"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_PLUGINS=/var/lib/grafana/plugins"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_PROVISIONING=/etc/grafana/provisioning"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SERVER_ROOT_URL=http://192.168.1.3"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_ADMIN_PASSWORD=*********"
t=2018-05-07T00:22:38-0400 lvl=info msg="Path Home" logger=settings path=/usr/share/grafana
t=2018-05-07T00:22:38-0400 lvl=info msg="Path Data" logger=settings path=/var/lib/grafana
t=2018-05-07T00:22:38-0400 lvl=info msg="Path Logs" logger=settings path=/var/log/grafana
t=2018-05-07T00:22:38-0400 lvl=info msg="Path Plugins" logger=settings path=/var/lib/grafana/plugins
t=2018-05-07T00:22:38-0400 lvl=info msg="Path Provisioning" logger=settings path=/etc/grafana/provisioning
t=2018-05-07T00:22:38-0400 lvl=info msg="App mode production" logger=settings
t=2018-05-07T00:22:38-0400 lvl=info msg="Initializing DB" logger=sqlstore dbtype=sqlite3
t=2018-05-07T00:22:38-0400 lvl=info msg="Starting DB migration" logger=migrator
t=2018-05-07T00:22:38-0400 lvl=info msg="Executing migration" logger=migrator id="copy data account to org"
t=2018-05-07T00:22:38-0400 lvl=info msg="Skipping migration condition not fulfilled" logger=migrator id="copy data account to org"
t=2018-05-07T00:22:38-0400 lvl=info msg="Executing migration" logger=migrator id="copy data account_user to org_user"
t=2018-05-07T00:22:38-0400 lvl=info msg="Skipping migration condition not fulfilled" logger=migrator id="copy data account_user to org_user"
t=2018-05-07T00:22:38-0400 lvl=info msg="Executing migration" logger=migrator id="create user auth table"
t=2018-05-07T00:22:38-0400 lvl=eror msg="Executing migration failed" logger=migrator id="create user auth table" error="attempt to write a readonly database"

t=2018-05-07T00:22:38-0400 lvl=eror msg="Exec failed" logger=migrator error="attempt to write a readonly database" sql="CREATE TABLE IF NOT EXISTS `user_auth` (\n`id` INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL\n, `user_id` INTEGER NOT NULL\n, `auth_module` TEXT NOT NULL\n, `auth_id` TEXT NOT NULL\n, `created` DATETIME NOT NULL\n);"

t=2018-05-07T00:22:38-0400 lvl=eror msg="Fail to initialize orm engine" logger=sqlstore error="Sqlstore::Migration failed err: attempt to write a readonly database\n"

 

Share this post


Link to post
18 minutes ago, djvj said:

Had this docker working great until the last update on either the Grafana docker, or the InfluxDB docker. Not sure which one broke it. But I get a "cannot write to readonly database" error when I try to start Grafana.

 

Anyone have a clue?

 

Log:

 


t=2018-05-07T00:22:38-0400 lvl=info msg="Starting Grafana" logger=server version=5.1.0 commit=844bdc53a compiled=2018-04-26T11:09:23-0400

t=2018-05-07T00:22:38-0400 lvl=info msg="Config loaded from" logger=settings file=/usr/share/grafana/conf/defaults.ini
t=2018-05-07T00:22:38-0400 lvl=info msg="Config loaded from" logger=settings file=/etc/grafana/grafana.ini
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.data=/var/lib/grafana"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.logs=/var/log/grafana"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.plugins=/var/lib/grafana/plugins"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from command line" logger=settings arg="default.paths.provisioning=/etc/grafana/provisioning"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from command line" logger=settings arg="default.log.mode=console"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_DATA=/var/lib/grafana"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_LOGS=/var/log/grafana"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_PLUGINS=/var/lib/grafana/plugins"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_PATHS_PROVISIONING=/etc/grafana/provisioning"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SERVER_ROOT_URL=http://192.168.1.3"
t=2018-05-07T00:22:38-0400 lvl=info msg="Config overridden from Environment variable" logger=settings var="GF_SECURITY_ADMIN_PASSWORD=*********"
t=2018-05-07T00:22:38-0400 lvl=info msg="Path Home" logger=settings path=/usr/share/grafana
t=2018-05-07T00:22:38-0400 lvl=info msg="Path Data" logger=settings path=/var/lib/grafana
t=2018-05-07T00:22:38-0400 lvl=info msg="Path Logs" logger=settings path=/var/log/grafana
t=2018-05-07T00:22:38-0400 lvl=info msg="Path Plugins" logger=settings path=/var/lib/grafana/plugins
t=2018-05-07T00:22:38-0400 lvl=info msg="Path Provisioning" logger=settings path=/etc/grafana/provisioning
t=2018-05-07T00:22:38-0400 lvl=info msg="App mode production" logger=settings
t=2018-05-07T00:22:38-0400 lvl=info msg="Initializing DB" logger=sqlstore dbtype=sqlite3
t=2018-05-07T00:22:38-0400 lvl=info msg="Starting DB migration" logger=migrator
t=2018-05-07T00:22:38-0400 lvl=info msg="Executing migration" logger=migrator id="copy data account to org"
t=2018-05-07T00:22:38-0400 lvl=info msg="Skipping migration condition not fulfilled" logger=migrator id="copy data account to org"
t=2018-05-07T00:22:38-0400 lvl=info msg="Executing migration" logger=migrator id="copy data account_user to org_user"
t=2018-05-07T00:22:38-0400 lvl=info msg="Skipping migration condition not fulfilled" logger=migrator id="copy data account_user to org_user"
t=2018-05-07T00:22:38-0400 lvl=info msg="Executing migration" logger=migrator id="create user auth table"
t=2018-05-07T00:22:38-0400 lvl=eror msg="Executing migration failed" logger=migrator id="create user auth table" error="attempt to write a readonly database"

t=2018-05-07T00:22:38-0400 lvl=eror msg="Exec failed" logger=migrator error="attempt to write a readonly database" sql="CREATE TABLE IF NOT EXISTS `user_auth` (\n`id` INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL\n, `user_id` INTEGER NOT NULL\n, `auth_module` TEXT NOT NULL\n, `auth_id` TEXT NOT NULL\n, `created` DATETIME NOT NULL\n);"

t=2018-05-07T00:22:38-0400 lvl=eror msg="Fail to initialize orm engine" logger=sqlstore error="Sqlstore::Migration failed err: attempt to write a readonly database\n"

 

I'd suggest trying to recreate your influxdb. delete the current db in the apps folder and let it make a new one.

Share this post


Link to post
On 5/1/2018 at 9:59 PM, Blaze9 said:

Hi,

 

I have InfluxDB/Grafana/Telegraf setup for system monitoring.

 

My docker img has become very full due to InfluxDB logs (1.8GB/1.6GB json files). Is there any way to have this setup write to a different directory instead of /var/lib/docker/containers/xxxx?

 

Thanks!

Not sure off the top of my head. I'd suggest figure out where the logs are being written to and then add that as a path for the container to some place you like them to go.

Share this post


Link to post

I updated to Unraid 6.5.1 and now Telegraf cannot start up. I am getting this error in the Telegraf log:

2018-05-06T07:00:40Z E! [outputs.influxdb]: when writing to [http://10.100.100.100:8086]: Post http://10.100.100.100:8086/write?consistency=any&db=telegraf: dial tcp 10.100.100.100:8086: getsockopt: connection refused
2018-05-06T07:00:40Z E! Error writing to output [influxdb]: could not write any address

Tried restarting influxdb as well but the issue with telegraf still persists.

Share this post


Link to post
On 5/7/2018 at 12:59 AM, atribe said:

Not sure off the top of my head. I'd suggest figure out where the logs are being written to and then add that as a path for the container to some place you like them to go.

 

 

I'm thinking this is docker log and not the actual container database.. Wonder if clearing it would be OK or not... Hmm.

Share this post


Link to post
On 5/7/2018 at 12:58 AM, atribe said:

I'd suggest trying to recreate your influxdb. delete the current db in the apps folder and let it make a new one.

Thanks, I ended up having to recreate the grafana docker from scratch to fix. Hopefully it doesn't happen again.

Share this post


Link to post

Does telegraf support NVMe drives? I don't see stats on my samsung nvme in the influxdb being recorded.

Share this post


Link to post
On 5/23/2018 at 11:51 AM, remati said:

Does telegraf support NVMe drives? I don't see stats on my samsung nvme in the influxdb being recorded.

:shrug: I would assume so, but I have no idea.

Share this post


Link to post

For those using the instructions posted on reddit to set Grafana, InfluxDB, and Telegraf up found 

The instructions for using hddtemp can be amended to just searching community apps for hddtemp and using the template I just uploaded (not sure the refresh cycle on CA so it might take some time to show up.) I basically just took the instructions on using docker hub and made an unRAID template out of it. Enjoy.

Share this post


Link to post
On 5/24/2018 at 3:51 AM, remati said:

Does telegraf support NVMe drives? I don't see stats on my samsung nvme in the influxdb being recorded.

 

I've looked into this myself in recent months. TLDR; No but personally I have a custom script which works for my setup, but there some inconvenience in setting it up and maintaining it...

I also noticed someone has recently made a request for this in telegraf (https://github.com/influxdata/telegraf/issues/4169)

 

If you put this code into a script called nvmetemp.sh in your /mnt/user/appdata/telegraf:

#!/bin/sh

for device in /dev/nvme[0-9]; do
	temp=`smartctl -a $device | grep Temperature | awk '{print $2}'`
	serial=`smartctl -a $device | grep Serial | awk '{print $3}'`
	percent=`smartctl -a $device | grep Percentage | awk '{print $3}' | sed 's/.$//'`
	echo "disk,device=$device,serial=$serial temperature=$temp,percent_used=$percent"
done

 

Then you need to change a couple of things inside the docker (which you get a shell to by typing "docker exec -it telegraf /bin/sh" without quotes): (**Note comments about adding smartmontools package below)

apk add smartmontools
chmod 755 /config/nvmetemp.sh

**Note smartmontools won't be installed the next time your docker updates to a new version. So if you have auto-update dockers it disappears and your temp is no longer recorded. You have to do the same process of adding the package inside the docker (apk add smartmontools) every time the docker updates.

 

Then un-comment in your telegraf.conf [[inputs.exe]] so it should look something like this:

[[inputs.exec]]
	commands = ["sh /config/nvmetemp.sh"]
	timeout = "10s"
	data_format = "influx"

 

The actual problem is the method used to get disk temperatures by Telegraf - I think it grep's the string from the smartctl -a /dev/*** command output. NVME devices have a different text format in smartctl, thus Telegraf doesn't find the NVME temp. It seems to me like the plugins [[inputs.sensors]] and [[inputs.smart]] use the same method of getting the disk temperatures.

 

 

Edited by dazzathewiz

Share this post


Link to post

hi,

 

i have installed the minecraft docker, i noticed its very similar to another minecraft docker i tried, i am having the same issues as i had previously with other dockers, any minecraft servers i create and not surviving a reboot of unraid, i can see the servers if i FTP to server folders and they persist, just not in the GUI, its clearly something with my setup but i cant see it...

i have it set to /mnt/user/appdata/minecraft and my appdata folder is set to cache only

Share this post


Link to post
9 minutes ago, loady said:

hi,

 

i have installed the minecraft docker, i noticed its very similar to another minecraft docker i tried, i am having the same issues as i had previously with other dockers, any minecraft servers i create and not surviving a reboot of unraid, i can see the servers if i FTP to server folders and they persist, just not in the GUI, its clearly something with my setup but i cant see it...

i have it set to /mnt/user/appdata/minecraft and my appdata folder is set to cache only

 

Sounds like your docker is not setup correctly. Do any docker containers persist? If not I'd check your docker settings to make sure they are similar to what I have.

image.png.0c82893c8cee2524dc233dabb55462db.png

 

Share this post


Link to post

all my docker container persist (i believe) as i have no issues with any other dockers. You can see the servers i created in the servers folder, they just dissapear from the GUI

 

Screenshot 2018-06-05 17.10.47.png

 

Screenshot 2018-06-05 17.18.24.png

Screenshot 2018-06-05 17.12.08.png

Screenshot 2018-06-05 17.25.33.png

Edited by loady
added another shot

Share this post


Link to post
3 hours ago, atribe said:

 

Sounds like your docker is not setup correctly. Do any docker containers persist? If not I'd check your docker settings to make sure they are similar to what I have.

image.png.0c82893c8cee2524dc233dabb55462db.png

 

 

I have been playing about, i can get the servers to show up after a reboot now, but i have to change the group/user properties to 1000:1000, however, after a reboot they are going back to nobody:99 and group:users100

Share this post


Link to post

Can anyone help me with this, or point me to where i should be looking, i can only get servers to show after changing permissions but after reboot permissions are getting reset for the folder, i know its something with my unraid setup now

Share this post


Link to post

I've been running a MineOS-node server for a long time, however I just recently noticed that the Web UI isn't responding. I tried removing and re-installing the docker but it didn't have any effect.

 

The servers I had set to run at startup are still responding, I just have no way to manage them from the UI.

 

Am I alone in this issue? what can I check next?

 

Below is my log file:

 

USER_NAME not provided; defaulting to "mc"
Created user: mc (uid: 1000)
Generating Self-Signed SSL...
Generating a 1024 bit RSA private key
........++++++
...........++++++
writing new private key to '.tmpkey.pem'
-----
writing RSA key
2018-06-18 21:48:03,051 CRIT Supervisor running as root (no user in config file)
2018-06-18 21:48:03,051 INFO Included extra file "/etc/supervisor/conf.d/mineos.conf" during parsing
2018-06-18 21:48:03,059 INFO RPC interface 'supervisor' initialized
2018-06-18 21:48:03,059 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2018-06-18 21:48:03,059 INFO supervisord started with pid 1
2018-06-18 21:48:04,060 INFO spawned: 'mineos' with pid 31
2018-06-18 21:48:05,443 INFO success: mineos entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-06-18 22:02:58,402 WARN received SIGTERM indicating exit request
2018-06-18 22:02:58,402 INFO waiting for mineos to die
2018-06-18 22:02:58,409 INFO stopped: mineos (terminated by SIGTERM)
USER_NAME not provided; defaulting to "mc"
mc already exists.
2018-06-18 22:15:15,200 CRIT Supervisor running as root (no user in config file)
2018-06-18 22:15:15,200 INFO Included extra file "/etc/supervisor/conf.d/mineos.conf" during parsing
2018-06-18 22:15:15,208 INFO RPC interface 'supervisor' initialized
2018-06-18 22:15:15,208 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2018-06-18 22:15:15,209 INFO supervisord started with pid 1
2018-06-18 22:15:16,211 INFO spawned: 'mineos' with pid 10
2018-06-18 22:15:17,562 INFO success: mineos entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-06-18 22:15:57,459 WARN received SIGTERM indicating exit request
2018-06-18 22:15:57,459 INFO waiting for mineos to die
2018-06-18 22:15:57,462 INFO stopped: mineos (terminated by SIGTERM)
USER_NAME not provided; defaulting to "mc"
mc already exists.
2018-06-18 22:16:20,203 CRIT Supervisor running as root (no user in config file)
2018-06-18 22:16:20,203 INFO Included extra file "/etc/supervisor/conf.d/mineos.conf" during parsing
2018-06-18 22:16:20,209 INFO RPC interface 'supervisor' initialized
2018-06-18 22:16:20,209 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2018-06-18 22:16:20,209 INFO supervisord started with pid 1
2018-06-18 22:16:21,210 INFO spawned: 'mineos' with pid 9
2018-06-18 22:16:22,588 INFO success: mineos entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-06-18 22:17:04,203 WARN received SIGTERM indicating exit request
2018-06-18 22:17:04,203 INFO waiting for mineos to die
2018-06-18 22:17:04,209 INFO stopped: mineos (terminated by SIGTERM)
USER_NAME not provided; defaulting to "mc"
mc already exists.
2018-06-18 22:24:02,047 CRIT Supervisor running as root (no user in config file)
2018-06-18 22:24:02,047 INFO Included extra file "/etc/supervisor/conf.d/mineos.conf" during parsing
2018-06-18 22:24:02,055 INFO RPC interface 'supervisor' initialized
2018-06-18 22:24:02,055 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2018-06-18 22:24:02,055 INFO supervisord started with pid 1
2018-06-18 22:24:03,057 INFO spawned: 'mineos' with pid 9
2018-06-18 22:24:04,387 INFO success: mineos entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

 

Share this post


Link to post

Hi where is the database stored for influxDB? I think its in the docker.img but why? it will only increase the volume. why not save the databse to appdata?

 

Just trying to figure out the logic behind it all.

Share this post


Link to post
39 minutes ago, BelgarionNL said:

Hi where is the database stored for influxDB? I think its in the docker.img but why? it will only increase the volume. why not save the databse to appdata?

 

Just trying to figure out the logic behind it all.

There is a default mapping to /mnt/user/appdata/influxdb from /var/lib/influxdb. That is where the data is stored.

Share this post


Link to post

Hello,

 

Occasionally my influxdb and grafana container CPU usage will spike incredibly high. It seems random. But I've seen it happen about 3 times in the last week or so. It's using so much CPU that the rest of the unraid system is nearly unresponsive. If I execute "docker stats" from the command line it will take literally 2 minutes for the result to come up. When it does, it says that both influxdb and grafana are using extremely high CPU. If I execute a restart of the influxdb container, everything goes back to normal. 

 

Ideally, someone knows what is causing it just by my description. However, if that's not possible, can someone explain what logs or location I can look at or even a debug/capture I can keep running somewhere that can help track down why it's doing this? 

 

I am not sure this is super helpful, but you can sort of see some weirdness around the time this started happening in this attached screenshot. 

 

A few random observations: I also run Netdata and I notice the container just stopped itself right about the same time these issues started up. I did notice Netdata had stopped itself a few times in the past week and now I'm thinking it probably happened at the same time I saw these issues before. 

 

Any ideas?

 

 

influxdb_only.jpg

unraid_cpu.JPG

Share this post


Link to post

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.