BillClinton

Hi Guys, Thanks for keeping an eye on this. I have had the server webgui lock up and muy deluge becomes unresponsive. I changed a couple of settings on deluge as the cache wasn't big enough. but the lock up still happened. Here is the latest Diagnostics and the syslog as well syslog-192.168.88.242.log tower-diagnostics-20240118-1750.zip

Thanks JorgeB I’ll enable that when I’m back from holiday in a couple of weeks. As a an FYI, the server webgui is inaccessible again. I update the post when I have the syslog info.

Hi Guys, I have had this issue happen a few times over the last couple of months. After a while the WebGUI becomes unresponsive and I am unable to log in and it times out. I can PING the server fine. All dockers are working in this last lock up. All accessable via their WebGUIs. My Ubuntu VM is still working as I have Twingate working in the VM and still accessible. I have trouble starting my Windows 10 VM via WOL (it is running on a Passed Through NVME) Can someone with better knowledge take a look over my diagnostics please. If you need anymore info, please let me know. tower-diagnostics-20231220-2242.zip

It’s shown in the quote “chmod -x /path/to/script/“ (remove quotes). The -x means executable. Run this command in a console window. Sent from my iPhone using Tapatalk

Only other thing I can think of is the certificate in Jacketts app data is old or balked. See if you can flush the old one.

It might be Telstra blocking that website. I know Australia has cracked down on torrent sites. Have you tried connecting to hd-torrents via your browser? Only solution is either to find another torrent site, or switch internet providers, or set up a vpn.

A friend of mine is a Plex nut. He’s not running Unraid but works with Linux. He’s done a heap of card testing and wrote up his results in a really nice website. Check it out https://www.elpamsoft.com/?p=Plex-Hardware-Transcoding

I did this when I was trying to figure out a server lockup. Turned out to be Radarr. I fixed it by limiting the containers memory. Edit the container and add —memory=xG To “extra parameters“ (Where x equals a value you are comfortable with). Hope this helps.

It looks like GitHub is down. You’ll have to wait for a while. Keep an eye on the Community Applications thread for an update.

I use 2 dockers for historical info. Netdata for fine details. Munin for long term stats history.

I had system hangs with this as well. It was from mono running away with my ram. In the end I limited the ram to this docker to just 1GB.

Try the NUT plugin instead. The built in application works best with APC branded UPS’s. you’ll find the NUT plugin via Community Applications. (Don’t forget to turn off the APC application before starting NUT so there is no interference).

Sounds nice. I hope it goes well. And welcome to UNRAID.

I have 16GB ram in my system. I do have to limit a couple of my dockers from hogging too much ram. And I’m not gaming on mine. Most people with VMs have at least 32GB. Might be a good idea if you can get some more. Make sure your sas card can be flashed to IT mode so it can pass the HDDs directly to unraid. Makes life easier in the long run.

Sounds very doable. You could leave 4cores/8 threads to unraid. I used to run my whole system with 4-7 streams from Plex on a i5-4460 (just 4 cores on that one, no VMs). Or you could leave 2 cores/4 threads to unraid and use the rest on you VM. Just make sure you definitely leave core 0 and h/t pair to unraid. Also check out a really good discussion in the thread https://forums.unraid.net/topic/55150-anybody-planning-a-ryzen-build/ Has a lot of info on other peoples systems. Also check out the spaceinvaderone videos on YouTube. He shows how to get your system up and running.

A bit of a shot in the dark; Have you tried /config -> /mnt/cache/apps/radarr Instead of /config -> /mnt/user/apps/radarr

This happens to me sometimes when I stop and restart the container too quickly. Eg stopping it just after starting the container, interrupting the torrent ‘resume’ process. There is a ‘state’ folder in the appdata which you can use to get it going. You’ll just have to re-add the torrents manually. You might have to add them in a paused state and make sure they are pointing to the right folder where your completed and not completed are kept. Then you’ll have to get them all to rescan for files. Could take a while.

You need to specify a build number within the edit docker page. In the repository field, add build number after linuxserver/deluge:XXX put in a number from the docker webpage -> tags. Click link in docker containers webgui Eg: “By:Linuxserver/deluge:latest”

VPN (within router) OPEN-vpn (docker) Zerotier (docker) And some others I can’t think of right now.

My two cents worth; Double check the serial numbers of your disks to make sure you don’t wipe the disks with your data before copying it off. (Double check and triple check). Might be less dangerous to transfer via the usb option to minimize risk. Other than that your plan seems sound.

Assuming you have all the original files still (including but not limited to all files have exactly the original file name) you put files back into completed directory, add .torrent file back to deluge IN A PAUSED STATE. Ensure that torrent is pointing to correct directory in details window. Tell deluge to recheck torrent. Make sure it sees most if not all files are complete 100% If all good start torrent. I hope this is clear

Are you running trim on your SSDs? I noticed you said all drive are connected to your LSI controller. There are a lot of posts and comments saying LSI controllers don’t support TRIM. Might be something to check. Try moving the SSDs to your mobo and schedule the TRIM in your webui.

This is not a solution to the problem itself, you could check out Zerotier. Admittedly you’ll have to get your server up and running properly first. https://lime-technology.com/forums/topic/72030-support-spikhalskiy-zerotier/ Might be something to check out.

You’ve got it slightly muddled up. You shouldn’t move data between disks and shares INSIDE your array. This increases the risk of data loss and data double up. ( moving data between shares is ok. Moving data between disks in the array is ok with some precautions). What you are doing, transferring data to the scratch disk and then to the array, is what the cache disk was set up originally for. This setting is included in the share settings. (Use cache disk: yes or Use cache disk: prefer). Then the “mover” takes care of shifting the data from cache to array. This setting might not be suitable to your needs depending how big your cache is and how much data you transfer. Also check the help button in your wedgui for more specific information. Hope this helps

Radarr has always given me trouble with runaway ram usage. There are a couple of steps you can take. I limit the amount of ram my docker apps use with the extra parameters section when you edit the docker. Something like “--memory=1G” (without quotes and depending on how much you want to give it). How much memory does your system have?