Magma

Same issue. I left the version blank and tried 11 but it would not download anything. This was using the Foundry Username + Password method. I had to specify the exact version for the installation to happen.

Yeah I noticed the same thing for a couple of my dockers as well.

So I noticed since sometime yesterday nzbhydra2 hasn't been loading. Looking at the logs I see the following error. [2m2021-02-18 15:22:26.118[0;39m [33m WARN[0;39m [2m---[0;39m [2m[ main][0;39m [36m.s.c.a.CommonAnnotationBeanPostProcessor[0;39m [2m:[0;39m[35m [0;39m[34m[0;39mDestroy method on bean with name 'nzbHydra' threw an exception: org.springframework.beans.factory.BeanCreationNotAllowedException: Error creating bean with name 'downloaderWebSocket': Singleton bean creation not allowed while singletons of this factory are in destruction (Do not request a bean from a BeanFactory in a destroy method implementation!) Does anyone have any ideas?

So I just noticed since I have updated to v3 that Radarr is not functioning correctly remotely. When I click "Add Movie" nothing happens. When I attempt to make changes to the settings I cannot save them. It always says there are unsaved changes despite hitting save. This all works correctly when accessing radarr locally. I have not made any changes to my reverse proxy or organizr settings. Any ideas? Thanks.

I have been trying to get Plex SSO working with Ombi V3 and Organizr V2. I have configured my reverse proxy according to https://github.com/causefx/Organizr/wiki/Plex-SSO. When I go to https://domain.com/plex I get a 401 error. If I go to https://domain.com/plex/web/index.html I am able to successfully reach plex. Any ideas as to what may be going on here? If it helps I've been following these guides: https://technicalramblings.com/blog/how-to-setup-organizr-with-letsencrypt-on-unraid/ https://technicalramblings.com/blog/installing-ombi-v3-beta-on-unraid-setting-up-sso-with-plex-and-ombi/ Thanks

I am at a complete loss so here's an update. I disabled all of my dockers and enabled them one at a time. Crashes were still happening though not as often. The event that most closely coincided with the crashes was plexs overnight maintenance although it wasn't uncommon for there to be no crash. I have also had it crash during the middle of the day with no real active usage. My longest uptime was 2.5 days. I have replaced the power supply, and ram. It has passed overnight memtest and prime95 tests. I have tried only using 1 stick of ram at a time and swapping them out. My only guess is that I need to replace the motherboard which I would prefer to avoid because at that point I should probably just replace the ram and cpu too. I have attached the most recent syslog and diagnostics from the last crash. FCPsyslog_tail.txt tower-diagnostics-20180528-1112.zip

Ok I will give that a shot. How long should I run it in safe mode? What exactly will this determine though? The server would essentially be idling with all of the drives spun down.

Another update. I have removed the dying hard drive and have replaced the ram which has passed overnight memtests. The crashing continues. It appears to be tied to high cpu usage. It happened when sabnzbd was unpacking at 30 gb download and it happens nightly when PLEX does it's scheduled maintenance. I rebooted today and started troubleshooting mode. I then started the scheduled maintenance and after about 30 mins it all locked up. Temperatures were only at 38 C. I have attached the latest diagnostics and syslog tail from this crash. I have a new 600w PSU with a 50a single +12v rail on the way. Any other suggestions on what could possibly be the issue or what I could try in the meantime? FCPsyslog_tail.txt tower-diagnostics-20180509-1148.zip

Unfortunately I'm still at a loss. Memtest overnight provided 0 errors. It lasted all day but crashed somewhere between 2:23 and 2:53 in the morning. I have attached the syslog and diagnostics again. Not exactly sure what else to be looking for honestly. One of my drives displayed read errors during a parity check. Nothing is stored on that drive presently however and is typically spun down. Could that be causing the crashes? tower-diagnostics-20180507-0223.zip FCPsyslog_tail.txt

Got home. Memtest had completed 2 passes with 0 errors. Reset bios settings to default and managed to boot this time. Going to be running a memtest overnight later.

I have only recently started using Unraid as of 2 weeks ago. Currently version 6.5.1. The entire time I have had random crashing. Sometimes multiple times a day. The longest uptime was just over 3 days. I'm only running Dockers for Plex, Sonarr, Radarr, sabnzbd, and nzbHydra2. I'm running it on an i7 970 with a EVGA X58 FTW3 motherboard with the latest bios. The temperatures were somewhat high so yesterday I replaced the stock heat sink with something better. This greatly improved the CPU temps but the crashing appeared to increase in frequency. Possibly just a coincidence. Today I went home during lunch and saw that it had crashed again. There is never any error message on the screen. This time however when I went to reboot it it hands on loading bzroot. I left it running memtest to see if detects any errors. I have installed the Fix Common Problems plugin and have attached the latest logs generated from troubleshooting mode. If anyone can provide any insight it would be greatly appreciated. I'm at a total loss currently. FCPsyslog_tail.txt tower-diagnostics-20180504-1120.zip