MACGoof

Have you tried to force update Radarr and Deluge? Might help as, from what I understand, that rebuilds them

**Ignore the below, the Radarr issue was a misconfiguration. Now I just need to work through why Radarr and Overseerr are not on speaking terms.** Hi all, hope everyone is doing well. If you would, please help make Radarr behave. Radarr has suddenly stopped talking to my indexer. Sonarr is working perfectly using the same indexer. I have uninstalled and reinstalled Radarr/renewed my indexer API/removed Indexer from Radarr settings but now cannot re-add due to error - (Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. Connection timed out (server ip address:8118). It should be noted that I use Wireguard via binhex-delugevpn and route all of my 'arr containers through that. They are all happy except for Radarr which gets the correct public IP and I can ping all but two default DNS servers from console. Other users have seen this error message and they were able to resolve by changing the NAME_SERVERS variable in the binhex-delugevpn container configs. I tried their recommendations, removing the default entries and to use only google (8.8.8.8,8.8.4.4) and then only cloudfare (1.1.1.1,1.0.0.1). I have tried keeping all of the default dns entries and only removing the two that do not respond to ping. In any case, any change to DNS breaks deluge which in turn breaks the other containers that run through it. Changing DNS also ghosts the NZBGET container forcing me to stop all containers and remove/re-install NZBGET. If i then revert back to the default dns entries in deluge and restart everything. All are happy except Radarr and I am back to the original issue of not being able to add my indexer back into Radarr. And I'm out of ideas short of trying a different container which seems like it could be tricky. Apologies for the word salad, hopefully that all makes sense. Any advice or tips would be greatly appreciated. radarr-logs.txt

Thanks for posting this. I followed your lead and set this up as well. Script works and the restarts at least allow some of my backlog to process a little at a time. Might tweak the frequency later but good enough for now. *edit: changed to every 30 minutes and is working well for me

This is the way I'm leaning as well. I did boot into safe mode last week and it was stable for roughly a day. As soon as I rebooted into normal (no GUI), it started crashing again. I'm going ahead with my plan to return the MB and convert to Intel. Going with a side-grade/maybe slight upgrade i5-12400. This started as a way to use spare parts and has turned into a whole thing Thanks again for your time and help.

Crashed again about 10 minutes ago. Here is the screen shot of kernel panic, logs and diags. Can anyone see anything relevant or do I have a hardware issue? Community Applications was the only plugin and Plex the only Docker running. What sort of things do you look for in the logs? Just errors I assume? I scan the previous logs and diags but never really see anything that stands out. rocinante-diagnostics-20240110-0547.zip syslog

Thanks for confirming. I saw this warning in Docker logs. Is this anything to worry about? time="2024-01-10T05:20:43-08:00" level=warning msg="containerd config version `1` has been deprecated and will be removed in containerd v2.0, please switch to version `2`, see https://github.com/containerd/containerd/blob/main/docs/PLUGINS.md#version-header"

I ran memtest overnight (10 hours) and it passed again with the manual settings I referred to above. (Memory 3200MT/s and flck 1600MT/s) Booted up and started the array. Then grabbed diagnostics and syslogs attached. Gonna let it run with zero pluggins and only the Plex docker running. rocinante-diagnostics-20240110-0547.zip rocinante-syslog-20240110-1353.zip

Thank you for replying. This was completed prior to posting.

Thank you so much for your input! Was starting to think I broke a forum rule or something since no one has replied. Yes, used the built-in memtest. Two cycles and it passed. Should I let it run for longer? Regarding the BIOS settings. I just now manually configured memory speed to be 3200MT/s and flck speed to be 1600MT/s per the recommendations I could find. Other than that, see attached for what I could find on voltages. I'm guessing you are referring to DRAM voltage which is set to Auto. Should I manually change that to something else? I didn't post my system specs, my fault. XMP is intel. AMD calls that DOCP and that setting is not enabled. It is set to Auto as well. Options are Auto/Manual/DOCP. Was honestly considering returning my MB and converting to an Intel system. I had this AMD processor, graphics card and power supply laying around so I bought the MB, RAM and storage for this build. AMD Ryzen 5 3600 NVIDIA RTX 2060 Asus ROG Strix B550-F x2 Crucial Pro RAM 64GB Kit DDR4 3200MT/s x2 WD Black SN850X 1TB cache x4 Seagate IronWolf Pro NAS 4TB Seasonic PX-850

And here is a screen grab from today’s kernel panic. I ran memtest this weekend and it passed. Tested with some other ram I have and it crashed then as well. I wiped my flash and recreated it just in case something went wrong on initial creation. It ran half the day today but crashed again just after dinner. What are normal temps for the drives? Most are ~35 C but my parity drive can get ~45 C. Just trying to think of anything here. Hopefully someone with more experience will chime in on if anything stands out in this grab or logs.

Just realized I attached the incorrect screenshot. Apologies. Below is the correct one.

Had another crash. New screenshot and logs. It ran fine in safe mode for ~9hrs today. After it completed parity, I rebooted normally and within about an hour, it crashed. So I guess I will remove all plugins and reboot. Then re-add one at a time until it crashes. Unless anyone can see something here that points to another culprit. syslog

Happy Saturday fellow Unraiders. I have been reluctant to create a new post for this and have tried find a resolution via others' pain. But, I'm out of ideas and fear that my system has a hardware problem. Any insight would be welcome. My server has never really been stable. Constant crashes/freezes which force unclean reboots. The most recent crash last night was while booted into safemode (non GUI). The only plugin I had active was Community Apps. My Plex docker was running and the system was performing parity check. Nothing else was running. I have captured syslogs, diagnostics and a screenshot of the kernel panic but nothing obvious sticks out to my eyes. Any thoughts or ideas of what to try next? Thanks in advance. Things attempted to resolve so far: BIOS update BIOS settings for AMD systems (disabled C-States globaly) Docker configured for ipvlan Boot into safe mode (Community Apps being the lone exception) rocinante-diagnostics-20240106-1030.zip syslog

@j5i7- Would you mind sharing your script please? I am having similar issues and am considering purchasing a pcie nic for testing. In the meantime, your script could be a big help. I am hesitant to create a new post for my issue as it seems redundant.