• Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Agent531C's Achievements


Newbie (1/14)



  1. I was rsyncing some files between drives, and saw in the file manager that some files had a Red font color, as opposed to the usual white font color other files in the same folder had. What exactly does the Red font mean?
  2. Ended up doing that, renaming, and rebooting, but still no luck. I ended up just pulling the compose/.env files out of the config, and then deleting the folders and recreating them through the web gui with no spaces. Seems to have no issues so far
  3. Ended up shutting down the array, renaming them, and then restarting the array, but it cause a weird docker crash where the manager wouldn't start. So I uninstalled the compose plugin, rebooted, and everything came back up fine. Added the Compose plugin again (with the renamed folders), and all of the ones in the originally attached image showed up fine, but none of the others are in the web ui, even though their containers are started. Should I try/have tried removing the containers completely, orphan images and all?
  4. I have an odd problem, and perhaps its related to ShadowBerts problem, but I just noticed that some of my compose stacks are missing from the web UI, even though they are in the compose.manager/project folder and are still being autostarted when the array starts. I am on 6.11-rc3, and the 'invisible stacks' all start fine, but have no representation in the UI for pull/up/down/editing. The Web UI: The Folder:
  5. Do the 'share' specific move buttons follow the mover tuner settings when they are run manually and the 'Move Now button follows plug-in filters' is enabled? I have a downloads/incomplete folder filtered out with a text file, so files are never moved out while they are downloading and processing, but using the 'share' move button seems to try and move the incomplete files over regardless. I assumed it would follow the plugin filters, since the setting was turned on, but does only the 'Move Now' button on the 'Main' tab follow the rules?
  6. Ive had a weird issue since updating from 6.9.2 where I have been unable to shut down my array, meaning every time I need to stop it, I have to hard reboot it. Docker looks like it shuts down properly, and as far as Im aware, I have no shell sessions active. (unless Ive been hacked and I havent recognized it). This applies to reboots as well as stopping the array I installed the 'Dynamixs Stop Shell' script hoping that may solve the issue, but unfortunately it did not, and Im still having issues shutting down the array.
  7. Just popping in to ask about the Docker Volume vs File System problem Ive seen mentioned in the past. I switched to File System image recently, and noticed that my /storage mount is now missing, just like mentioned in other comments. Curious if a workaround has been found to work, or if I need to go back to a docker image for it to work properly again.
  8. It looks like some recent changes in the radarr api makes it so the :latest varken tag doesn't work. Ive switched over fully to develop, so it may be worth it to migrate now instead of later. Im not sure why they haven't pushed a single update to the main repo in 2 years, but the develop one has been moving strong with a lot of new features (like Overseerr support)
  9. Glad it worked out! I do wish it brought over some of the info it doesn't, but I only have about 9 months of tautulli data, so Im not super concerned about it. Can't wait for 1.7, and to see what it has in store.
  10. I honestly didn't know that about compose-up. As for the first part, the actual webui doesn't pick up the changes for any label changes. If I set a label for an icon, and change it, it remains the first one even through reboots, deleting the cached image, and deleting/rebuilding the stack alltogether. Same goes for the 'webui' button on the popup. If I set a 'webui' label, and then go change it later, it remains whatever that first label was set on. I am on 6.10.2, but this very well could be a limetech issue with the way labels work at an OS level as opposed to the compose plugin.
  11. I didn't notice any data duplication, corruption, or schema issues since my total plays broken down by device looked similar to what I had in tautulli. Because of the discrepancies I had noticed, I actually ended up running it, and then deleting all the data from my influx to run it again 'fresh' in case of data duplication. I only had a couple days worth, since I set the retention policy after seeing your post on it. My numbers looked similar on the run + backfill as they did when I cleared out all of my data and backfilled it, so I don't think it duplicates things, but I don't want to say for sure. I was definitely in the same boat of wanting all my data viewable in grafana, which is why I went looking. Worst comes to, you can always back up your DB and run it to see what happens. As for building everything into a single container, Im not too sure about that. It seems like the GUS container used a lot of custom scripts to build/grab config files out that I don't have experience with. Id love to learn, and know some apps (like AzuraCast) have 'monolith' containers that have 5 services running in one. Its definitely possible, but I'd need to look deeper at it.
  12. Ive got some really weird behavior surrounding changing labels after setting them initially. If I set an icon/webui port option, and then change it later, the old one sticks for some reason. Restarting the server doesn't clear them out, deleting the stack and rebuilding it under a different name doesn't clear them out either. Also, a great feature would be a 'restart' button. With how the unraid gui loads, I spent a lot of time waiting for things to load while editing docker compose files. Id change one thing, save, load. Compose down, load. Compose up, load. Itd be nice to have a restart button which does down followed by up for when you're editing compose files and testing things out.
  13. If you haven't figured it out, I was able to backfill all of my Tautulli data into influxdb using their backfill script on the 'develop' tag. Unfortunately, it does have some side effects with what seems like data structure changes, but it fills out enough that its usable. I've mainly noticed some fields act up, like 'Time', 'Plex Version', and 'Stream Status'. Sometimes the 'Location' would show as 'None - None' as well, but it usually got it correctly. To get started, change your varken container to the 'develop' tag. From there, open the console for it and run these commands: This moves the script to a location it can recognize the varken python import from mv /app/data/utilities/ /app From there, run the script with a few arguments: python3 /app/ -d '/config' -D 365 -d points to your appdata/varken.ini -D is the number of days to run it for That should backfill everything into your influxdb. I tried to run this on the 'latest' tag, but unfortunately the script is broken in it, and doesn't fill any data, so you have to use the develop tag.
  14. Hey, I saw talk about turning the project into a single container to rule them all. Obviously testdasi has done it, so it is possible. I felt like docker-compose was more appropriate for the use case, so I wrote up a compose file and guide on how to set it up on Unraid using the Docker Compose Manager plugin: I can't wait till they add native support, but this works great in the meantime.
  15. I saw the discussion about installing proton via script, but it would be great to get it in the container natively. With the advent of the steam deck, it's really become a powerhouse. I assume this will transition to the Steam OS theyve been building for the deck, once it officially releases as 'Big Picture 2.0', or whatever they call it? --------- I am actually having some permission issues with the proton install script provided earlier, so Ill have to take a look at it. Not used to handling user's permissions/owners properly in linux. ------- After a bit more investigation, the permission thing seems to be a protonup problem: The Author of ProtonUp is MIA, so a new PyPi package was created in the meantime: protonup-ng The PR detailing the switch to Protonup-ng is here: You can fix your boot script running protonup by simply changing 'pip3 install protonup' to 'pip3 install protonup-ng'