Squid

Nothing yet. You'd have to post a new set once you see it climbing up

First thing you want to do is go to Docker and then hit Container Size. It likely won't add up to the right amount, but you'll probably see a container that is significantly larger than others. This is usually caused by misconfiguration of the settings within the container. IE: You've inadvertently set a downloader to download the files directly into the container instead of outside of it with the result of your image file filling up. For what it's worth, to expand the size of the image, in Settings, Docker disable the service then enter in a higher value for the image size and re-enable. It will automatically expand the vdisk to match

Your screenshots show a folder that exists on disk3 and disk4. There's only a duplicate if there is only a single file within the folder. Depending upon how your split level share settings are, this is quite normal. EG: The mkv may be on disk 3, but the posters could be on disk 4 Not a real issue

I would try and rename /config/rsyslog.cfg on the flash drive to something else and reboot. Not sure if the file gets recreated, hence why I didn't want to delete it just in case we have to restore it

7.1 (soonTM) has them enabled by default. Welcome to my aggravation at times. One just showed up within CA out of the blue. It's an annoyance right now, but as time goes on those PHP Deprecated issues will ultimately become fatal in future versions. LOL. When we started Unraid 7 beta, we had to go and fix tons and tons of them. Generally all uninitialized variables. With CA I cheated as to start using ?? every time I'm looking at a variable or array key, I simply looked at every error that was popping up and initialized the main array with every possible entry set to null. Saved a ton of work and debugging and the inevitable typos.

This might be a regression error on one of the last updates. I'll try and look at it and see if there's a fix

Ideally during dev, you should enable PHP warnings in Tools, PHP Settings. Set them to All Categories. Then look at Tools / PHP Settings, PHP Log during your dev work. IIRC correctly there are some PHP warnings coming from PHP 8's changes. Any improvements to handle the warnings in your code will be fully compatible with the older versions of PHP in 6.12. (Highly unlikely you'd be using any PHP commands / features that have actual breaking changes)

User scripts runs at stopping_svcs. At that point, VMs and Docker are already disabled. This is event is basically right before the disks get unmounted. Hopefully I didn't cause any offence by missing your questions. On any given day I get about 100 notifications and much of them I ignore. This thread a fair amount of time also tends to fall into that as much of the time (most?) its questions regarding making scripts etc rather than the plugin itself

Can you post a screenshot after the docker run command completes with all the layers being pulled. Usually I find that small layers never show Extracting or pull complete. I suspect that what you're seeing is that the GUI "lost" the message on the large layers for some reason. But these don't sound like 0B pulls so its not a container always showing an update being available, and I don't believe that it sounds like you're having any issues after it installs the container.

You want this

Simply rebooting the server would have likely also fixed it. Did you happen to upgrade some other plugins recently?

Click SHOW MORE

Diagnostics *might* help. But, personally I've got no problems with Chrome (my go to) / Safari or FF. My new MacBook Air worked out of the box connecting to the GUI with no settings etc being modified. Connecting via my guest network to the server's GUI via TailScale is barely perceptible that its a hair slower.

We haven't been able to reproduce as of yet, and seems to have only affected a small subset of users. A reboot should resolve this problem, and if it doesn't then please post your diagnostics following the reboot

PM me when you need help / direction on this

Not sure why this is happening, but will check it all out.

and error of 127 from upgradepkg is very strange. Rebooting into safe mode and then attempting to install CA from scratch would tell the story.

Isn't that the last line? "Patches Installed" or "....Reboot to install"

Ratings by the community have been thought about. No ETA on implementation

Thanks. The message itself is harmless, and we're trying to figure out why it's showing up.

Yes - It says "Already Installed"

You can uninstall the mover tuning plugin, reapply the patches, but then errors would result on all of the other files prompting the system to show the banner again to reboot to apply. With regards to the patch for mover, I wouldn't fret about this immediately. Reboot when its convenient. Next revision of the patch plugin is going to have a ton of changes which is going to adjust the behaviour and address most of the concerns / suggestions people have voiced here

Did it list the patch and description?

Because the patch would still fail to fully install on the second attempt, because it would try to patch the other files which have already been patched and then subsequently fail. I can change how the reboot notification gets handled and make it dismissable

The patches do not require a reboot to apply fully. If you've gotten the message saying that a reboot is required it is because you've got Mover Tuning Plugin installed. It replaces one of the files that are being patched. That plugin in its course of action does wind up calling the original script that we are patching. Because we are patching that file, the only way to install the patch is to reboot. Any future patches (if released) won't require a reboot.