nraygun

Gotcha. Thanks!

I see where @Torvald Utne is coming from since I never got a clear answer in my original question either. In Unraid, does "shutdown" perform a safe, graceful shutdown of Unraid? 5/21/2025 asked by me, "Does "shutdown" perform a graceful shutdown? Stop containers, stop parity check if running, and such." 1/24/2026 asked by @Torvald Utne , "poweroff is a standard linux command. Does using it SAFELY shut down the array, stop dockers and VMs and such before powering off?"

I restarted the container and now MaxMind works. Must have been a down server or something. :-)

Just updated to Swag 5.2.2-ls433 and I see these errors in the logs: [mod-init] Adding linuxserver/mods:swag-maxmind to container [mod-init] linuxserver/mods:swag-maxmind digest could not be fetched from lscr.io, checking local cache [mod-init] (ERROR) OFFLINE: linuxserver/mods:swag-maxmind not found in modcache, skipping [mod-init] Adding linuxserver/mods:swag-dashboard to container [mod-init] linuxserver/mods:swag-dashboard digest could not be fetched from lscr.io, checking local cache [mod-init] (ERROR) OFFLINE: linuxserver/mods:swag-dashboard not found in modcache, skipping The container seems to run anyway as do the services that are proxied. What's up with these errors?

I went into Safe Mode, started the array, then edited one of the containers(DuckDNS). I just put a space in the Overview field, then deleted it just to have some sort of change to cause the Apply button to activate. I get the same problem. It shows only "Update Container" , then shows the rest after the update is completed. It used to show the interim steps previously(Stopping container, Removing container, Command execution).

I haven't tried safe mode yet since I'm waiting for a container to have an update available. To update the container, I'm going into the config and changing the Repository field.

Sorry for the long delay. I tried Firefox and still got the same results. It's only when I update the template with a new container version that this happens.

Shout out to Unraid support for turning around my license key so fast - it took 8 minutes to get the license key link in an email! The replacement drive seems to work and so far has survived two boots with no problems.

I didn't have any occassion to reboot the server while on 7.2.0 so I don't know if it was happening before. I do know that I had this same problem earlier this year(~May 2025) and changed out the USB drive then. I'm going to replace the USB drive yet again just in case.

Last time, this happened with the drive in a USB 2.0 port on the back of the server. I have an industrial USB drive I'm going to try.

It did it again. :-( I just tested shutting down and rebooting without moving the drive and it failed to boot. I then booted my Ventoy drive and it came right up. I did this a few times to make sure the port worked, which it did. I then put the USB 3.0 boot drive into into this port on the back of the server and got the same sort of error reported initially. I then rebooted yet again and it booted through and came up, again, like nothing happened. I even put something in the log via logger to show when I rebooted. Nothing out of the ordinary appearing in the syslog. Maybe I burned up another thumb drive? I'm going to get a USB 2.0 drive if I can find a good recommendation and try to restore my backup to it.

Thanks @Frank1940 I removed the adapter and plugged the drive directly into the USB ports. Some also didn’t work but I wound up using a front port. Plus, I had replaced this adapter previously figuring it was the problem. I really think this motherboard had USB problems in general but can’t get consistent behavior.

Yeah, that's what I had. But now I have it plugged into a front USB port. I'm thinking there's something wrong with the motherboard's USB ports in general. I've had numerous issues with them. But I can't confirm it, because then it starts working again.

I don't see anything in the syslog that shows any problem with the thumb drive. I can see it downloading 7.2.2 and its MD5. I see the shutdown request, stopping containers, and then a restart of the system right at the entry, "rc.rsyslogd: Syslog server daemon... Started." and then normal startup stuff. Looks like it wasn't even aware of the multiple times I tried to boot from the USB drive.

Thanks @JorgeB ! The drive is only 7 months old. I tried other ports then finally got it to work on a port on the front of the machine. It was originally on a USB motherboard header connector. Is there a way to confirm the drive is fine now that it's working? That is, confirm there are no missing/corrupt files?

I upgraded my system to 7.2.2 from 7.2.0. I did my usual checklist of updates and backups and then dove it. Upon the first boot of the system, I got the screen attached. I saw in this screen mention of pressing enter to reboot which I did. Then it wouldn't recognize the thumb drive(booted to BIOS). I moved the drive out of the USB motherboard header to a regular USB front port. Still no go. I checked the drive on my main Linux PC. Seemed OK. I tried a port on the back of the PC. No go. Then tried another front port. It finally came up! Whew! (having a victory beer as I type this, was sweating there for a minute) I seem to have had problems with USB since I got this new hardware almost exactly a year ago. It's an ASRock Z790 PRO RS and the thumb drive currently is Samsung Bar Plus 3.1 64GB drive. It's definitely more problematic than the Dell R710 I had previously. I was able to grab the logs directory off of the USB drive after it had booted to the error state. Can anyone tell me what's going on here? Bad USB ports on my motherboard? USB 3.1(vs 2.0) weirdness? PS - Going from 7.1.4 to 7.2.0 went smoothly.

I notice that when I update a Docker container manually, I get a blank status while it's updating but then shows what it was doing when it completes the task. It just says "Update Container". I just wait for it to show the Done button, but it doesn't show progress like it did before. flores-diagnostics-20251207-1008.zip

Yep, BOINC was the problem. Relatively clean syslog now with no odd behaviors.

Yep, it was BOINC. I manually started it and the RAM usage jumped to 94% after a minute or two. There must have been an update that broke it. I'll leave it off for a day or two to see if I continue to get the OOM messages.

Still looking through the logs but I see that things seemed to start going haywire on Friday 11/28/2025 at 22:35:05. It went almost a month with no oom-killing. And before 11/28, the last one was on 10/4/2025, and then before that it was 12/27/2024. On 11/28 it started to call oom-killer for different processes every few minutes! I haven't had any today on 12/1/2025. Got a few theories: Maybe BOINC was causing all this. I see in the config the memory usage was set to use up to 90%. The client is not using the setting I have setup via web prefs. I manually set it to 50%. Bad memory? As soon as it's done with the parity check, I'll run a Memtest.

I was watching a movie last night with the family and all of a sudden Plex stopped playing the movie. A few moments later it looked like it was down. I tried to log into the web page of the server but it was not responding. I also could not ssh into it either. However, I could ping it. I went into the basement and connected a monitor and keyboard. I could log in and saw that BOINC was using lots of memory. The system was very slow at this point and it took a while for "top" to even come up. I paused the BOINC container and it started to behave normally and we finished the movie. This morning I see in the syslog a bunch of oom-killer processes for various apps on my server. These go all the way back to 10/4/2025 of this year. That day also happens to be the first time I got an out of memory error. It bombed on postgres but I was also running a VM with 8GB of RAM at the time so I think that's what did it. It's running a monthly parity check as I type this. Not sure what's going on this time and it seems to be happening often from what I can tell in the logs. Not sure why I was OK from 12/27/2024 to 10/4/2025. Maybe I just need more RAM? I'm on 32GB and my old server had 64GB. flores-diagnostics-20251201-1149.zip

I got it! I had to add the container range, the server range, and the IP of that my ISP gives me to the WOPI setting in the configuration for the Nextcloud Office app. I even tested taking entries out one at a time to confirm they are needed. So, the WOPI values for my instance are: 172.18.0.0/24,192.168.0.100/24,ipaddrisp where ipaddrisp is my IP from the ISP.

I had found the WOPI area of the app and had said I tried things there so you didn't need to provide the breadcrumbs to get there. The online dox for Collabora are pretty bare bones in my opinion. And to get to this point, yes, I've been Googling. Surely you recognized this or perhaps you're new to trying to help people. However, I'll keep Googlin'.

I got it! It was a little weird here and there, but I now have editing capabilities in my Nextcloud instance. Woohoo! Here's what I did: Installed Collabora using the template from L4stIdi0t. I changed the container name to collabora and turned off privileged mode. Tested that I was able to access the container by using the WebUI link for the container. Went into SWAG's appdata/ and removed .sample from the file swag/nginx/proxy-confs/collabora.subdomain.conf.sample At this point, SWAG revokes certs and has a problem connecting back to the standalone server on port 80 to confirm the CA cert. More on this in a bit. Added the CNAME to my domain's DNS. Used TTL=30 minutes so I waited at least this amount of time for it to propagate. Had to wait a little longer but confirmed CNAME was ready by going to https://toolbox.googleapps.com/apps/dig/ to confirm it. At this point going to collabora.mydomain.com gives an OK So now onto getting SWAG to refresh certs. I had to edit the config.php in Nextcloud to remove the "s" for 'overwrite.cli.url' and 'overwriteprotocol'. This made SWAG work again but I don't know why. I then put things back to the way they were originally. With new certs, I was then able to access Nextcloud again. I added the "Nextcloud Office" plugin. I entered the URL for my collabora instance(collabora.mydomain.com) in the "Use your own server". And it worked! I do get a warning about WOPI. I'm not sure what to add to that list. I tried the real IP of the nextcloud and collabora containers and still got an error. I have Collabora turned off for now until I can figure out this WOPI business. I think this ties it down so only Nextcloud can access the internet facing Collabora container. Can someone point me in the right direction on the plugin's WOPI setting?

I saw that setting. Will that Collabora container work with it turned off? I gave the L4stIdi0t template a try. Things went completely wonky when I added the CNAME for Collabora in my registrars DNS setting for my domain. Took me all morning to get SWAG and Nextcloud working again just from that one little change. Not even sure what fixed it other than perhaps a DNS propagation of changes. Nextcloud seems like a delicate house of cards. Again, I think I'll leave well enough alone.