JudMeherg

Amazing! Simply amazing this has been updated again! Thanks for all the hard work. Now its time to see if it can be translated to a Jellyfin/Jellystat version. Thanks for all the hard work falcon!

For some reason "docker exec -it paperless_ngx-webserver-1 document_exporter ../export". I guess the -i flag made all the difference. Thank you for pointing this point! You are right it should point to the export folder mounted inside the container.

Thank you for the reply! I had tried your suggestion, maybe I should have added more information. Here are the results of docker compose ls root@Tower:~# docker compose ls NAME STATUS CONFIG FILES immich running(8) /boot/config/plugins/compose.manager/projects/immich/docker-compose.yml,/boot/config/plugins/compose.manager/projects/immich/docker-compose.override.yml paperless_ngx running(3) /boot/config/plugins/compose.manager/projects/paperless-ngx/docker-compose.yml,/boot/config/plugins/compose.manager/projects/paperless-ngx/docker-compose.override.yml This is a screenshot of the stack folder: And here are a few more ways I have tried to run the command: root@Tower:~# docker compose -f '/boot/config/plugins/compose.manager/projects/paperless-ngx/docker-compose.yml' exec -T paperless_ngx-webserver-1 document_exporter /mnt/user/backup/paperless-ng service "paperless_ngx-webserver-1" is not running root@Tower:~# docker compose -f '/boot/config/plugins/compose.manager/projects/paperless-ngx/docker-compose.yml' exec -T webserver-1 document_expo rter /mnt/user/backup/paperless-ng service "webserver-1" is not running root@Tower:~# docker compose exec -T paperless_ngx-webserver-1 document_exporter /mnt/user/backup/paperless-ng no configuration file provided: not found Here is my compose file: I am still not sure what I am missing.

Hello fair users and awesome developers! Loving the plugin for immich and paperless-ngx! There is just one thing I cannot figure out. On my previous paperless-ngx install via docker compose on ubuntu server I had a cron job running to call the paperless exporter and make a backup of all the files in paperless. #!/bin/sh cd /home/server1/paperless-ng /usr/local/bin/docker-compose exec webserver document_exporter ../export However, I cannot quite get it to work with compose manager on Unraid. Whenever I try to call the webserver document_exporter, docker compose says "service webserver isn't running." root@Tower:/mnt/user/backup# docker-compose -f '/boot/config/plugins/compose.manager/projects/paperless-ngx/docker-compose.yml' exec -T webserver document_exporter ../paperless-ng Or root@Tower:/boot/config/plugins/compose.manager/projects/paperless-ngx# docker compose exec -T webserver document_exporter /mnt/user/backup/paperless-ng Above are the commands I have tried using to call the export, but the same result. Is there some special trick to address a container started via the compose manager?

New cable installed. Seems to be fine. tower-diagnostics-20230903-1557-6.12.3.zip

Hello, This morning I did my normal update upgrade check on my setup. I went from 6.12.3 to 6.12.4 and was immediately hit with BTRFS errors on the cache drive and docker failures. I rolled back to 6.12.3 thinking it was a update bug, but the errors are still there. It looks like from the forum I am not the only one seeing this pop up recently. I checked my grafana logs and everything was humming right along up until the update. Below is the 6.12.4 diag and the diag after rolling back to 6.12.3. I will be shutting down and running a memtest as soon as I post. Thanks for the assistance. tower-diagnostics-20230903-0808-6.12.4.zip tower-diagnostics-20230903-0827-6.12.3.zip

Nope, just tried it again.

It's back now.

Appfeed failed here too, but dockers updated and I can ping dns and websites from the terminal. I am guessing the feed is down.

Hey look through my post I made here just a few above yours. It might help answer some of your questions. It sounds like you may not have the Unraid-API docker talking to Grafana. Ha that would be femtobytes. It is an insanely small memory unit. https://scratch.mit.edu/discuss/m/topic/168582/ Again it sounds like something isn't configured correctly to read the array statistics.

Well butter my butt and call me a biscuit..... Page 34 release notes for 1.6 and there is the JSON datasource. Yep I missed that when I was just following the instructions on the first post in this thread. Just me being a bad user and not reading all the documentation. As for 1.7, I just got 1.6 running and am still tweaking it for my system lol I am sure the other users that have had it running for a while are looking for a new hit of the good stuff. Thanks again for the work, and to everyone else that contributes. One day I hope to be a real contributor to projects like this.

Hey Everyone! New UUD user here and I have had a good bit of fun settings things up! Thank you so much to all the contributors in this thread and others. @falconexe You are an amazing dev and looking at your announcement/documentation posts has been great! I would like to add my two cents here for anyone else coming to this thread looking to set up their dashboards. Quick specs: My TICK stack is hosted on a Ubuntu VM on a Mini PC separate from my Unraid Server. InfluxDB 1.8 Grafana 8.5.2 Chronograf 1.9.1 ( not that it matters for this) Unraid 6.10.2 1: Docker and VM icons - Part 1: Maybe I missed the documentation (if it isn't in the documentation could it be added?), but it took me forever looking through the forums to figure out this required a separate JSon API database to be configured in Grafana. This is in the same place you add the InfluxDB to Grafana. It was down at the bottom for me under (Others) 2: Docker and VM icons - Part 2: For me, the icons were broken after I got the JSON API datasource configured. I could not right click on the broken images like a lot of other posters. What worked for me was adding the port number to the ip address of the panel settings. I am guessing I don't use HTTPS or SSL or TLS or whatever for my server so it worked. 3: Constantly Resetting Dashboard Variables - This one really really drove me nuts! I would set all the variables, save the dashboard, then I would exit out and after a reload all the variables would be back to defaults and the entire dashboard would be broken. Turns out....if you slow down and read, there is a nice little checkbox on the save dialog box asking if you want to "Save the current variable values as dashboard defaults." That one was crazy how simple it was and dumb I felt. Hope this helps someone. 4. VM Details - I think this is a "it's me not you" issue. Or at least maybe its a Unraid-API concern. For the VM details I get the "Table fields have different lengths" error. I tracked it down to this query $.['vm']['details'][*].hddAllocation.all.[?(@.interface== 'VirtIO')].path . Any time I put the hddAllocation queries in the panel it throws the error. HOWEVER, if I put the queries in their own panels it only pulls the info for my one Debian VM. My windows VM had a entire disk passed through for the OS. It doesn't use a VirtIO disk and I think that throws the query off. ALSO, if no VM's are started then the allocation query throws an error. I found this article about null values in JSON queries and it might be the problem. 5. I saw some rumblings about the Dynamic image panel being unsigned and therefore depreciated in UUD 1.7. I am running Grafana 8.5.2 and it does not show unsigned for me. 🤷‍♂️ This took longer than I thought to setup and write up so some of the points escaped from my brain, but in summary: This project is awesome and thank you so much for putting it together!

Came here to check on this. So thankful for devs like you that have the skills to help us normal people have awesome things!! Can't wait to give this new update a shot. Seems like it has some really good changes.

<ip>:8086 is the API port. I don't think GUS includes Chronograf, so there isn't a webGUI (normally on <ip>:8888) for Influxdb. You would need to use the cli to interact with influxdb for adding other databases and users. Once you have that set up you should be able to point homeassistant to influx and then add that database to Grafana and use that new data to build dashboards.

I think you were on to something about the name being "shared". I changed the share name and it maps with the IP address just fine.