widowshyper

Just tried that and still got the same error on one docker container tautulli

Hello, I've been getting this error recently. It's not the same containers each time and has happened when running in stop all then backup and stop, backup start each container modes.

I am also experiencing similar issues to you. Recently been getting lots of " CUDA_ERROR_NOT_INITIALIZED: initialization error" but it only happens with the GPU(1660 super) installed in my unraid server. If I use my RTX 3080 as a remote transcode node on my gaming PC works perfectly fine zero issues. So I'm leaning to something happening in unraid that is dropping the gpu from docker containers. something in tdarr that is dropping nvidia gpu's from view or the lastest nvidia driver v575.51.02 could have bugs in it that are causing issues. I also get the same issue using a regular tdarr ffmpeg stack not a custom plugin. only started happening the last week or so. Current Unraid Version: 7.1.2 Latest tdarr version. O6sW895sO-log.txt

ended up just having to swap my transcode directory to my cache ssd. unsure of why my ram disk was filling up and then not clearing itself out and was unable to diagnose why. Most likely a config issue on my end with how I setup the ram disk.

I get this, It's been locked at 98% since I removed the ram disk. This was my original ram disk config inside my plex container Name: Transcode Container Path: /transcode Host Path: /tmp/PlexRamDisk Default Value: /tmp/PlexRamDisk Access Mode: Read/Write Display: Always Required: Yes

I did have a Plex RAM Disk setup and I'm guessing that's what was causing my issues, since my rootfs has filled back up since I changed my transcode directory to my cache ssd. Not sure why it's suddenly filling up since I setup the ram disk probably 8-9 months ago.

docker run -d --name='plex' --net='host' --cpuset-cpus='2,4,6,8,10,12,13,14,15,3,5,7,9,11' --pids-limit 2048 -e TZ="Australia/Hobart" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Widow" -e HOST_CONTAINERNAME="plex" -e 'VERSION'='docker' -e 'PLEX_CLAIM'='' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-1bddcbfb-3677-ed45-31e2-3a15a7134ae2' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='000' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web/index.html' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/plex-logo.png' -v '/mnt/user/data/':'/PlexVault':'rw' -v '/mnt/cache/transcode/':'/transcode':'rw' -v '/mnt/remotes/WINSVR_TheVault/Seeding/':'/RemoteJBOD':'ro,slave' -v '/mnt/cache/appdata/plex/':'/config':'rw' --device='/dev/dri' --runtime=nvidia 'lscr.io/linuxserver/plex' a918a8cb2053f03ef728f99fd1961a5ad70aca33b3aa680ad137ca7f35804983 The command finished successfully!

I've gotten this error this morning with the Fix Problems plugin "Rootfs file is getting full (currently 98 % used)Possibly an application is storing excessive amount of data in /tmp." the only thing I know of that is in /tmp is a plex ram disk (which I don't remember how I setup, which isn't helping me diagnose the issue) but I would have set that probably 8-9 months ago and haven't had any issues since. Could anyone help with diagnose what could be causing this issue? widow-diagnostics-20250507-1243.zip

Not sure if this thread is still active but I've tried hunting around but the github page has very lack luster setup instructions for unraid and I'm not super well versed in docker. So far I'm not sure what IP address I need to put in. If it needs to have /admin or :443 or :80 for use HTTPS or HTTP or /api at the end. My password is just a string of numbers as well so no fancy characters. I use a pihole app and I can access my pi's just fine using HTTPS. I also tried swapping the ports to 80 and http I am currently getting this error. 2025-02-28T23:38:56+11:00 INF Starting nebula-sync v0.3.0 2025-02-28T23:38:56+11:00 INF Running full sync replicas=1 2025-02-28T23:38:56+11:00 INF Authenticating clients... 2025-02-28T23:38:56+11:00 FTL Sync failed error="authenticate: https://192.168.1.8:443/api/auth: Post \"https://192.168.1.8:443/api/auth\": tls: failed to verify certificate: x509: cannot validate certificate for 192.168.1.8 because it doesn't contain any IP SANs" If I try HTTP I get this error: 2025-02-28T23:42:55+11:00 INF Starting nebula-sync v0.3.0 2025-02-28T23:42:55+11:00 INF Running full sync replicas=1 2025-02-28T23:42:55+11:00 INF Authenticating clients... 2025-02-28T23:42:55+11:00 FTL Sync failed error="authenticate: http://192.168.1.8:80/api/auth: Post \"http://192.168.1.8:80/api/auth\": dial tcp 192.168.1.8:80: connect: connection refused" ** Press ANY KEY to close this window **

I did have to cancel the plex backup as I already left a backup running overnight which took an hour and a half to complete.

I noticed my weekly appdata backup was suddlenly HUGE 133gb per backup in size and it appears that the backup and restore appdata plugin is not ignoring the requested folders in Plex, its backing them up anways. Is this currently bugged? Debug ID: 65e268a4-e3b3-457f-9909-2c259253839a

I've enabled that now, thank you for the tip. So as far as those logs say there any no issues?

Good Evening all, I've been using unraid for about 5 months now, and it's been fantastic but recently in the two weeks I've had my unraid server lock up. Hard lock up, unable to SSH in, unable to telenet in, even plugging in a monitor and kbm I get a display signal but the GUI is just frozen. Requires a hard reboot to come back. Just happened a couple hours ago but it did come back instead of hard freezing and needing a reboot like a week ago. I've attached diagnostics I took right after I got back into my server. Any help would be appreciated. widow-diagnostics-20241006-2009.zip

Just a tip for anyone who is having issues accessing their dashboard but are able to access docker containers via zerotier. I ended up enabling SSL/TSL in the management option in settings set to "Yes" not strict, which now lets me access my dashboard via zerotier.