Unraidmule

Ah OK, if you find a solution can you please post it here

If you keep the tabs closed, does it fix your issue? For me, I was calling the API constantly for 3 instances (every 2-3s) while keeping the web UI open, which has a glitch to increase the RAM until server crashes.

Are you using any other sort of application which is probing the qBit API? Also my issue only occurred if I stayed on the web UI I was also instructed the same as you - lscr.io said it wasn't their problem too.

I am having the same issue which has not been resolved yet: RAM leak issue Did you find a solution?

Thanks for the reply, the drive is formatted to btrfs. I am also using extra flags on other docker containers to try to solve the issue, but it does not seem to have worked. I added the --no-healthcheck to all docker images which were showing in the advanced menu — GluetunVPN must have a check because when I added it to that container it wouldn't start up. For others, I added these flags: --log-driver none --no-healthcheck --mount type=tmpfs,destination=/tmp,tmpfs-mode=1777,tmpfs-size=256000000 Still, the problem is occurring. Is there a disadvantage of changing the docker image to folder structure?

I added the --no-healthcheck flag to the containers which showed (healthy) in the advanced menu and now the writes have gone up to 5 GB per hour Should I add this to all containers, regardless if they showed that state or not?

Thanks for the reply. I have not disabled health checks. Is it a flag I have to put on each docker container? I forgot to mention in the original post that the disk is also formatted btrfs if that helps diagnose the issue.

I am running Unraid v6.12.9 I only use the cache drive for docker.img and storing app data, so I can't figure out why it's writing data constantly 24/7. The actual total data used on the drive is static, and the drive is not actually filling up, just wearing the SSD endurance down. My guess is overwriting existing data with the same data? The docker containers should only be writing log files, no transcoding or anything intensive takes place on the cache drive. 6.91 TBW @ 3,752 Power on hours 7.55 TBW @ 3,893 Power on hours In 141 hours, 0.64 TB of data was written to the drive, which is roughly 4.5 GB per hour

Thanks for the reply, since it is happening with all qBit containers from different docker images — so I would have to post the same to the maintainers of each container?

I am running Unraid v6.12.9 I have an issue where if I leave the web UI of a qBittorrent instance on for too long in a browser tab, it uses all available RAM and crashes the whole server. I can ping the server but not access the Unraid web UI any more or the shares. I set the --memory flag on the container(s) to limit RAM usage and prevent crashing, but then the instance hits the limit, crashes, and resets itself, which is a problem. This creates a lot of ghost peers and losing upload stats, by not announcing to trackers before the crash. The middle client has 804 torrents with only a maximum of 8 being allowed active to seed, which is causing the biggest issue as it increases in RAM the fastest out of the three. When the problem begins by accessing the web UI: End result just before a server crash (bottom container crashed itself and uptime reset): Total RAM:

Thanks for the reply. Weird since running the rclone script GBs of data is slowly getting written to the cache with nothing else new running to cause the issue. rclone is writing data directly to the array skipping cache. So I am confused. I will try looking at that folder again. When I checked I couldn’t access any logs will it be in the running folder?

I am running rclone in the background and I think this script is writing GBs of log files on the SSD cache, does anyone how to to confirm this? I can't even locate where this plugin stores the logs.

hi, I have vpn disabled but when i load the qbit gui and login i get qBittorrent client is not reachable so not able to go into settings. Please help

HI, It only goes orange when you do the DLNA search to find //Synology in the list but you don't even need to click it in the list after search it goes orange. Kind Regards,

Hi, The button is grey this is the ping test results Kind Regards,

HI, Here is my log files I rebooted Unraid and manually started the Array - and waited for UD to mount but it didn't do anything Log is suggesting synology nas is offline ? but it has an uptime of 70 days. thanks tower-diagnostics-20240114-0914-UD.zip

Like I said previously, thanks for your work. we really appreciate it. And I didn't even know that button existed thanks for teaching me something new! I will update now and test it out! Have a great day!

Thanks for the reply. I tried searching the forum for the support page but couldn’t find it. Then went on to the GitHub page which sent me here. Maybe one doesn’t exist yet? EDIT: I see it now, was on mobile before so was more difficult to find. You can update the GitHub page to send to the official thread

Hey ich777, The lounge support link sent me here. There is an update available to v4.4.1 released Jun 18, 2023. Do you plan on updating the container? Thanks for your work!

The array is not set to auto start on boot - due to motherboard needs dummy HDMI to auto start server - which I still need to get. but UD should still mount before array is started as its a different location? and there is dockers dependant on UD location so this needs to start before array goes online.

I rebooted the system and ov the mount is not connected due to issue but this is my diagnostics file - hope it helps if you need anything else let me know please tower-diagnostics-20231230-1055.zip

Hi guys, I need some help - I'm using UD plugin and have mounted a folder from my Synology NAS - everything is working fine - but when I reboot Unraid - I have to mount it again and add the user/pass again - is there a way to fix this issue please Automount is on but on reboot the mount button is greyed out

If i used PrivateVPN every time it connects to a server i will be given a dynamic port - does this container relay the port in qbit? or do i have to do it manually?