fonzie

I've had my current rig for about 6 years and I'm looking to upgrade. -------------------------------------------------------------------------------------------------------------- My current setup: Mobo: ASRock EP2C602-4L/D16 http://www.newegg.com/Product/Product.aspx?Item=N82E16813157350&ignorebbr=1 CPU: 2x Xeon 2670 matching pair SR0KX https://www.ebay.com/itm/264797287830 Cooler: 2x Noctua NH-U9DXi4 https://www.amazon.com/gp/product/B00E1JGFA0/ref=ox_sc_act_title_2?ie=UTF8&psc=1&smid=A1H9NMCPZH97BO Memory: 96GB (12x 8GB) Micron DDR3 Ram http://www.ebay.com/itm/122249072561?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT PSU: EVGA SuperNOVA 1000 G2, 80+ GOLD 1000W https://www.amazon.com/gp/product/B00CGYCNG2/ref=ox_sc_act_title_1?ie=UTF8&psc=1&smid=ATVPDKIKX0DER SAS Card: LSI SAS 9201-16i https://docs.broadcom.com/doc/12352036 Case: Norco 4224 https://www.amazon.com/NORCO-Mount-Hot-Swappable-Server-RPC-4224/dp/B00BQY3916/ref=sr_1_1?s=pc&ie=UTF8&qid=1482874823&sr=1-1&keywords=norco+4224 # of Hard drives: 24 --------------------------------------------------------------------------------------------------- My needs: I want to be able to handle 4K HEVC transcoding on and Emby docker using Intel Quicksync. I don't want an external GPU. I want to run at least one Windows 10 VM at a time. I'm thinking based off my limited research that the i7-12700K might be good enough with its UHD770 graphics which are the same on the 13700K (so no need to pay more for same GPU power) Looking at maybe 32GB DDR4 RAM with the possibility of expanding it to 64GB in the future. I also just got a PCIe 4.0 NVMe m.2 drive so I'll need a new mobo with a slot for that (I'm sure most new ones already have m.2 slots) My budget is around $800, but if it can be done for less or if you think the CPU above is overkill let me know. I'm open to any suggestions or corrections.

Interesting. So how do I select which VPN server rtorrentVPN connects to if it's done automatically? Or do I just let it choose the best option?

I'll give that a try. I see the option in the docker settings for rutorrentVPN to change from openvpn to wireguard, but where in the private internet access website can i find the config files for wireguard? And where in the docker will I place them once I have them?

Haven't fixed it for myself yet. I'm using PIA and installed the qbittorrentVPN docker and the speeds are much faster using the same PIA VPN server so I have to assume that it's an issue with either rtorrent or the docker itself. I just wish I could fix this issue because I much prefer the feature rich rTorrentVPN docker over the qbittorrentVPN docker. I'll be checking in this thread regularly to see if any updates come by that let me come back to this docker.

This docker has been working perfectly for a long time, but just recently have the speeds been super slow to completely stopped. Some torrents will show there are no seeders (when I know there should be) and even those with seeders will not download. I'm using Private Internet Access as a VPN provider. I was using the Berlin VPN for years and it's been fine up until recently. Tried changing it to the Mexico one, due to lower latency, but it is the same issue, if not worse. Does anyone have a recommendation for a city to use with Private Internet Access and this docker? Or know of anything that could be causing my downloading issues?

I've been using the offical emby docker for years now without issue but lately I've found that my "Movies" share isn't storing metadata. No subtitles, or fanart, or even thumbnails are being stored alongside the movies in their corresponding folders. Yes, I have the settings correct. It's worked for years and I didn't change anything in emby. Could it be a permissions setting within unraid that's not allowing the docker to write to the share. I'm using Sonarr to download movies and place them in the correct folder, so I don't know why Sonarr would be able to write to that share when it seems that Emby does not? Any tips would be appreciated.

I don't have a UPS. So once it happens again, turn on syslog server and see if it catches anything? That would be terrible if it were hardware related. Could it be a problem with overheating? I might open the server up and do some cleaning to it.

Lately, my unRAID server (about once a week or maybe less often) gets stuck in a reboot cycle by itself. It randomly will restart the server and starts doing a partiy check (as if it wasn't a clean reboot) then after about 10 minutes it restarts again and the cycle continues. Even if I press the restart button on the unRAID GUI and it cleanly restarts it will still keep on the cycle. The only way to stop it is to physically press the power button, wait a few minutes, then press the power button again to start it back up. Obviously this isn't ideal, as I am usually not home when this cycle starts. I've attached the diagnostics What log or information can I post to get some assistance? It's currently stuck on the reboot cycle as I post this. media-diagnostics-20220813-1922.zip

What ended up working for me was I went into appdata>rtorrentvpn>rtorrent>session and deleted all the files in there. I was able to start rutorrent after that. Now I'm slowly adding my existing torrents back on there.

Where did you set this Extra Parameters? I can't find the setting

I was checking the container size for all of my dockers and found that the log for my xteve docker is 36.4GB! How do I delete these logs to reduce my container size and what settings do I change to prevent the log from getting this large again?

My rtorrentvpn has been down since yesterday and I cannot get it back up and running. It's been working fine for over a year and yesterday I added several torrents all at once. It started getting slow and then stopped responding. I've tried restarting the docker and even restarted the entire server but still it does not load. the log says: [info] rTorrent process listening on port 5000 2022-06-15 09:54:20,242 DEBG 'watchdog-script' stdout output: [info] Initialising ruTorrent plugins (checking rTorrent is running)... 2022-06-15 09:54:20,253 DEBG 'watchdog-script' stdout output: [info] rTorrent running [info] Initialising ruTorrent plugins (checking nginx is running)... 2022-06-15 09:54:20,264 DEBG 'watchdog-script' stdout output: [info] nginx running [info] Initialising ruTorrent plugins... 2022-06-15 09:54:31,849 DEBG 'watchdog-script' stdout output: [info] ruTorrent plugins initialised 2022-06-15 09:55:17,100 DEBG 'watchdog-script' stdout output: [info] rTorrent not running 2022-06-15 09:55:17,108 DEBG 'watchdog-script' stdout output: [info] Removing any rTorrent session lock files left over from the previous run... 2022-06-15 09:55:17,114 DEBG 'watchdog-script' stdout output: [info] Attempting to start rTorrent... 2022-06-15 09:55:17,115 DEBG 'watchdog-script' stdout output: Script started, output log file is '/home/nobody/typescript'. 2022-06-15 09:55:17,151 DEBG 'watchdog-script' stdout output: Script done. 2022-06-15 09:55:19,190 DEBG 'watchdog-script' stdout output: [info] rTorrent process started [info] Waiting for rTorrent process to start listening on port 5000... 2022-06-15 09:55:19,201 DEBG 'watchdog-script' stdout output: [info] rTorrent process listening on port 5000 2022-06-15 09:55:19,202 DEBG 'watchdog-script' stdout output: [info] Initialising ruTorrent plugins (checking rTorrent is running)... 2022-06-15 09:55:19,213 DEBG 'watchdog-script' stdout output: [info] rTorrent running [info] Initialising ruTorrent plugins (checking nginx is running)... 2022-06-15 09:55:19,226 DEBG 'watchdog-script' stdout output: [info] nginx running [info] Initialising ruTorrent plugins... 2022-06-15 09:55:39,515 DEBG 'watchdog-script' stdout output: [info] ruTorrent plugins initialised 2022-06-15 09:56:09,726 DEBG 'watchdog-script' stdout output: [info] rTorrent not running 2022-06-15 09:56:09,734 DEBG 'watchdog-script' stdout output: [info] Removing any rTorrent session lock files left over from the previous run... 2022-06-15 09:56:09,737 DEBG 'watchdog-script' stdout output: [info] Attempting to start rTorrent... 2022-06-15 09:56:09,738 DEBG 'watchdog-script' stdout output: Script started, output log file is '/home/nobody/typescript'. 2022-06-15 09:56:09,773 DEBG 'watchdog-script' stdout output: Script done. 2022-06-15 09:56:11,807 DEBG 'watchdog-script' stdout output: [info] rTorrent process started [info] Waiting for rTorrent process to start listening on port 5000... 2022-06-15 09:56:11,817 DEBG 'watchdog-script' stdout output: [info] rTorrent process listening on port 5000 2022-06-15 09:56:11,818 DEBG 'watchdog-script' stdout output: [info] Initialising ruTorrent plugins (checking rTorrent is running)... 2022-06-15 09:56:11,828 DEBG 'watchdog-script' stdout output: [info] rTorrent running 2022-06-15 09:56:11,828 DEBG 'watchdog-script' stdout output: [info] Initialising ruTorrent plugins (checking nginx is running)... 2022-06-15 09:56:11,839 DEBG 'watchdog-script' stdout output: [info] nginx running [info] Initialising ruTorrent plugins... 2022-06-15 09:56:20,175 DEBG 'watchdog-script' stdout output: [info] ruTorrent plugins initialised any suggestions or advice?

I've had experience with this happening in the past so I'm careful to make sure the directories are correct when adding new dockers. I haven't configured or added any new dockers recently so I'm confused as to why this would happen suddenly this morning. Is there a way to see what is being written to the docker.img in realtime? How do I check for the orphan images? I was planning on deleting the docker.img and rebuilding but I'm afraid that what caused it to happen the first time will just do it again

I haven't made any changes to my dockers and haven't gotten any new ones, but this morning I woke up to messages about every 10 minutes that my docker.img was filling up 1% each time. What's the best way to find out which docker is causing the issue?

Follow up curveball question: Can I copy all of the contents of disk21 (including the incomplete files from the cancelled disk4 process) to another disk (lets say disk 8) and then run the command: rsync -avX /mnt/disk4/ /mnt/disk8 and have it resume the sync to disk8 even though the original process was started moving the files to disk 21? I'm thinking (hoping) yes because it will just compare files from both drives and sync them, as the name implies...but I want to be sure.