midwesterner

I am having an issue with the initialization of the app that I just can't get past. Every time I start the container, it stops immediately, and in the logs I see: Enter the response uri from your browser: An empty or invalid response uri was entered The OneDrive API could not be initialised I never get a chance to enter the response after visiting the login page. Even when I start the container via command line it starts up, shows some logs, and goes right past the point where I am to enter information from the response. I am not able to get it to pause so that I can login to my onedrive account and then come back to enter the response URI. It immediately goes to the message above. Any ideas on how to get the response entered? (am using the web based terminal for unraid here - should I be going in via SSH?)

This appears to be strictly related to getting to the Adguard DNS services running in docker. If I change the DNS address for the network to 8.8.8.8, I am able to resolve lookups from the terminal. So it appears to be something related to why unraid is not able to call the adguard DNS that is running in docker.

I have been running unraid with dockerized Adguard as my primary DNS server for my network for over a year. For the last couple days, unraid is not able to reach this DNS service and is not able to resolve anything external. I have Adguard getting its own IP on the unraid server so it is unique and not bridged. All my other devices on my network are able to use the Adguard DNS service without issue. Its only unraid and other containers running on it that are not able to get to the DNS service. Containers are not able to update. The community apps times out and does not load any apps. The plugins page also fails to load the version status of the plugins. My unraid IP is 192.168.0.10 and my dns IP that is assigned to Adguard is 192.168.0.49 In the unraid terminal, I am not able to do an nslookup on any external addresses. On unraid 6.12.2 and have been for a while. My router advertises the Adguard IP as the DNS for my network. I have my unraid server configured with a static ip and manually entered DNS addresses in the network config. I have recycled everything, modem, router, unraid server, docker containers, and still am not able to resolve DNS from the unraid machine. Networking is unfortunately not my strong suit. I have not been able to identify a change that was made to cause this. Any help would be appreciated. Thank you. homelab-diagnostics-20231014-0958.zip

Hello all. Recently upgraded to 6.12.2 on a 12th gen Dell R720. Everything was running fine after the upgrade. I decided to try out the CPU isolation feature. I have a total of 40 CPUS (20 main cores and 20 hyper threads). I left 4 CPUs unchecked, and selected the remaining 36 CPUs for isolation. My understanding is that the 36 selected CPUs are then only allocated to Docker containers or VMs. Based on the help text that shows up under the CPU Isolation area So that leaves 4 CPU for unraid and the rest for docker and vms. I then try to startup my plex docker container, for which I have allocated 8 CPUs that are within the 36 available to the containers via the isolation. I then get this error starting the plex container., It appears docker is only seeing the 4 CPUs that are not isolated rather than seeing the 36 CPUs available that it can use for the container. Is my understanding of the CPU pinning correct here, and if so, is this a potential bug?

Disk 4 file system check corrected errors. I also bumped up the memory for the plex container to 16gb. I will mark as solved if that seems like the most likely cause here and keep an eye out for more in the next few days.

Yes - will do that for disk 4. If the OOM was from Plex, which is running in docker, is that a safe error to ignore? Should I allocate more than the 2 gb of memory it currently has?

Hello all. I have a 12th gen Dell R720 with 192 gb of ram. After a reboot only about 48 hours ago, the Fix Common Problems plugin has indicated there is an out of memory error. Attached are the diagnostics. Any help would be appreciated. Thanks! homelab-diagnostics-20230115-1629.zip

Hello! Bit of a longer story here, and will certainly upload diagnostics if needed. Been running Unraid on a 12th gen Dell R720 with 192 gig of ram on Unraid 6.11.5. After about 10 days, I noticed an Out of Memory error captured in the Fix Common Problems plugin. Memory on the main page showed only 5% in use. After looking at meminfo, saw the free memory was only a gig or so, but the available memory was still high, around 188 gig. Rebooted last night, and saw that memory had cleared up, and free memory was now fully available. Ran top as of this posting (attached screen shot) and saw that there was a significant amount of memory under 'buff/cache' - about 77 gig after about 24 hours since reboot. What is the easiest way to identify why that memory space is being filled up? (I have very little running on this server at this point. Docker is not running, and no VMs running)