urmyboyblue

Ah gotcha. Thanks again @Kilrah ! I'll try the extra mount and see how it goes.

Thanks @Kilrah . I was considering that , but according to this post, that folder name is random and I'm not sure it it might change, so mapping it might be a problem (at some point). Nextcloud communityWhat is the appdata_ocpom4nckwru directory?Its a quick fix to keep app related data (such as configuratin files or caching) in data/ since data/ has user ids as sub folders, adding an appdata folder would make a user appdata owner of that di

I've been seeing issues with my disks spinning up and after using the Files Activity tool it looks like Nextcloud (News app) is causing it. It seems like the NC apps create and use a "appdata_<some_id>" directory in the /data container, which (best I can tell) is used for temporary application data with a lot of reads and writes. Since the /data folder is also for all of the user data, I have it mapped to my array, which is the reason for the disks to keep spinning up. I did some digging and it looks like the NC AIO container has a "NEXTCLOUD_DATADIR" environment variable that can be set to address this. https://github.com/nextcloud/all-in-one#how-to-change-the-default-location-of-nextclouds-datadir I tried setting that with this container but it doesn't work. Anyone tried this or have any suggestions? I know I could use a different news reader, but it seems like this affects all of the NC apps. :)

@pants Have you tried setting the address argument?

I noticed this error in my log [drm] User-defined mode not supported: "1280x720" then did some searching and found this article Unix & Linux Stack ExchangeHow can I change the resolution for DRM?I need to change the standard resolution for my DRM mode. How can I achieve that? When I do cat on cat /sys/class/drm/card0/card0-HDMI-A-1/modes 1920x1080 1920x1080 1920x1080 1280x720 1280x720 128...https://www.kernel.org/doc/html/latest/fb/modedb.html After looking in my /sys/class/drm/ directory, it seems like my "connected" HDMI port is card0-HDMI-A-2 (based on the "status" file showing "connected"). I then changed my append statement to this and rebooted. The error is gone but still no luck with the resolution. video=HDMI-A-2:1280x720@60

I tried this on my setup to try and force the non-GUI resolution to 1280x720 but it doesn't work. Any idea? label Unraid OS menu default kernel /bzimage append initrd=/bzroot video=1280x720@60

Anyone confirm if there is any concern running this due to the recent CUPS CVE? I don't think that it would be since I don't see cups-browsed running in the container so I assume not but I've not seen any discussions or issues reported on the Github page. https://www.evilsocket.net/2024/09/26/Attacking-UNIX-systems-via-CUPS-Part-I/

I have a Realtek R8186 NIC and the Fix Common Problems app listed this as a warning for me. I assume it doesn't apply, correct?

https://github.com/go-gitea/gitea/issues/25915#issuecomment-1640933269 Followed this to get mine working.

Thanks @Indmenity83! I had this issue where the Plex container was logging to log.json and filling up /run which caused problems with all containers not starting (found that from here) I was deleting the log.json file manually but bow this --no-healthcheck option prevents it from happening. Would love to know if this is happening because of something else being wrong or if it's a bug that should be fixed.

Same!! Been pulling my hair out trying to figure this out too! Thanks @vstylez_!! Is this a bug or something gone awry? EDIT Found this which on another thread which was causing my issues. Added the "--no-healthcheck" option under my Plex container and the logs stopped.

I'm getting these as well periodically. Best I can tell is that they seem to happen when my backup share (over Tailscale) starts seeing some issues (possibly packet loss somewhere?) and "du" or "df" (can't remember) starts failing to that remote share. But once it happens there is no recovery - even when the remote Tailscale node recovers, which I can see from my laptop on my same home LAN. The main issue I start seeing is that my docker apps won't restart and throw an exception. The only way to recover Unraid is a reboot. Yeah, I know the Tailscale container states that it is intended to provide remote access to Unraid only (not any gateway functionality).

Great utility... thanks!! I have it all working (using SWAG/NGINX - /opt/log directory path is set to my SWAG /mnt/user/appdata/swag/log/nginx/ folder) and pulling into the access.log. I am seeing this error message though: nginx: [alert] could not open error log file: open() "/var/lib/nginx/logs/error.log" failed (13: Permission denied) Couldn't find much from a Google search. Any idea how to fix it? The error.log file is in the same directory as access.log so I assume it can read it.